Magento Upgrade: 12 questions answered.

Fixed-price tiers, no per-hour surprises:

• Express: $1,499, minor-version jumps (2.4.7/2.4.8 → 2.4.9), Hyvä intact, < 5 custom modules
• Standard: $3,499, multi-version jumps, theme migration, up to 20 extensions
• Enterprise: Custom quote, B2B, multi-store, 30+ extensions, ERP/POS integrations, M1 → M2

Every quote includes pre-upgrade audit, full QA, blue-green deploy, and 14 days of post-launch bug-fix coverage.

No. Magento upgrades are schema-only, your products, customers, orders, reviews, CMS pages, configurations all stay intact. We snapshot the production database before every step, run the upgrade on a clone, validate counts (orders, customers, products) match before and after, and only then promote to production. Plus the blue-green setup means the original DB is preserved for 72 hours.

You don’t have to upgrade to 2.4.9 the day it ships, but you do need to be on a supported, patched line. If you’re on 2.4.4 or older, your version goes EOL in 2026 and stops receiving security patches, that’s the urgent case. For 2.4.5+, you can stay on your current line as long as you apply the May 12 security patch (2.4.x-pYY).

Some will. The pre-upgrade audit (free with every booking) catalogues every extension + custom module on your store and flags incompatibilities before we touch production. For incompatible extensions we either: (1) upgrade to a 2.4.9-compatible version from the vendor, (2) patch the extension ourselves if the vendor is slow, or (3) rebuild the functionality natively. You get a full report before any work starts, no surprises.

Typical timelines:

• Express (2.4.7 / 2.4.8 → 2.4.9): 5-7 business days
• Standard (2.4.5 / 2.4.6 → 2.4.9): 10-14 business days
• Major (2.4.3 or older → 2.4.9): 3-5 weeks
• Magento 1 → 2.4.9: 6-12 weeks (full re-platform)

Add 2-3 days for staging review, regression QA, and the production go-live window.

Adobe Commerce 2.4.9 supports PHP 8.3 and 8.4 (8.4 recommended). MariaDB 10.6 / 10.11, MySQL 8.0, OpenSearch 2.x, RabbitMQ 3.13, Redis 7.2. We handle the full stack, if your hosting needs upgrading we can either coordinate with your provider or migrate you to a more performant setup as part of the upgrade.

Two safety nets: (1) Blue-green means the old version stays warm for 72 hours, one DNS flip rolls back instantly. (2) Every upgrade includes 14 days of post-launch bug-fix support: anything that breaks because of the upgrade gets fixed at no extra charge. After day 14, you can move to a monthly retainer if you want continued cover.

If your store has < 5 extensions, no custom modules, and you’re comfortable with composer + bin/magento, yes. Adobe’s own upgrade tool handles most of it. The cases where DIY usually goes wrong: extension conflicts, broken indexers post-upgrade, payment/checkout regressions you don’t catch in QA, missing data patches, and the dreaded composer.lock conflict between core modules and theme overrides. If your monthly orders have a comma in them, get help.

Not if it’s done right. We preserve every URL rewrite, canonical, hreflang, sitemap, and structured-data block. Pre/post crawls (Screaming Frog) compare the URL set; any 301 redirects you had stay 301s. Core Web Vitals typically improve on 2.4.9 because of the new caching + Hyvä performance fixes, which is good for rankings, not bad.

We typically run 3-4 upgrade cohorts per month with capacity for 2 stores per cohort. The May 12, 2026 launch cohort books out 4-6 weeks ahead, so reserve before April 1, 2026 for a Day-1 slot. After that we shift you to the next available cohort, usually within 2-3 weeks.

May 12, 2026, per Adobe’s official release schedule. Alongside 2.4.9, Adobe ships security patches for every supported line: 2.4.8-p5, 2.4.7-p10, 2.4.6-p15, 2.4.5-p17, and 2.4.4-p18.

No. We use a blue-green deployment: the upgrade runs on a parallel staging environment, gets full QA, and then the DNS/load-balancer cuts over to the new version in under 30 seconds. Your live store keeps taking orders the entire time. We do schedule a 5-minute maintenance window for the final database sync, typically at 3 AM in your timezone.