How to export and install content with version history

[matija_kovacek]

I have a case where I need to backup a content (site pages) including their versions, so to we can an any time on any instance restore the content with their versions. Content is on AEMaaCS, restore activity can be and doesn't need to be on AEMaaCS.

Seems crx2oak could support this, but we can't use it due to AEMaaCS.

We tried to create a package with content and versions /jcr:system/jcr:versionStorage/*. Can be exported, but can't be installed on other instance, due to different errors, based on how we export versions (e.g versionStorage root VS versionHistory of the page VS only specific version of the page )

First error was org.apache.jackrabbit.vault.packaging.PackageException: Error creating/updating node /jcr:system/jcr:versionStorage/8e/90/dd/8e90dd8e-b13b-4d44-83a1-ea6c8498d3be. Caused by javax.jcr.nodetype.ConstraintViolationException: /content/test/main/en/archive/jcr:content/jcr:versionHistory is protected 
First error was org.apache.jackrabbit.vault.packaging.PackageException: Error creating/updating node /jcr:system/jcr:versionStorage/ff/70/d2/ff70d273-1a75-4eb4-86df-75389ee5abd9/1.0. Caused by javax.jcr.PathNotFoundException: 1.0 

Also I'm aware of VersionManger and VersionHistory API.

I'm wondering is it possible to somehow programmatically achieve this or any different way?

Thanks.

[Shashi_Mulugu]

Hi @matija_kovacek ,

I dont think it is possible in aem cloud.

[matija_kovacek]

What would be possibilities on non cloud version?

[Saravanan_Dharmaraj]

For Non cloud, like you said CRX2OAK is the option. Used in AMS/On Prem set up for transferring with version. 

[muskaanchandwani]

Hello @matija_kovacek 

For AEMaaCS :

Environment‑level backup/restore via Cloud Manager, which restores the entire repository including versions to a point in time on the same environment

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/operations/resto...

Using JCR VersionManager/VersionHistory only within a single repository for local restore/version operations.

If you need "backup + restore with versions":
- Use Cloud Manager restore for that environment, within the backup window.
- For cross‑instance migration, only move current content, and if you need history, you may explore implementing your own snapshot/versioning scheme instead of moving raw JCR versions.

[lavishvasuja]

@matija_kovacek -

In AEM as a Cloud Service, content backup and restore are supported, but JCR version history cannot be transferred across instances.

• Version storage (jcr:system/jcr:versionStorage) is protected and repository-bound, so exporting or importing it via packages or tools like crx2oak isn’t supported.

• Cloud Manager restore is designed for point-in-time rollback within the same environment, not for cross-instance migrations.

• JCR APIs such as VersionManager operate only within a single repository and can’t recreate version history elsewhere.

For cross-instance needs, the supported approach is to migrate the current content state and handle historical requirements via snapshots or external versioning, rather than JCR versions.

Adobe reference:

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/operations/resto...