Upgrade project and best practices | Community
Skip to main content
gamal_kamil_abd
gamal_kamil_abd
October 16, 2015
Solved

Upgrade project and best practices

  • October 16, 2015
  • 1 reply
  • 520 views

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

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 Sham_HC

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

1 reply

Sham_HC
Sham_HCAccepted solution
Level 10
October 16, 2015

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

Terms & ConditionsAccessibility statement

Loading footer...