Hyvä Migration

Magento to Hyvä Migration. Done Properly.

Move from Luma to Hyvä without losing SEO, without breaking your extensions, and without a six-month timeline. Fixed price, fixed timeline, by a team that does this every week.

Get a fixed-price quote Read the migration guide

50+

Hyvä migrations completed

6-10 wks

Typical timeline

+35pts

Avg Lighthouse lift

100%

URL preservation

What's actually included in a Hyvä migration

Hyvä Theme install + brand-system Tailwind config
Every storefront template re-platformed (home, PDP, PLP, search, cart, customer account, CMS blocks)
Hyvä-compatibility module per paid extension on the store
100% URL preservation + redirect plan for any URL that does change
Schema.org structured data carried over + extended (Product, Offer, Breadcrumb, FAQPage where applicable)
Lighthouse mobile tuned to 90+ before cutover
Pre-launch UAT on staging — real orders end-to-end with your team
Off-peak DNS cutover + 72-hour post-launch monitoring
Final handover doc covering theme config, custom modules, and a deploy runbook

What we won't lose during a Hyvä migration

Migrations done badly lose SEO, break checkout, and leave the merchant scrambling for weeks post-launch. The three hard rules:

URLs.Every URL preserved, every change 301'd. Search Console "Pages with redirect" report stays clean.
Structured data. Product / Offer / AggregateRating / Breadcrumb / FAQPage all carried over. Rich results stay eligible from day one.
Checkout integrations. Payment + shipping + fraud modules tested on staging with real orders before cutover. No customer hits a broken checkout.

Hyvä migration timeline at a glance

A standard Luma → Hyvä migration runs about 8-10 weeks from kickoff. The biggest variable is the extension list, not the catalogue size.

Week 1. Kickoff, design audit, extension inventory, Tailwind brand system.
Weeks 2-3. Header / footer / nav / PDP / PLP templates on Hyvä.
Weeks 4-5. Cart, checkout, customer account, CMS blocks. Every paid extension wrapped in a Hyvä compatibility module.
Week 6-7. Performance tuning. Lighthouse mobile 90+ as exit criteria.
Week 8. Staging UAT with your team. Real orders end-to-end. Bug-bash list closed.
Week 9. Cutover, off-peak. 72-hour monitoring.
Week 10. Post-launch tuning, indexation monitoring, final handover doc.

Hyvä migration — questions we get asked

How long does a Magento to Hyvä migration take?: Standard Luma → Hyvä migrations take 6-10 weeks for typical Magento stores, measured from kickoff to DNS cutover. The driver is extension count + design complexity, not catalogue size. Stores with 20+ paid extensions or heavy customisation land at the 10-12 week mark; clean Luma stores can finish in 6.
How much does a Hyvä migration cost?: Hyvä migrations start at £12k for a small Magento Luma store with a handful of extensions, and run to £35k for medium B2C with full design rebuild. Hyvä Commerce migrations (including Hyvä Checkout) sit at £35k-£90k. We quote fixed-price, fixed-timeline after a 30-minute scoping call.
Will a Hyvä migration affect my SEO?: Done properly, it improves it. We preserve every URL, redirect every legacy URL that's changed, retain all structured data, and typically lift Core Web Vitals (LCP / CLS / INP) by enough that Google's mobile-first index ranks the new pages higher than the old ones within 4-8 weeks. Migrations that hurt SEO are migrations done by teams that didn't take URL preservation seriously — that's the trap to avoid.
What happens to my paid Magento extensions after Hyvä migration?: Each extension needs a Hyvä compatibility module before its frontend renders correctly. Many vendors now ship their own — we install those first. For extensions without a vendor-provided compat, we write a custom one. The cost of compatibility work is included in the migration scope, not a surprise add-on later.
Can you migrate from Luma to Hyvä without downtime?: The build happens on staging; the cutover is a planned maintenance window of 30-60 minutes for DNS + cache flush + final order sync. Customers do not see a half-migrated site at any point. We do the cutover off-peak (UK Sunday 02:00 by default) and monitor for the first 72 hours.
Do I need Hyvä Commerce or just Hyvä Theme?: Most merchants start with Hyvä Theme alone — covers storefront, PDP, PLP, cart, and account. Add Hyvä Commerce when your checkout conversion is the bottleneck (Hyvä Checkout consistently lifts mobile completion by 8-15%) or when you want a single coherent design language across the storefront and customer-account.
What's the actual difference between Magento Luma and Hyvä?: Luma is the legacy Magento frontend — Knockout.js, RequireJS, LESS, heavy on PHP-rendered templates. Hyvä replaces all of that with a modern stack: Alpine.js for reactivity, Tailwind for CSS, and a simpler module pattern. The result is dramatically less JavaScript on the page, faster Time-to-Interactive, and a frontend codebase a current frontend engineer can read and ship on.

