Migrate Content from AMS to AEMaaCS | Community
Skip to main content
Mahedi_Sabuj
Community Advisor
Community Advisor
September 11, 2024
Solved

Migrate Content from AMS to AEMaaCS

  • September 11, 2024
  • 1 reply
  • 805 views

Is it possible to migrate content from one org to another using CTT?

For example, we have OrgA with an AMS setup and OrgB with an AEMaaCS setup. A user has access to both Cloud Manager instances. Can content be ingested using Ingestion Jobs from OrgA into OrgB?

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 Tad_Reeves

The Content Transfer Tool doesn't require (or care) that your source and destination are in the same org, as that's not at all how they authenticate.   A primary use case for the CTT (and how I've used it in almost every case) is to transfer from an on-prem 6.5 environment to AEM as a Cloud Service, and in such case the source environment is not in any Adobe-managed org at all.  In fact, the last time I used this was done on a copy of a 6.5 Author that I had hosted on a computer under my desk.  

So, the answer to your question is yes - you absolutely can migrate content from two separate orgs. 

1 reply

Tad_Reeves
Adobe Champion
Tad_ReevesAdobe ChampionAccepted solution
Adobe Champion
September 11, 2024

The Content Transfer Tool doesn't require (or care) that your source and destination are in the same org, as that's not at all how they authenticate.   A primary use case for the CTT (and how I've used it in almost every case) is to transfer from an on-prem 6.5 environment to AEM as a Cloud Service, and in such case the source environment is not in any Adobe-managed org at all.  In fact, the last time I used this was done on a copy of a 6.5 Author that I had hosted on a computer under my desk.  

So, the answer to your question is yes - you absolutely can migrate content from two separate orgs. 

Mahedi_Sabuj
Community Advisor
Community Advisor
September 26, 2024

Thanks @tad_reeves. I successfully migrated content from AMS to AEMaaCS.

However, I encountered an issue during ingestion jobs where no environments were available in the destination dropdown. I later discovered that migration sets need to be created on AEMaaCS, not AMS.

Mahedi Sabuj