How to migrate page versions from once CQ instance to another?

Question

I am working on Adobe CQ. I created 2-3 versions(1.2,1.2,1.3) for a particular page in my author instance. Now I tried to package my content page and installed it in another instance. I couldn't see the versions of the page which I installed in another instance.

Can anyone help me out doing this?? I want to migrate my content pages along with their versions from one CQ instance to another??

Answer 1

If anyone comes across this question like me, here is the summarised answer:

You can use crx2oak utility available from link below to migrate pages and page version across instances: https://repo.adobe.com/nexus/content/groups/public/com/adobe/granite/crx2oak/

This is a powerful utility with multiple uses (especially in upgrades) as documented in links below:

https://docs.adobe.com/docs/en/aem/6-2/deploy/upgrade/using-crx2oak.html https://jackrabbit.apache.org/oak/docs/migration.html

The source and destination repositories need to be offline while running this utility so best to plan ahead for this type of migration.

HTH

Answer 2

We are in the same situation. You can extract prior version details using the packaging approach, but you will be precluded from reloading them in due to the new Oak security model. The next issue is that you would need to extract and transform the data, and then reinsert due to the node ID's potentially differing, especially if you are using partial data sets to extract.

Where we have gotten to, and are proving now, is to use the new migration tool to move content from instance to instance, which purportedly has a version extract tool. I will update details here when we get our results back.

---

UPDATE:

We have tested the CRX2OAK migration tool, and it indeed does move versions across. Using the tool, you can specify filters to only migrate a subset of content, which will then drag the version details across as well.

It seems this approach works quite well for both single tenancy and multi tenancy approaches as it used to using a package for content.

Unfortunately, it can't be used as a portable backup system, as it is an instance to instance solution. It does, however, work well for blue/green deployment strategies.

Answer 3

Versions are stored by path '/jcr:system/jcr:versionStorage' in AEM. To transfer pages with their versions just create a package with filters for content which you want to move and the version storage path as well, download package and install in other AEM.