Related Hyvä services

Talk to a Hyvä specialist

30-minute scoping call. Fixed-scope, fixed-price quote within 48 hours. No forms, no sales sequence.

Book a call All services

What's actually included in a Hyvä migration

Hyvä Theme install + brand-system Tailwind config
Every storefront template re-platformed (home, PDP, PLP, search, cart, customer account, CMS blocks)
Hyvä-compatibility module per paid extension on the store
100% URL preservation + redirect plan for any URL that does change
Schema.org structured data carried over + extended (Product, Offer, Breadcrumb, FAQPage where applicable)
Lighthouse mobile tuned to 90+ before cutover
Pre-launch UAT on staging — real orders end-to-end with your team
Off-peak DNS cutover + 72-hour post-launch monitoring
Final handover doc covering theme config, custom modules, and a deploy runbook

What we won't lose during a Hyvä migration

Migrations done badly lose SEO, break checkout, and leave the merchant scrambling for weeks post-launch. The three hard rules:

URLs.Every URL preserved, every change 301'd. Search Console "Pages with redirect" report stays clean.
Structured data. Product / Offer / AggregateRating / Breadcrumb / FAQPage all carried over. Rich results stay eligible from day one.
Checkout integrations. Payment + shipping + fraud modules tested on staging with real orders before cutover. No customer hits a broken checkout.

Hyvä migration timeline at a glance

A standard Luma → Hyvä migration runs about 8-10 weeks from kickoff. The biggest variable is the extension list, not the catalogue size.

Week 1. Kickoff, design audit, extension inventory, Tailwind brand system.
Weeks 2-3. Header / footer / nav / PDP / PLP templates on Hyvä.
Weeks 4-5. Cart, checkout, customer account, CMS blocks. Every paid extension wrapped in a Hyvä compatibility module.
Week 6-7. Performance tuning. Lighthouse mobile 90+ as exit criteria.
Week 8. Staging UAT with your team. Real orders end-to-end. Bug-bash list closed.
Week 9. Cutover, off-peak. 72-hour monitoring.
Week 10. Post-launch tuning, indexation monitoring, final handover doc.

Hyvä migration — questions we get asked

How long does a Magento to Hyvä migration take?

Standard Luma → Hyvä migrations take 6-10 weeks for typical Magento stores, measured from kickoff to DNS cutover. The driver is extension count + design complexity, not catalogue size. Stores with 20+ paid extensions or heavy customisation land at the 10-12 week mark; clean Luma stores can finish in 6.

How much does a Hyvä migration cost?

Hyvä migrations start at £12k for a small Magento Luma store with a handful of extensions, and run to £35k for medium B2C with full design rebuild. Hyvä Commerce migrations (including Hyvä Checkout) sit at £35k-£90k. We quote fixed-price, fixed-timeline after a 30-minute scoping call.

Will a Hyvä migration affect my SEO?

Done properly, it improves it. We preserve every URL, redirect every legacy URL that's changed, retain all structured data, and typically lift Core Web Vitals (LCP / CLS / INP) by enough that Google's mobile-first index ranks the new pages higher than the old ones within 4-8 weeks. Migrations that hurt SEO are migrations done by teams that didn't take URL preservation seriously — that's the trap to avoid.

What happens to my paid Magento extensions after Hyvä migration?

Each extension needs a Hyvä compatibility module before its frontend renders correctly. Many vendors now ship their own — we install those first. For extensions without a vendor-provided compat, we write a custom one. The cost of compatibility work is included in the migration scope, not a surprise add-on later.

Can you migrate from Luma to Hyvä without downtime?

The build happens on staging; the cutover is a planned maintenance window of 30-60 minutes for DNS + cache flush + final order sync. Customers do not see a half-migrated site at any point. We do the cutover off-peak (UK Sunday 02:00 by default) and monitor for the first 72 hours.

Do I need Hyvä Commerce or just Hyvä Theme?

Most merchants start with Hyvä Theme alone — covers storefront, PDP, PLP, cart, and account. Add Hyvä Commerce when your checkout conversion is the bottleneck (Hyvä Checkout consistently lifts mobile completion by 8-15%) or when you want a single coherent design language across the storefront and customer-account.

What's the actual difference between Magento Luma and Hyvä?

Luma is the legacy Magento frontend — Knockout.js, RequireJS, LESS, heavy on PHP-rendered templates. Hyvä replaces all of that with a modern stack: Alpine.js for reactivity, Tailwind for CSS, and a simpler module pattern. The result is dramatically less JavaScript on the page, faster Time-to-Interactive, and a frontend codebase a current frontend engineer can read and ship on.