Sitecore

Sitecore Upgrades: A Mini-Series Table of Contents

Welcome to my Mini-Series! In my Mini-Series, I take you through the steps required to perform a Sitecore upgrade. Use this Mini-Series to help empower your business with the latest version of Sitecore!

How long does it take to upgrade?

Sitecore - Understanding Development Approaches: A Sitecore Outlook
Understanding Development Approaches: A Sitecore Outlook

Designing, building, and implementing top-notch experiences not only requires a great deal of planning, strategy, and time – it also requires the right digital experience platform (DXP) and the right development approach for your business needs.

Get the Guide

The path to upgrading your solution is unique. It’s your own custom solution, after all. Listed below is how long each phase will likely take where one sprint is two weeks. The more complex the solution, however, the longer the upgrade will take.

  • Investigation – 1 sprint
  • Database Upgrades – 1 sprint
  • Sitecore.Config Patching – 1 sprint
  • Dependency Injection Changes – 1 sprint
  • ORM and Other Dependency Updates – 2 sprints
  • Infrastructure Setup – 2 sprints
  • Testing and Bug Remediation – 2 sprints

At the beginning of the upgrade, you will want to spend two weeks making decisions on how you will do the upgrade. This investigation phase should include what dependencies you want to remove/upgrade, what your infrastructure will look like, etc. You will also need to spend at least to set up your infrastructure and deal with the myriad of user access issues, whitelisting IPs, etc. Your investigation phase will determine whether you’re retaining your current infrastructure, shifting to Azure PaaS, shifting to SaaS, or even moving to containerized environments.

You will also want to have test users go into the site to find bugs once the upgraded solution is deployed. They will be crucial in finding incorrect behaviors for the new version of the site. If you are switching search providers for your solution, you should tack on another sprint or two to your timeline. All in all, I would suggest a 4-month period to have a completely successful upgrade with bugs ironed out.

About the Author

More from this Author

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Subscribe to the Weekly Blog Digest:

Sign Up
Categories