Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Is a 6.1 content package compatible with with 6.5?

Avatar

Level 2

We are on 6.1 and building a new set of 6.5 servers. I would like to take sample content from the 6.1 server, page content and assets, and install on the 6.5 server testing. This will speed up the process of checking the front end code.

Will 6.5 be able to use a content package from 6.1 on 6.5? Will we be able to migrate content from 6.1 to 6.5?

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

Yes, Packages created from <host>:<port>/crx/packmgr/index.jsp are compatible with all versions of AEM

View solution in original post

4 Replies

Avatar

Correct answer by
Employee Advisor

Yes, Packages created from <host>:<port>/crx/packmgr/index.jsp are compatible with all versions of AEM

Avatar

Level 3

If the package contains only assets and content - that should be ok. If the package contains Java code - then no - the APIs will be outdated.

Avatar

Employee Advisor

From upgrade planning perspective, we need to first define the upgrade procedure

1. fresh install approach - we create a new 6.5 instance - move upgraded artefact, content, tags, ACLs etc

2. In-place upgrade - we upgrade the existing 6.1 instance to 6.5.

This decision is mostly made based on

1. size of your repository

2. infrastructure setup

Content packages are agnostic to AEM versions. So as long as component properties and features are not modified, content package created from previous version can be used in another version.

Other tools that you can consider for content movement are

1. VLT-RCP

2. GitHub - TWCable/grabbit: Grabbit - Fast Content Sync tool for AEM/CQ