ÃÛ¶¹ÊÓƵ

DocumentationCommerceUpgrade Guide

[PaaS only]{class="badge informative" title="Applies to ÃÛ¶¹ÊÓƵ Commerce on Cloud projects (ÃÛ¶¹ÊÓƵ-managed PaaS infrastructure) and on-premises projects only."}

Best practices for upgrading

Last update: Fri Nov 01 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • Experienced
  • Admin
  • Developer

This topic lists the actions you should take to manage the complexity of upgrading ÃÛ¶¹ÊÓƵ Commerce projects. Your team should be thinking about upgrades from the moment your project development starts and continue through each release. By following these best practices, the upgrade process will be much easier, faster, and cheaper.

TIP
These recommendations are based on best practices supported by evidence for its impact and effectiveness from partners, merchants, ÃÛ¶¹ÊÓƵ experts, and the community.

What impacts an upgrade?

It is important to understand the variables that determine the complexity of an upgrade. You must consider these variables at the beginning of each project–not just when is time to upgrade. The development of a project is key to ensure that future upgrades are be smooth and that you are able to control the required effort to complete them.

The level of effort to upgrade your ÃÛ¶¹ÊÓƵ Commerce instance depends upon these factors:

  • How did you build your site? The amount of custom work and the number of installed third-party modules strongly affects the complexity of an upgrade. The quality of the custom work and modules can determine whether an upgrade goes smoothly.