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

Upgrade project and best practices

gamal_kamil_abd
Level 1
Level 1

We are planning to run a technical as-is upgrade of our website from CQ 5.2 to 5.6 without changing functionality. From a planning perspective:

 

1. What are the considerations we need to address to understand the required effort and time required for the upgrdade?

2. Dow we need to run any migration of the content? how long does it take for a medium complex environment, say for a single system environment (DEV or Prod)

3. What are the risks, if the content is considered highly bespoke?

 

thanks

1 Accepted Solution
Sham_HC
Correct answer by
Level 10
Level 10

Refer [1] for planning.  

Ultimately you want to upgrade production. I would recommend clone production into dev & start upgrading so that you will know well ahead what are the problems so that your production upgrade will be smooth.

If you need version history you might need to plan that piece for migration.

More details at [2]

[1]  http://dev.day.com/docs/en/cq/current/deploying/upgrading/planning.html

[2]   http://dev.day.com/docs/en/cq/current/deploying/upgrading.html

View solution in original post

1 Reply
Sham_HC
Correct answer by
Level 10
Level 10

Refer [1] for planning.  

Ultimately you want to upgrade production. I would recommend clone production into dev & start upgrading so that you will know well ahead what are the problems so that your production upgrade will be smooth.

If you need version history you might need to plan that piece for migration.

More details at [2]

[1]  http://dev.day.com/docs/en/cq/current/deploying/upgrading/planning.html

[2]   http://dev.day.com/docs/en/cq/current/deploying/upgrading.html

View solution in original post