Magento 2 to Hyvä Migration: Step-by-Step Plan and Timeline

A Magento 2 to Hyvä migration runs in five stages: audit and module inventory, theme scaffolding, component rebuild (PDP/PLP/cart), checkout migration, and QA plus launch. For a mid-size store this is typically 4 to 8 weeks, with checkout and third-party Knockout modules driving most of the cost.

Key takeaways

• Migration is staged, not a rewrite: audit → scaffold → rebuild → checkout → QA/launch.
• Timeline: ~4-8 weeks for a mid-size store; complexity scales with custom + third-party UI.
• The two risk centers are checkout and any Knockout-only third-party module.
• Hyvä runs alongside Luma during the build, so you migrate without freezing the store.

Stage 1 — Audit and module inventory

List every theme customization and every module that ships frontend (Knockout) UI. This inventory determines scope and risk. Output: a component-by-component rebuild plan and a "keep / rebuild / replace" decision per third-party module.

Stage 2 — Theme scaffolding

Install Hyvä, set up Tailwind config to match the brand, and stand up the base layout. Hyvä installs as a separate theme, so Luma keeps serving production while you build.

Stage 3 — Component rebuild (PDP, PLP, cart)

Rebuild product detail, product listing, and cart as Hyvä/Alpine components. This is the bulk of visible work and where performance gains are locked in by shipping minimal JS.

Stage 4 — Checkout migration

Checkout is the highest-risk surface. Migrate to a Hyvä-compatible checkout and re-integrate payment and shipping modules, testing every path (guest, logged-in, multi-address, each payment method).

Stage 5 — QA and launch

Cross-device QA, Core Web Vitals verification, and a staged cutover. Validate analytics, structured data, and redirects before flipping the theme live.

See the Hyvä vs Luma performance comparison for the "why", the Velgrina case study for proof, and Magento / Hyvä Engineering to scope it. Request a quote.

Frequently asked questions

How long does a Magento 2 to Hyvä migration take?

For a mid-size store, typically 4 to 8 weeks. The timeline scales with the number of custom theme components and third-party modules that ship Knockout UI, with checkout being the largest single piece.

Can I migrate to Hyvä without taking my store offline?

Yes. Hyvä installs as a separate theme that runs alongside Luma, so the live store keeps serving while the Hyvä build proceeds. You only cut over at launch.

What is the riskiest part of a Hyvä migration?

Checkout and any third-party module that only provides a Knockout.js UI. These need careful rebuilding and full path testing across payment and shipping methods.

What are the stages of a Hyvä migration?

Five stages: audit and module inventory, theme scaffolding, component rebuild (PDP/PLP/cart), checkout migration, and QA plus staged launch.