Get answers to frequently asked questions about content migration to AEM as a Cloud Service.
Please use the below template for providing more details while creating CTT related Adobe support tickets.
There are three different methods available
No. CTT as a tool could extract from AEM source and ingest into AEMaaCS. However there are specific limits on AEMaaCS platform that should be considered before migration.
For more info, refer to cloud migration prerequisites.
Please review the code and content complexity assessment provided by the tool and make a note of associated action items that lead to code refactoring backlog or Cloud Migration Assessment.
It is always recommended to perform 1:1 extraction and ingestion between author and publish tiers. That being said, it is acceptable to extract source production author and ingest that into Dev, Stage, and Production CS.
Since the migration process depends on internet band width, heap allocated for CTT process, free memory available, and disk IO which are subjective to each source system, it is recommended to execute Proof Of migrations early on and extrapolate that data points to come up with estimates.
CTT tool runs in its own Java™ process which takes up to 4gb heap, which is configurable through OSGi configuration. This number may change but you can grep for the Java™ process and find that out.
If AZCopy is installed and/or Pre copy option / validation feature enabled, then AZCopy process consumes CPU cycles.
Apart from jvm , the tool also uses disk IO to store the data on a transitional temp space and that will be cleaned up after extraction cycle. Apart from the RAM, CPU and Disk IO, CTT tool also uses the network band width of the source system to upload data into Azure blob store.
The amount of resources the CTT extraction process takes depends on the number of nodes, number of blobs and their aggregated size. It is hard to provide a formula and hence it is recommended to execute a small Proof of migration to determine the source server upsize requirements.
If clone environments are used for migration, then it will not impact the live production server resource utilization but has its own downsides regarding synching content between Live production and clone
The short answer is “Yes”.
The CTT extraction and ingestion without user mapping only migrates the content, the associated principles (users, groups) from source AEM to AEMaaCS. But there is a requirement for these users (identities) present in Adobe IMS and have (provisioned with) access to AEMaaCS instance to successfully authenticate. The job of user-mapping tool is to map the local AEM user to IMS User so that authentication and authorizations work together.
In this case, the SAML identity provider is configured against Adobe IMS to use either Federated / Enterprise ID, rather than directly to AEM using Authentication handler.
The short answer is “Yes”.
The CTT extraction and ingestion without user mapping does migrate the content, the associated principles (users, groups) from source AEM to AEMaaCS. But there is a requirement for these users (identities) present in Adobe IMS and have (provisioned with) access to AEMaaCS instance to successfully authenticate. The job of user-mapping tool is to map the local AEM user to IMS User so that authentication and authorizations work together.
In this case, the users use personal Adobe ID and the Adobe ID is used by IMS admin for providing access to AEMaaCS.
In the context of extraction phase, The options are either to overwrite the data in the staging container from previous extraction cycles or add the differential (added/updated/deleted) into it. Staging Container is nothing, but the blob storage container associated with migration set. Each migration set gets their own staging container.
In the context of ingestion phase, The options are + to replace the entire content repository of AEMaaCS or sync the differential (added/updated/deleted) content from staging migration container.
Yes, it is possible but requires careful planning regarding:
Please review the Top up extraction and ingestion process as documented before planning the migrations.
Yes. End-user traffic is not interrupted by content migration activity. However, the author ingestion freezes content authoring until it completes.
Yes. The missing original rendition means the asset binary is not properly uploaded in the first place. Considering it as bad data, please review, backup using Package Manager (as required) and remove them from source AEM before running extraction. The bad data will have negative results on the asset processing steps.
jcr:contentnode for folders. What should I do with them?
jcr:content is missing at folder level, any action to propagate settings such as processing profiles, etc. from parents will break at this level. Please review the reason for missing
jcr:content. Even though these folders could be migrated, please note that such folders degrade user experience and cause unnecessary troubleshooting cycles later.
Yes, there is a Check Size feature which is part of the CTT.
Yes, there is a validation feature which is part of CTT.
Unfortunately, No. CTT’s use case is to migrate content from On-premises/AMS-hosted AEM 6.3+ source to AEMaaCS cloud environments. Please read CTT documentation.
Extraction Phase is an involved process that requires multiple aspects to work as expected. Being aware of different kind of issues that may occur and how to mitigate them increases the overall success of content migration.
The public documentation is continuously improved based the learnings, but here are some high-level problem categories and possible underlying reasons.
Ingestion phase completely occurs in cloud platform and requires help from the resources that have access to AEMaaCS infrastructure. Please create a support ticket for more help.
Here are possible issue categories (please do not consider this as an exclusive list)
The short answer is “Yes”.
The CTT process requires connectivity to the below resources:
Refer to the documentation for more information about source connectivity.
No. To process the assets, the request to reprocess must be initiated.
Yes. The assets are reindexed based on the index definitions available on AEMaaCS.
Yes, please consider the following when source AEM has Dynamic Media Integration.
Please read the above question and answer before
(These are two possible options but are not limited to only these two). It depends on how customer wants to approach the UAT, Performance testing, the available environment and whether a clone is being used for migration or not. Please consider these two as starting point for discussion
If the number of assets / nodes in the source environment are on lower end (~100K), assuming these can be migrated over a period of 24 + 72 hours including extraction and ingestion, the better approach is
With this option you can run migration one to one, meaning On-prem Dev → AEMaaCS Dev, and so forth. and move the DM configurations from respective environments
(In case the migration is being planned to be performed from Clone)
Run a wipe migration from on-premise Dev to AEMaaCS Dev.
The above approach can be used for just measuring the migration duration but requires cleaning it up later.