Skip to content
FAQ topic 12 answers

Magento Upgrade Cost Calculator FAQ

How accurate the calculator is, what’s in vs. out of scope, DIY vs agency vs freelance, fixed vs hourly, timeline expectations, riskiest upgrade phases, Hyvä-alongside-upgrade pricing, version-skip rules, PHP 8.3 breakage, downtime, post-launch support.

All 12 answers

How accurate is this calculator?

The calculator output is a budgeting range, not a quote. The low to high spread (-20% / +50%) intentionally absorbs the things you can’t see from outside your codebase: undocumented customisations, vendor extensions that have gone silent, hidden cron-orchestrated integrations, and the dependency-resolution chaos that only surfaces when you actually run composer update.

To turn the calculator output into a hard number, run a paid audit. After the audit you get a fixed written quote.

Was this helpful?

What’s NOT included in the estimate?

The calculator covers code-side upgrade work only. It does not include:

  • Hosting / infra changes, PHP 8.3 upgrade on the server, MySQL 8.0 migration, OpenSearch, Redis 7, Varnish 7. If your hosting is managed (Cloudways, Nexcess, JetRails, MageMojo) this is usually free; if self-hosted, it is quoted separately.
  • Theme migration, Luma → Hyvä is a separate project. The calculator’s “Hyvä yes” toggle assumes you’re already on Hyvä and adds compat-checking cost.
  • New extension licences, if a vendor has gone silent and you need to swap to a different extension, the new licence cost is yours.
  • Adobe Commerce licence renewal, if you’re on Adobe Commerce, your licence cost is independent.
  • Content + design changes, Page Builder content rework, new homepage design, photo shoots, copywriting.
  • Data cleanup, deleting orphaned customers, archiving old orders, deduplicating SKUs. Done as a separate engagement if needed.
  • Post-launch retainer, calculator covers the upgrade itself. The 14-day bug-fix warranty on production deployments covers regressions in delivered scope. Ongoing retainer is separate.
Was this helpful?

Why so expensive, can I DIY the upgrade?

Yes, if your team has shipped a Magento upgrade in the last 12 months. No, if they haven’t.

The honest cost equation:

  • DIY in-house with experienced team: ~60% of the calculator number in cash, but 1.5-2x in calendar time. Worth it if you have a senior Magento dev on payroll.
  • DIY with a dev who’s never done a Magento upgrade: You’ll spend 2-3x the calculator number when you count the senior-dev hours wasted re-googling the same composer errors. Cheap DIY upgrades often end up costing more to fix than to do properly.
  • Hire a consultant for the audit only: Smartest middle path. Pay for a 1 to 3 day audit + written upgrade plan, hand it to your team, save the build cost.

Specific risks of DIY: missing a deprecated API surfaces in production a month later (when an obscure cron runs); an untested extension breaks checkout silently for 2-3% of customers; a forgotten db_schema.xml migration leaves stale columns indefinitely. These are the kinds of bugs that are expensive to chase later.

Was this helpful?

Agency vs freelancer, what’s the actual cost difference?

For Magento upgrades specifically:

  • Top-tier Magento agency (Vaimo, Born, Absolunet, Something Digital): the highest rates. PM + senior dev + QA + account manager.
  • Mid-tier agency: lower rates. Same roles, less overhead.
  • Senior Magento freelancer with Adobe certification: a fixed written quote. You’re directly paying the dev who’s writing the code.
  • Offshore / random freelancer: the lowest rates. I’d avoid for upgrades, the cost-of-mistakes math doesn’t work out.

The agency premium buys: 24/7 SLA, multiple parallel workstreams, depth of bench (someone’s on PTO, someone else picks up), and someone to sue if it goes badly. The freelance premium buys: direct line to the dev, faster decisions, no account-manager telephone game.

For a single-store upgrade with well-defined scope, freelance wins on cost and speed. For multi-region or B2B+DTC parallel upgrades, agency wins on bench depth.

Was this helpful?

Fixed-price vs hourly, which is safer for an upgrade?

Fixed-price is safer after a paid audit; hourly is safer during the audit. The pattern I default to:

  1. Audit hourly. I document every blocker, every risky extension, every custom module needing rework. Output is a written report.
  2. Upgrade fixed-price based on audit findings. I lock the number. If reality bites and a hidden customisation surfaces mid-build, I show you the line item and we agree before extending scope.
  3. Stabilisation after launch. The 14-day bug-fix warranty on production deployments covers regressions in delivered scope. New requests that come out of UAT are quoted separately.

