Content Transfer Tool

Learn how the Content Transfer Tool lets you efficiently move content from AEM 6.5 to AEM as a Cloud Service.

[Upbeat Music] Migration tools. These are some of the cloud readiness tools, which are developed in mid public. These tools save time while transitioning to AEM, cloud services. These tools also help current implementation to AEM cloud compatible. We’ll discuss these tools in the next slide. And Anthony will demo CTT UI at the end of the presentation.
The content transfer tool is used to move existing content over from a source, AEM instance on-premise or AMS, to the target AEM cloud service instances.
The tool also transfers users and groups required by the content to satisfy permissions. There are two phases associated with the cart and transfers.
One is extraction. During this phase, it extracts the content from the source AEM instance into a temporary area called migration set.
The second part of the CTT is ingestion. Ingesting content from the migration set into the target cloud service instances. The migration set is an Azure blob store area provided by Adobe to temporarily store the transfer content between the source AEM instance and the cloud service AEM instance. It maximum of forward migration sets can be created and maintained, they take time. During the content transfer activity.
Each migration set should have a unique name. If your migration site has been inactive for more than 30 days, it will automatically delete it. CTT extraction can take long time to complete, depending on the repository size you are extracting during this time to check the blob storage for what data is there, When it does create a for debugging purposes, buy using shared access signature, which is your status URL; and for more authentication details to create a connection to blob storage.
This will help to check the progress of the migration.
During the ingestion phase, the target AEM cloud instance will scale down, which means during the ingestion time, the AEM cloud instances will be unavailable.
Plan this activity accordingly. During this time AEM cloud service author in publish will not be available. Some of the important considerations while doing the migration using CTT. Before starting the migration, some of the important considerations to plan for, the system minimum requirement for contractors is AEM 6.3+. And it also requires Java eight.
And if you are on a lower AEM version, you will need to upgrade the content depository, to AEM 6.5 to use the contract transfer tool.
Always start with the newer version of CTT.
There’ll be constant updates to CTT, and newer versions are constantly released. It is always better to take the latest CTT which have some new enhancements.
You can find a newer version of CTT in the software distribution portrait. Ensure the target AEM cloud instance are upgraded to the latest release. If it is a production environment, it is automatically upgraded. Ensure you have admin access to run the tool on the source system. Only admins can run the tool on the source system.
A new feature that is recently added to CTT tool is user mapping.
This is essentially preparing users and group notes in a copy of source AEM GCR for migrating to the cloud. Once migration is complete users with IMS accounts should be able to log into AEM cloud services, and the content is yours should be the same on migrated cloud content, as it was in the source AEM instance.
Before running the CTT tool follow the steps. The best practice is to run compaction data store garbage before extraction is started to check the repository consistencies.
Allocate enough space on the source AEM best practice is to have minimum at least more than one and half percent of what you have currently.
CTT is a resource intensive program activity, so it needs enough resources, system resources to be able to successfully run.
Migration approaches. Before moving onto migration approaches, I want to introduce one other feature of CTT. The content transfer tool has a feature that supports different shared content top up, where it is possible to transfer only changes made since the previous content transfer activity.
After the initial content transfer, it is recommended to do frequent differential content top-ups to shorten the content-free speed here for the final differential content transfers before going live on cloud services. There are a couple of approaches to take on how to do the migration. Approach one: clone the existing production environments, author in publish and install the CTT on the cloned environments, and then do the migration from the clone.
With this, you’re not really disrupting anything on that publish on the actual production instances. You’re completely isolating the migration activities from the current production instances. The second approach is where we can install content transfer to directly on the production author in publish and do the migration from there. when you take this approach, be cautious that you have allocated enough system resources to be able to support this activity. One of the advantages for this approach is it supports top-up differential content migration. In the case of approach one, where clone production instances popups are not supported any delta migrations have to be performed using via a traditional package approach. Before taking one of the approaches, understand the business requirements and choose one of the approaches according to the need. It is also recommended that while this migration activity started taking an approach, and then if possible clean up some of the unused or old data before you start the migration. At the end of the presentation, Anthony will do a quick demo on what CTT UI looks like, and how to create a migrations.
[Upbeat Music] -