Getting Started with Content Transfer Tool getting-started-content-transfer-tool

Navigate to the Adobe Experience Manager Web Console on your source instance, by going to Tools > Operations > Web Console or directly to the URL at https://serveraddress:serverport/system/console/configMgr

Search for Content Transfer Tool Extraction Service Configuration

Use the pencil icon button to edit its configuration values

Enable the Enable ssl logging for extraction setting, then press Save:

Log into Cloud Acceleration Manager (CAM) and click the CAM project that you had created previously to assess your readiness to move to AEM as a Cloud Service. If you haven’t created a CAM project, refer to Creating and Managing a Project in CAM.

Click the Content Transfer card to open the Migration Set List view.

Create a Migration Set by clicking Create Migration Set.

The following dialog box is presented. Notice that a migration set will expire after a prolonged period of inactivity. After warnings are displayed on the project card and the migration job table rows for a time period, the migration set will expire and its data will no longer be available. Review Migration Set Expiry for details.

You should now see your migration list in the list view. Select the three dots symbol (…) to open the drop-down and select Copy Extraction key. You need this key during the Extraction phase. Copy this Extraction key.

After installing the latest version of the Content Transfer Tool on your source Adobe Experience Manager instance, go to Operations - Content Migration

Click Create Migration Set.

Paste the extraction key that was copied from CAM earlier into the Extraction key input field of Create Migration Set form. After you do this, the Migration set name and Cloud Acceleration Manager (CAM) Project name fields are automatically populated. These should match the Migration Set name in CAM and the CAM project name that you created. You can now add content paths. After you have added content paths, save the migration set. You can run the extraction with either versions included or excluded.

Next, select the following Parameters to create a Migration Set:

1. Include Version: Select as required. When versions are included, the path /var/audit is automatically included to migrate audit events.

   

   note note
   NOTE
   If you intend to include versions as part of a migration set, and are performing top-ups with wipe=false, then you must disable version purging due to a current limitation in the Content Transfer Tool. If you prefer to keep version purge enabled and are performing top-ups into a migration set, then you must perform the ingestion as wipe=true.

2. Paths to be included: Use path browser to select paths which need to be migrated. Path picker accepts input by typing or by selection.

   note important
   IMPORTANT
   Following paths are restricted while creating a migration set:
   /apps /libs /home /etc (some /etc paths are allowed to be selected in CTT)

Click Save after you populate all the fields in the Create Migration Set details screen.

Select a migration set and click Check Size.

This opens up the Check Size dialog.

Click Check Size to start the process. You will then return to the migration set list view, and you should see a message indicating that Check Size is running.

After Check Size process is completed, the status changes to FINISHED. Select the same migration set and click Check Size to view results. Below is an example of Check Size results with no warnings.

If the Check Size results indicate that either there is insufficient disk space, or the migration set exceeds product limits, or both, a WARNING status is displayed.