Avoid two anti-patterns:

  • Pure hourly upgrade quote with no cap, the dev has zero incentive to be efficient. Pure hourly upgrades can balloon well past the first number.
  • “Fixed estimate” (i.e., fixed-price-but-actually-hourly), always overruns. If a quote uses the word “estimate” it’s hourly with a fig leaf.

Get the change-order policy in writing before you sign. Mine: any out-of-scope work gets a written line item before I touch it.

Was this helpful?

How long will my upgrade take in calendar time?

Calendar time, not effort time. Most upgrades fit one of these buckets, from shortest to longest:

  • 2.4.8 → 2.4.9 patch hop: Mostly composer + reindex + smoke-test. Best done in a planned maintenance window.
  • 2.4.6 → 2.4.9 minor jump: Two minor versions of deprecation work, full UAT cycle.
  • 2.4.4 → 2.4.9 multi-minor: The PHP 8.1 → 8.3 hop kicks in here, plus several waves of extension audits.
  • 2.4.0 → 2.4.9: Composer 1 → 2, OpenSearch migration, layout-XML schema cleanup, library deprecations.
  • 2.3.x → 2.4.9: Effectively a re-build. PHP 7 → 8.3, full Knockout audit, every extension re-validated, often a Hyvä migration tagging along.

B2B in scope, each extra storefront and an ERP integration (for the schema-handshake retest) all add calendar time. The timeline is set in the written quote, after we agree the scope. The calculator’s timeline output is the realistic elapsed time including UAT, not just dev hours.

Was this helpful?

What’s the riskiest part of an upgrade?

The riskiest parts, roughly in order:

  1. Third-party extensions that have gone silent. A Mageplaza / Aheadworks / random-marketplace extension hasn’t shipped a 2.4.9-compatible version, and the vendor isn’t replying. Mitigation: pre-audit the extension list, identify silent vendors early, plan swap-outs before upgrade kickoff.
  2. Custom checkout customisations. Custom JS in checkout, third-party payment plugins (Klarna / Affirm / Mollie), or custom shipping calculators. Even a clean composer-resolve can leave checkout broken in subtle ways. Mitigation: 100% of test orders run through staging before cutover.
  3. B2B Companies + quote workflows. Schema-tied to specific Magento versions; quote silently breaks if a column was renamed. Mitigation: validate company-record + quote-record integrity post-upgrade with a dedicated test plan.
  4. Reindex windows on huge catalogs. 100k+ SKU catalogs can take 6-8 hours to reindex on first post-upgrade run. Mitigation: schedule the reindex inside the maintenance window, don’t cutover until clean.
  5. SEO / URL-rewrite collisions. Upgraded code regenerates URL rewrites; old ones go stale. Mitigation: snapshot URL rewrites pre-upgrade, diff post-upgrade.
  6. Other, cron schedules, email-template syntax, custom queue consumers, etc.
Was this helpful?

Hyvä migration alongside the upgrade, what’s the extra cost?

Hyvä migration during the upgrade is cheaper than doing it later, because you’re already in the codebase, but it doubles the project surface area.

Combined is usually cheaper than sequential, but it makes the upgrade project longer and adds a lot of testing (Hyvä changes every storefront-facing template and every extension’s frontend hooks need re-validation). The timeline is set in the written quote, after we agree the scope.

Decision rule: combined wins if you’re already planning Hyvä in the next 12 months, and you have the budget + calendar runway. Sequential wins if upgrade is urgent (security patches, support deadline) or if Hyvä isn’t locked-in yet.

Both patterns work. Combined suits stores that want one project and one testing cycle; sequential suits stores where a single longer project is the bigger risk.

Was this helpful?

Can I skip 2.4.6 / 2.4.7 / 2.4.8 and go straight to 2.4.9?

Yes, Magento upgrades are cumulative, not stepped. You can compose-update from 2.4.4 → 2.4.9 in a single jump. Adobe explicitly supports skipping minor versions during the upgrade process.

