Should you upgrade or migrate when your platform reaches end of life?

Upgrade if the platform still fits and the upgrade is mostly routine. Price a migration if most of the cost is rework, or if the next end-of-life date is already in view.

Updated

Start by pricing the upgrade realistically: custom code to rebuild, extensions to replace or retest, integrations to re-verify, and the agency or internal time involved. Then ask three questions:

  • Does the platform still fit how the business sells and publishes today?
  • How much of the custom code serves the business, and how much exists to make the platform behave?
  • When is the next end-of-life date for the version you would upgrade to?

If the platform fits and the upgrade is routine, upgrading is usually the cheaper path. If most of the cost is rework, or you would be back at the same decision in two or three years, price a migration to a platform that is updated as part of the service alongside it. Use the support date and your change freeze to set the decision deadline. See Migrating to composable commerce before your platform reaches end of life.

← Back to Help Center