Hyvä Migration

We move Magento 2 and Adobe Commerce stores from Luma to Hyvä. We’re a Hyvä Silver Partner, and our lead developer is Adobe-certified, with four years of building on Hyvä.

A Hyvä migration replaces what your customers see and leaves the rest of Magento alone. Your products, customers, orders, admin and integrations stay put. The frontend that loads over 200 JavaScript and CSS files on every page goes, and the one that replaces it loads two files and about 0.2MB.

Most of the risk sits in two places: your extensions, and what happens to your rankings on launch day. We deal with both before we quote, so you know what you’re paying for.

Book my NNP Workshop Review my site for free

The frontend changes. Everything behind it stays.

What stays

Your Magento or Adobe Commerce install stays, along with your catalogue, customers, order history and admin. So do the integrations into your ERP, warehouse, PIM and payment providers. Your URLs normally stay the same as well, because the same Magento store is still serving the pages, and your team keeps working in the admin they already know.

What changes

The theme, templates and styling are rebuilt on Tailwind CSS and Alpine.js, and the checkout moves to Hyvä Checkout, which we’ve used on every Hyvä site we’ve built. Any extension that puts something on the page, like search, reviews, product options or promotions, needs a Hyvä-compatible version. And the page weight drops from somewhere between 1.5 and 2MB on Luma to about 0.2MB.

Because nothing behind the frontend moves, a migration carries far less risk than a replatform, and nobody on your team has to learn a new system. If you’re still weighing up the two themes, our Hyvä vs Luma comparison covers when each one makes sense.

Google ranks what it can read on the page, and a new frontend rewrites all of it. So the SEO work happens during the build, with the launch-day checks on top.

Before we start, we crawl the live site and record every indexable URL, page title, meta description, heading, canonical tag and piece of structured data. The Hyvä build has to reproduce all of it, and we crawl the staging site and compare the two before launch. Where a URL does change, for example when category paths or layered navigation get tidied up, it gets a 301 redirect mapped in advance.

We also check product, review and breadcrumb schema, image alt text and internal links, and make sure the filtered pages you’ve kept out of the index stay out of it. After launch we watch Search Console and fix anything that drops, rather than waiting for a monthly report to tell you.

A lighter frontend also gives you a far better starting point on Core Web Vitals, which feed into how Google ranks your pages.

A Hyvä migration can go live in as little as six weeks. Most take two to three months, because most include new UX and design built around what the store needs to do next, and that’s the part worth spending time on.

It costs less than a new site, which starts at £46,000 + VAT with a Hyvä frontend, because your backend, data and integrations don’t need rebuilding.

We quote a fixed price once the extension audit is done. For what moves that number, and what the Hyvä licences cost, read how much a Hyvä build costs.

We’d rather tell you now than sell you a migration you don’t need.

Hold off if you’re likely to leave Magento in the next year or so, because a new frontend on a platform you’re about to leave is money you won’t get back. Hold off, too, if the store depends on niche extensions with no Hyvä version and no alternative, at least until you’ve priced rebuilding them. And if your site already passes Core Web Vitals on mobile and you’re not changing the design this year, the money will pay back sooner somewhere else, like the checkout or on-site search.

If the backend is part of the problem (an old Magento version, or custom code stacked up by several agencies), a new frontend won’t fix it on its own. The NNP Workshop is where we work out which of those you’ve got.