What you cannot skip:

  • The deprecation work from each intervening version. If 2.4.5 deprecated \Zend_Date and 2.4.6 removed it, your custom code still needs to update. Skipping versions doesn’t skip deprecations, it just delivers them all at once at upgrade time.
  • The dependency cascade. Composer will resolve to the latest compatible versions of every dependency at once, which can mean cascade-failures across multiple modules. Doing one minor version at a time spreads the failure surface.
  • Database migrations. All data:upgrade patches between your current and target versions run sequentially, in order. You don’t skip them; they all execute on first setup:upgrade.

My recommendation by version:

  • 2.4.6+ → 2.4.9: jump direct, single-shot.
  • 2.4.4 → 2.4.9: jump direct, but allocate 50% extra UAT time.
  • 2.4.0 → 2.4.9: jump direct only if dev team is senior; otherwise step through 2.4.4 first.
  • 2.3.x → 2.4.9: step through 2.4.4 first. The PHP + composer + framework cascade is too risky to do in one shot.
Was this helpful?

PHP 8.3 requirement, what does it actually break?

Magento 2.4.8+ requires PHP 8.3. The most common breakages I see when teams bump from 8.1/8.2 → 8.3:

  • Dynamic property deprecation (PHP 8.2+, error in 8.3). Custom modules that set $this->something = $foo on a class without declaring the property break. Fix: declare every property explicitly, or use #[\AllowDynamicProperties] as a band-aid.
  • Implicit nullable parameter types deprecated. function foo(string $bar = null) now needs ?string $bar = null. Common in older custom modules and 2.3-era extensions.
  • Untyped properties / methods. Several Magento core classes added strict types in 2.4.8; any vendor module overriding them needs matching signatures.
  • Removed functions. utf8_encode() and utf8_decode() are gone (deprecated in 8.2). Use mb_convert_encoding() instead. Old extensions use them everywhere.
  • Random number generator changes. mt_srand() behaviour changed. Anything using PHP RNG for security tokens needs review (you should be using random_bytes anyway).
  • SimpleXML quirks. A few SimpleXML edge cases changed in 8.3. Layout-XML loaders sometimes need patches.

Pre-flight script before upgrade: run vendor/bin/phpcs --standard=PHPCompatibility --runtime-set testVersion 8.3 app/code/ over your custom code and audit every warning.

Was this helpful?

Downtime during upgrade, how long is the maintenance window?

Depends on your data volume and cutover strategy. The two patterns:

Blue-green cutover (zero-downtime): upgraded code runs on a parallel environment. Final data-sync, then DNS / load-balancer flip. Downtime: only the DNS propagation tail. Cost: roughly 2x the hosting bill during cutover prep. Recommended for stores above $2M annual GMV.

In-place upgrade (planned downtime): upgrade is run on production directly. The window grows with catalog size and order history, and at very large scale (500k SKUs, multi-region) blue-green is the better choice.

The downtime breakdown for in-place is mostly setup:upgrade (data patches running) + reindex + cache warm-up. Database migrations run in parallel where possible.

I always recommend running the upgrade dry-run on staging at production-data scale to measure exact timings before scheduling the maintenance window. Surprise reindex times are the #1 cause of overrun maintenance windows.

Was this helpful?

What’s your post-launch support like after upgrade?

Two phases, then optional retainer:

Phase 1, Stabilisation (first 14 days, included in upgrade quote):

  • Daily check-ins (Slack / email) for the first 7 days, every-other-day for the next 7.
  • Bug-fix work: the 14-day bug-fix warranty on production deployments covers regressions in delivered scope.
  • Performance monitoring: I track LCP, INP, error rates, conversion rate vs pre-upgrade baseline. If anything regresses, I diagnose and fix.
  • The rollback plan is agreed with you before launch.

Phase 2, Post-stabilisation (days 15-90, optional retainer):

  • Weekly check-in + monthly perf report.
  • Capped hours for new bug-fix work or small enhancements.
  • Security patch monitoring (I’ll apply 2.4.9-px patches as Adobe ships them).
  • Quarterly extension audit (catch newly-incompatible extensions before they bite).

Phase 3, Long-term ops (optional, separate engagement): Ongoing development retainer for stores that want a dedicated Magento dev relationship. Capped hours, monthly invoice, you can scale up/down.

I don’t lock anyone into a retainer after stabilisation. Most stores at $1M to $5M GMV don’t need one; most stores above $10M GMV do. You’ll know which you are by day 30.

Was this helpful?
Fixed quote Discuss the scope and next steps Get a fixed quote