Plenty of organizations still run Sitecore 9.3. It works, but each year it falls further behind on security fixes, supported platforms and features. If you're planning the move, this checklist covers the steps that keep an upgrade from turning into a six-month surprise.
Why upgrade now
Check Sitecore's product support lifecycle page for the current support status of your version. Beyond support, newer versions bring newer .NET, SQL Server and Solr support, faster deployments with items as resources (10.1 and later), and the modern Sitecore CLI for serialization. Waiting longer makes the jump bigger, not easier.
First decision: XP, XM or XM Cloud?
Before anything technical, answer one question: do you use xDB, personalization and marketing automation?
- If yes, an XP 10.x upgrade keeps your analytics data and features.
- If not, XM 10.x is simpler and cheaper to run.
- If you're ready for a headless front end and want Sitecore to run the platform, assess XM Cloud. That's a migration, not an upgrade. Components are rebuilt for a headless front end, so budget accordingly.
Phase 1: Inventory what you have
- Topology: roles (CM, CD, processing, reporting), servers, xConnect, Identity Server.
- Modules: SXA, Sitecore Forms, EXM, Publishing Service, Commerce, and any marketplace modules.
- Custom code: solution projects, pipeline processors, event handlers, scheduled tasks.
- Config patches: every file in
App_Config/Includeand your environment-specific patches. - Integrations: CRM, search, DAM, SSO, payment and anything else calling in or out.
- Infrastructure: SQL Server, Solr, .NET Framework and Windows Server versions.
Phase 2: Check compatibility
Use Sitecore's compatibility tables to confirm the supported SQL Server, Solr, .NET and module versions for your target release. Solr usually needs upgrading too, and indexes have to be rebuilt. Every marketplace module needs a version that supports the target, or a replacement plan. This phase often decides which 10.x version you target.
Phase 3: Upgrade in a separate environment
- Install a clean instance of the target version, with its modules.
- Upgrade copies of your databases. For 10.1 and later, Sitecore provides an upgrade tool for the database step, so read the upgrade guide for your exact source and target versions.
- Update NuGet references in your solution to the target version, then fix compile errors from removed or changed APIs.
- Rebase your config patches on the new default configuration instead of copying old files over.
- Move developer-owned items into serialization (Sitecore CLI, Unicorn or TDS) so environments can be rebuilt repeatably.
- Rebuild all Solr indexes.
Phase 4: Test properly
- Smoke-test every page template and component.
- Have content authors run their daily tasks: editing, workflow, publishing and media uploads.
- Test every integration end to end.
- Compare performance against the baseline from your current production site.
- Run a security scan and review roles and permissions.
Cutover and rollback
Agree a content freeze window, take full database backups, and do a final content sync before switching traffic. Write down the rollback steps and who decides to use them before go-live day, not during it. Keep the old environment available for at least a couple of weeks.
After go-live
Watch logs, response times and publishing closely for the first two weeks. Then clean up: remove old patches and unused modules, and document the new setup so the next upgrade is easier.
What to do next
Start with the inventory. It's useful even if the upgrade is a year away, because it shows how big the job really is. I can run an upgrade readiness assessment that produces the inventory, a compatibility report and an effort estimate.
