Need help with using the CRX2OAK tool with my AEM Guides instances. | Community
Skip to main content
Level 2
February 4, 2026
Solved

Need help with using the CRX2OAK tool with my AEM Guides instances.

  • February 4, 2026
  • 3 replies
  • 40 views

We have an instance of AEM 6.5.12. with Guides 4.6 UUID running on a server and we want another instance of the exact same thing on another server that we will use as our “development server.”

 

This is not an upgrade. We want the 2 instances to be identical.

On our new server I have installed the exact same AEM 6.5 with the same service pack and same 4.6 release guides. 

 

All we need is the repository from the first instance. I cannot use package manager to do this because we must preserve the version history of all of our DITA topics. 

 

From the documentation I’ve read it seems the best way to do this is with ther CRX2OAK tool.

I’m not experienced with migration and would appreciate any steps or advice you might have. 

  1. First, is the CRX2OAK tool the  best way to accomplish this?
  2. How do I get one repository to connect with another? Should the crx-quickstart folder from the target server be on the same server as our first AEM installation? 
  3. If so, what is the best way to move the crx-quickstart file? Simple copy and paste?
  4. Once the migration is complete ,again, how do I get the repository folder back to the target server?

Any help here is appreciated!

Best answer by BrettBirschbach

If you’re just trying to get a one-time duplicate of your current server (rather than an ongoing merge) as a starting point for the development server, you can simply:

  1. Turn off the source server
  2. Zip the `crx-quickstart` folder (new file, leaving the existing folder in-place)
  3. Turn on the source server
  4. Move the zipped crx-quickstart to wherever your dev server is, alongside the AEM jar
  5. Assuming there isnt already a `crx-quickstart` folder here (i.e. server has never been created) unzip the file to a `crx-quickstart` folder.
  6. Start the dev server AEM Jar - it will use the `crx-quickstart` folder in place, and will be exactly the same as the server you copied from.

This doesn’t “merge” servers, and this doesn’t handle ongoing syncs.  For doing that, `crx2oak` is probably worth investigating, but I cant say for sure if it’s the best method.

3 replies

kautuk_sahni
Community Manager
Community Manager
February 11, 2026

@arunpatidar  ​@lukasz-m  ​@BrettBirschbach Adding you to the thread in case you have thoughts or best practices to offer on this topic. Your expertise would would be helpful here, thanks!

Kautuk Sahni
BrettBirschbach
Adobe Champion
BrettBirschbachAdobe ChampionAccepted solution
Adobe Champion
February 11, 2026

If you’re just trying to get a one-time duplicate of your current server (rather than an ongoing merge) as a starting point for the development server, you can simply:

  1. Turn off the source server
  2. Zip the `crx-quickstart` folder (new file, leaving the existing folder in-place)
  3. Turn on the source server
  4. Move the zipped crx-quickstart to wherever your dev server is, alongside the AEM jar
  5. Assuming there isnt already a `crx-quickstart` folder here (i.e. server has never been created) unzip the file to a `crx-quickstart` folder.
  6. Start the dev server AEM Jar - it will use the `crx-quickstart` folder in place, and will be exactly the same as the server you copied from.

This doesn’t “merge” servers, and this doesn’t handle ongoing syncs.  For doing that, `crx2oak` is probably worth investigating, but I cant say for sure if it’s the best method.

kautuk_sahni
Community Manager
Community Manager
February 17, 2026

@davidl38471046 Following up to see if this has been resolved. If you’ve found the answer, whether through the suggestions here or through your own troubleshooting, feel free to post the solution so others can benefit. If any reply helped along the way, marking it as accepted ensures the most useful information is easy to find. Thanks for helping close the loop!

Kautuk Sahni