Instead of using tree-activation or creating multiple packages to migrate content, run a special migration tool from within the ContentBus CQ instance. This migration tool connects via RMI to the fresh CRX instance. Then, it spools content and versions directly to the destination repository.
(ContentBus is abbreviated with CB in the following text.)
- Set up a fresh CQ4.2.1 running on CRX1.4.2 (see  ).
- Install the attached migration3.5.5to4.2.zip according to the included readme instructions
- Make sure that you restart the CB instance and that RMI access is enabled in the target CRX instance.
- Request the migration tool on the CB instance, http://://system/migration/content/versions.html.
- Provide the root path of pages to migrate.
- Select Dump to simulate a dry run; deselect to migrate content/versions.
- Select Include Content if you want to migrate content pages as well. Otherwise, only versions are migrated if corresponding content pages are in the destination repository.
- Click Submit to start the migration process.
- Depending on the volume of your source instance, the migration process takes some time to finish. After the process is complete, stop the CRX based CQ author webapp via the CQSE admin interface. Make sure to keep CRX running. Because the migration tool has created content and versions via the JCR API, it is required to rebuild CQ's search indexes and also the uuid-registry.
Do the following on the CRX based CQ4.2.1 instance:
- Delete all search indexes below <cq_home>/data/author.
- Rebuild the uuidRegistry.properties file, for instructions see .
- Start the CQ4.2.1 webapp via the CQSE admin interface.
Content and versions are available now on the new CQ4.2.1 running on CRX.
For more information regarding migration in general, see the corresponding documentation  on docs.day.com.
 Install CQ4.2 with CRX1.4.2
 Recreate UUID registry
 Migration on docs.day.com