Zero-downtime Adobe Commerce upgrade playbook
An Adobe Commerce (Magento) upgrade goes wrong when it is treated as a task. Treated as a small program — audit, rehearse, cut over, hold — it ships without disrupting trading. This is the runbook we used for three consecutive production upgrades for a Southeast Asian sports-retail group.
Week 0 — Compatibility audit
Inventory every extension, customisation, integration and theme override. Check each against the target version. Decide: upgrade, replace, or remove. This audit is 30–40% of the total effort and the part clients want to skip; skipping it is how upgrades take three months instead of six weeks.
Weeks 1–3 — Upgrade in a full staging environment
Production-like data volume, all integrations pointed at sandboxes, full regression suite. Fix, re-run, fix. Performance test at 1.5× peak traffic.
Week 4 — Rehearse the cutover
Run the entire cutover against staging with a stopwatch: freeze, backup, upgrade, smoke test, DNS or load-balancer switch. Then execute the rollback for real. If rollback has not been executed, it does not exist.
Cutover night
Approved maintenance window or blue-green switch, named roles (commander, platform, QA, client sign-off), a go/no-go checkpoint every 30 minutes, and a pre-agreed rollback trigger. Orders, payments, checkout and search are smoke-tested before the client signs off.
Hypercare (2 weeks)
Named rota across time zones, daily error-log review, a defect triage that separates upgrade-caused from pre-existing, and an agreed end date so hypercare does not become free support.
What the client sees
A date that holds, a site that never went down, and an invoice that matches the SOW. That is what a zero-downtime upgrade looks like from the outside; the inside is the discipline above.
Frequently asked questions
- How long does an Adobe Commerce upgrade take?
- 4–8 weeks for a well-audited mid-size store; longer when extensions and customisations were never inventoried.
- Can an Adobe Commerce upgrade be done with zero downtime?
- Yes, with blue-green deployment or a short approved maintenance window, a rehearsed cutover and a tested rollback.
- What is the biggest risk in a Magento upgrade?
- Untested third-party extensions and undocumented customisations; the compatibility audit exists to find them early.
If you are building or fixing a delivery organisation and want someone who has run one as a business, book 20 minutes.
Book a 20-minute intro call