Migrating JCR Data from one AEM instance to another

Forum|Forum|8 years ago
April 6, 2017
7 replies
5254 views

I have a situation where I have created a new instance of aem 6.2

I have installed and run a package on the new instance with my AEM 6.0 site.

My code works correctly, the DAM moved correctly, content is correct.

However the versions I have on several pages is not transferred.

So I need a method to export the relevant JCR data from my old instance into the new instance.

Is there any recommended tools and best practices to doing this.

Regards

Clive Stewart

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

Best answer by MC_Stuff

Oak migration tool will help http://jackrabbit.apache.org/oak/docs/migration.html

C

Clive_StewartAuthor

New Participant

Thank you Scott,

That was what I was looking for

MC_StuffAccepted solution

New Participant

Oak migration tool will help http://jackrabbit.apache.org/oak/docs/migration.html

Kunal_Gaba_

New Participant

Package manager does not support version copy. You can use OAK migration utility to copy the full repository content including the version history.

Refer this documentation - http://jackrabbit.apache.org/oak/docs/migration.html

smacdonald2008

New Participant

I am going to check to see if this is a known issue. I seem to recall in the past - this was an issue.

C

Clive_StewartAuthor

New Participant

To elaborate.

All the content is transferred, but archived content is not.

The authors often run special events on a page and then revert back to the previous version after a period of time.

I have tried moving content across using the package manager, and I do get everything across but I end up loosing all previous versions of the pages.

C

Clive_StewartAuthor

New Participant

Hi Scott, it is the previous versions of a page that are missing.

smacdonald2008

New Participant

The best way is to indeed use Package Manager:

https://docs.adobe.com/docs/en/aem/6-2/administer/content/package-manager.html

When you use Package Manager and include your pages under /content - what exactly is missing?