Migration of Content & Assets from other CMS to AEM as cloud service | Community
Skip to main content
rajatc
rajatc
March 1, 2024
Solved

Migration of Content & Assets from other CMS to AEM as cloud service

  • March 1, 2024
  • 2 replies
  • 1423 views

We're currently engaged with a client to transfer their current content and assets from various sources to AEM as a cloud service.

Consequently, we're seeking to devise a migration strategy. Content may originate from platforms like WordPress, while assets are sourced from platforms such as Amazon S3 and other DAM solutions/products. 

Could you assist us in outlining the migration process for both content and assets into AEM as a cloud service?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by SureshDhulipudi

If you have to migrate content from different sources - first you have to start content analysis and structure of the different sources.

In a high-level

Content Migration:

  • Content Analysis : Analyze the existing content in the source system (like WordPress). Identify the content types, their structure, and relationships.
  • Content Model Design:Design the content model in AEM. This includes creating templates, components
  • Content Extraction / Transformation : Extract the content from the source system in a format that can be imported into AEM and transform to AEM format
  • Content Import : Import the transformed content into AEM

 

Same for Assets also - Analyze the existing asset data.

 

To upload assets from a third-party application to Adobe Experience Manager (AEM) author, you can use AEM's HTTP API. This API allows you to perform CRUD operations on AEM assets using HTTP requests.

https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/assets/admin/developer-reference-material-apis.html?lang=en

2 replies

pulkitvashisth
Community Advisor
pulkitvashisthCommunity Advisor
Community Advisor
March 1, 2024

Hi @rajatc 
As per documentation you can migrate content to AEMaaCS via

If you are not migrating from AEM previous versions, then for content (as in webpages) you would have to go through the process of creating pages from scratch in AEM( via templates and components)

For Assets , above sources should be ok.

Also while migrating to AEMaaCS you would need to setup a new project on the Adobe Cloud Manager , you can follow Cloud Acceleration Manager for the same.

 

    rajatc
    rajatcAuthor
    March 1, 2024

    Hi @pulkitvashisth 

     

    Thank you for responding. However, in our situation, we're transitioning from platforms such as WordPress or Amazon S3, which are not AEM. Consequently, we won't be able to utilize the content transfer tool in this scenario.

      SureshDhulipudi
      Community Advisor
      SureshDhulipudiCommunity AdvisorAccepted solution
      Community Advisor
      March 1, 2024

      If you have to migrate content from different sources - first you have to start content analysis and structure of the different sources.

      In a high-level

      Content Migration:

      • Content Analysis : Analyze the existing content in the source system (like WordPress). Identify the content types, their structure, and relationships.
      • Content Model Design:Design the content model in AEM. This includes creating templates, components
      • Content Extraction / Transformation : Extract the content from the source system in a format that can be imported into AEM and transform to AEM format
      • Content Import : Import the transformed content into AEM

       

      Same for Assets also - Analyze the existing asset data.

       

      To upload assets from a third-party application to Adobe Experience Manager (AEM) author, you can use AEM's HTTP API. This API allows you to perform CRUD operations on AEM assets using HTTP requests.

      https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/assets/admin/developer-reference-material-apis.html?lang=en

        Terms & ConditionsAccessibility statement

        Loading footer...