Magento upgrades

Magento 2.4 upgrades and Hyvä migration at a fixed price.

Patch releases, minor 2.4.x upgrades with PHP 8.x, upgrades from 2.3 or older, and Hyvä theme migrations. You get a written plan and a fixed quote after an audit, and the work happens on staging first.

Sound familiar?

The upgrade you keep postponing.

  • Your release line is out of standard support, or close to it.
  • PHP, Elasticsearch or MySQL on the server are reaching end of life.
  • Extensions block the upgrade, and nobody knows which ones.
  • The Luma frontend is slow and every change takes too long.

What’s included

Everything the upgrade touches, tested on staging.

  • Extension compatibility matrix

    Every module checked against the target release and PHP: update, replace, patch or remove.

  • Platform update

    PHP, OpenSearch, database and cache versions the target release expects.

  • Custom code fixes

    Deprecated APIs, plugins and preferences on core classes, composer patches.

  • Regression testing

    Checkout, customer accounts, search and every integration, tested on staging.

  • Planned release

    A low-traffic window, a written runbook and a tested rollback plan.

  • Hyvä migration

    Theme rebuilt with Tailwind and Alpine.js, extensions mapped to compatibility modules, a checkout plan.

Packages

Fixed-price packages.

Starting prices. The final price is set after the audit, once extensions and custom code are known.

  • Patch upgrade

    Apply the latest 2.4.x security and patch release (2.4.x-pN).

    from €300
  • Minor upgrade

    2.4.x to the current release, PHP 8.x and extensions included.

    from €1,000
  • Upgrade from 2.3 or older

    Larger version jumps, PHP and search engine included, planned after a deep audit.

    from €2,600
  • Hyvä migration

    Replace Luma with a Hyvä theme for a lighter, faster storefront.

    from €2,000
  • Deep audit

    Code, extensions and an upgrade plan. Credited towards the project.

    €490

Fixed-price projects: 50% upfront, 50% on delivery. Projects from €5,000 are split into milestones (40/30/30). Invoiced in EUR, paid by SEPA or SWIFT.

Typical engagements

What this usually looks like.

Example

A typical 2.4 upgrade

How an upgrade usually runs. Every store differs; the audit sets the real plan.

An illustrative scenario based on typical projects, not a specific client.

Situation
A B2C store on 2.4.4 with PHP 8.1, dozens of third-party extensions and security support coming to an end.
Approach
Audit, an extension compatibility matrix, the upgrade on staging, regression tests of checkout and integrations, then a release in a low-traffic window.
You get
An upgraded store, updated extensions and a runbook for the next upgrade.
Example

Hyvä migration with a staged checkout

When the storefront and the checkout move at different speeds.

An illustrative scenario based on typical projects, not a specific client.

Situation
A store on a supported 2.4 release with a customised Luma theme and several extensions with storefront output.
Approach
Extensions sorted into Hyvä-ready, compatibility module, rewrite or remove; the theme rebuilt with Tailwind and Alpine.js; the existing checkout kept through Hyvä’s Luma fallback as a first step.
You get
A Hyvä storefront, a cleaned-up extension list and a plan for the checkout as a second phase.

How we work

How a project runs: audit, quote, staging, release.

  1. Audit

    Free express audit, then a deep audit of code and extensions.

  2. Plan and quote

    A written plan and a fixed price. 50% upfront, 50% on delivery.

  3. Upgrade on staging

    Platform, Magento, extensions and code, step by step.

  4. Release and monitoring

    A planned release window, then a close watch on errors and orders.

Questions

Frequently asked.

Why are the prices “from”?

The effort depends on your extensions and custom code. The audit shows both, and then you get a fixed price for the project.

What is the difference between a patch and a minor upgrade?

A patch upgrade applies the latest security and patch release of your current line, for example 2.4.8-p4 to 2.4.8-p5. A minor upgrade moves to a newer line, for example 2.4.7 to 2.4.8, with new PHP and service versions, extension updates and custom code fixes.

Can a Hyvä migration be combined with an upgrade?

Yes, and it often makes sense. If the store is on an unsupported version, the upgrade comes first, because it may change your extension list anyway.

Is a Hyvä licence included?

The Hyvä Theme has been free and open source since November 2025. Hyvä Checkout and other Hyvä products are commercial and licensed separately, if you choose them.

How do payments work?

Fixed-price projects: 50% upfront and 50% on delivery. Projects from €5,000 are split into milestones of 40/30/30. The deep audit fee is credited towards the project.

Find out what your upgrade involves.

The free audit shows your version, patch level and the biggest risks.

Ask a questionAsk