How long does a Hyvä migration take?

Eight weeks for a single-brand store on Magento 2.4.x with a moderately customised Luma theme. Six weeks for a clean default-theme migration. Twelve weeks for multi-brand or heavily-customised storefronts. We share the week-by-week timeline as part of the discovery call so you can plan stakeholder reviews.

What does the Core Web Vitals guarantee cover?

If your post-migration LCP, INP or CLS scores are worse than the week-1 baseline on any of the top-five surfaces, we keep working at no extra cost until they are better. If we still cannot beat the baseline within four extra weeks, we refund 50% of the programme fee.

Do we have to stop the existing store during migration?

No. Hyvä is built alongside the existing theme on a staging environment. Production traffic continues uninterrupted. The cutover at week 8 is the only moment of risk and we run it inside a planned maintenance window with a tested rollback path.

Can you migrate Luma-only third-party modules?

Modules with a Hyvä-compatible release are migrated as part of the programme. Luma-only modules without a Hyvä equivalent need either a swap to a Hyvä-compatible alternative or a custom compatibility layer; we quote that separately during discovery so you can decide.

What if our team wants design changes during the migration?

We accommodate one round of in-flight design refinement during week 4 at no extra cost. Larger redesigns become a separate engagement quoted after the migration ships; trying to redesign and migrate at the same time always costs more than doing them in sequence.

Do you provide post-launch support?

Two weeks of engineering support is included in the programme fee. That covers any issues that surface in real customer traffic after cutover. After week 10 you can move onto our Magento Support and Maintenance retainer or just open ad-hoc tickets.

How much does it cost?

Single-brand standard-customisation migrations are a fixed price in the mid-five-figure GBP range. We share the exact number after a 30-minute discovery call where we look at your current theme. Multi-brand or heavily-customised projects get a longer fixed quote based on the catalogued customisation list.

URL structure, meta tags, structured data and canonical tags are preserved exactly. Page speed improves, which Google rewards. We have not seen a Hyvä migration cause an SEO drop in any of the 50+ we have shipped to date.

Hyvä Development

هجرة ثيم Hyvä

قلل من وقت تحميل متجرك على الهواتف المحمولة بنسبة 60 إلى 80 في المئة. ثمانية أسابيع، سعر ثابت، فوز في Core Web Vitals أو استرداد أموالك.

Programme length: 8 weeks
CWV target: All green
Done to date: 50+ migrations
Guarantee: CWV or refund

Overview

What it is.

تخسر معظم متاجر Magento الزوار الذين دفعت أكثر للحصول عليهم، وهم الزوار عبر الهواتف المحمولة، لأن واجهة المتجر بطيئة. هجرة Hyvä تحل هذه المشكلة. نحن ننقل متجرك من واجهة Luma القديمة إلى Hyvä، واجهة المتجر الحديثة لـ Magento. نفس الخلفية، نفس المنتجات، نفس الإدارة، نفس الوحدات حيثما كان ذلك متوافقًا. ثمانية أسابيع من بدء المشروع حتى الإطلاق. سعر ثابت. إذا لم تكن Core Web Vitals أفضل بشكل ملحوظ في النهاية، ستحصل على أموالك. لقد قمنا بشحن أكثر من 50 هجرة Hyvä والنمط الآن أصبح مملًا.

What you get

Deliverables.

Full Hyvä theme migration of the storefront, header to footer
Migration of every customisation from the existing theme (catalogued and signed off in week 1)
AlpineJS state layer for interactive components (cart drawer, filters, mini-search)
Tailwind design tokens matched to your existing brand palette
Performance baseline before migration starts (Lighthouse + WPT + CrUX)
Performance baseline after migration on the same surfaces with delta report
QA sign-off on top-20 customer journeys (cart, checkout, account, search, filtering)
Composer-managed deployment with rollback plan
Two weeks of post-launch engineering support included

Honest limits

What it isn't.

Backend module conflicts may need separate remediation work
We do not migrate Luma-only third-party modules without a Hyvä-compatible equivalent
Multi-brand or multi-store stores get a longer fixed quote after discovery

Not sure if it's a fit? Email us. We'll tell you straight.

How it works

From inquiry to handover.

01
1. Discovery (Week 1)
Two-day audit of the current theme. We catalogue every customisation and confirm scope. Performance baseline captured here so the after-shot is comparable.
02
2. Foundation (Week 2)
Hyvä installed in a staging environment alongside the existing theme. Design tokens, type scale and component library scaffolded against your brand.
03
3. Build (Weeks 3-5)
Pages rebuilt in the agreed order: home, category, product, cart, checkout, account. Each page reviewed before moving on. AlpineJS state added for the interactions that need it.
04
4. Customisations (Week 6)
Every catalogued customisation from week 1 ported. Sign-off from your team on each before we move to QA.
05
5. QA + performance (Week 7)
Top-20 journeys QA passes. Performance re-baselined. Any regression against the week-1 baseline fixed before launch.
06
6. Launch + support (Week 8)
Production cutover with rollback plan. Two weeks of included engineering support for any issues that surface in real customer traffic.

Frequently asked

Questions we get from people about to book.

How long does a Hyvä migration take?: Eight weeks for a single-brand store on Magento 2.4.x with a moderately customised Luma theme. Six weeks for a clean default-theme migration. Twelve weeks for multi-brand or heavily-customised storefronts. We share the week-by-week timeline as part of the discovery call so you can plan stakeholder reviews.
What does the Core Web Vitals guarantee cover?: If your post-migration LCP, INP or CLS scores are worse than the week-1 baseline on any of the top-five surfaces, we keep working at no extra cost until they are better. If we still cannot beat the baseline within four extra weeks, we refund 50% of the programme fee.
Do we have to stop the existing store during migration?: No. Hyvä is built alongside the existing theme on a staging environment. Production traffic continues uninterrupted. The cutover at week 8 is the only moment of risk and we run it inside a planned maintenance window with a tested rollback path.
Can you migrate Luma-only third-party modules?: Modules with a Hyvä-compatible release are migrated as part of the programme. Luma-only modules without a Hyvä equivalent need either a swap to a Hyvä-compatible alternative or a custom compatibility layer; we quote that separately during discovery so you can decide.
What if our team wants design changes during the migration?: We accommodate one round of in-flight design refinement during week 4 at no extra cost. Larger redesigns become a separate engagement quoted after the migration ships; trying to redesign and migrate at the same time always costs more than doing them in sequence.
Do you provide post-launch support?: Two weeks of engineering support is included in the programme fee. That covers any issues that surface in real customer traffic after cutover. After week 10 you can move onto our Magento Support and Maintenance retainer or just open ad-hoc tickets.
How much does it cost?: Single-brand standard-customisation migrations are a fixed price in the mid-five-figure GBP range. We share the exact number after a 30-minute discovery call where we look at your current theme. Multi-brand or heavily-customised projects get a longer fixed quote based on the catalogued customisation list.
Will my SEO drop?: URL structure, meta tags, structured data and canonical tags are preserved exactly. Page speed improves, which Google rewards. We have not seen a Hyvä migration cause an SEO drop in any of the 50+ we have shipped to date.

Ready to start?

Tell us about your project.

A member of our team reads every message. Replies within one business day. No sales call required.

See all services

Hyvä Development

هجرة ثيم Hyvä

Programme length: 8 weeks
CWV target: All green
Done to date: 50+ migrations
Guarantee: CWV or refund

Overview

What it is.

What you get

Deliverables.

Full Hyvä theme migration of the storefront, header to footer
Migration of every customisation from the existing theme (catalogued and signed off in week 1)
AlpineJS state layer for interactive components (cart drawer, filters, mini-search)
Tailwind design tokens matched to your existing brand palette
Performance baseline before migration starts (Lighthouse + WPT + CrUX)
Performance baseline after migration on the same surfaces with delta report
QA sign-off on top-20 customer journeys (cart, checkout, account, search, filtering)
Composer-managed deployment with rollback plan
Two weeks of post-launch engineering support included

Honest limits

What it isn't.

Backend module conflicts may need separate remediation work
We do not migrate Luma-only third-party modules without a Hyvä-compatible equivalent
Multi-brand or multi-store stores get a longer fixed quote after discovery

Not sure if it's a fit? Email us. We'll tell you straight.

How it works

From inquiry to handover.

01
1. Discovery (Week 1)
Two-day audit of the current theme. We catalogue every customisation and confirm scope. Performance baseline captured here so the after-shot is comparable.
02
2. Foundation (Week 2)
Hyvä installed in a staging environment alongside the existing theme. Design tokens, type scale and component library scaffolded against your brand.
03
3. Build (Weeks 3-5)
Pages rebuilt in the agreed order: home, category, product, cart, checkout, account. Each page reviewed before moving on. AlpineJS state added for the interactions that need it.
04
4. Customisations (Week 6)
Every catalogued customisation from week 1 ported. Sign-off from your team on each before we move to QA.
05
5. QA + performance (Week 7)
Top-20 journeys QA passes. Performance re-baselined. Any regression against the week-1 baseline fixed before launch.
06
6. Launch + support (Week 8)
Production cutover with rollback plan. Two weeks of included engineering support for any issues that surface in real customer traffic.

Frequently asked

Questions we get from people about to book.

How long does a Hyvä migration take?: Eight weeks for a single-brand store on Magento 2.4.x with a moderately customised Luma theme. Six weeks for a clean default-theme migration. Twelve weeks for multi-brand or heavily-customised storefronts. We share the week-by-week timeline as part of the discovery call so you can plan stakeholder reviews.
What does the Core Web Vitals guarantee cover?: If your post-migration LCP, INP or CLS scores are worse than the week-1 baseline on any of the top-five surfaces, we keep working at no extra cost until they are better. If we still cannot beat the baseline within four extra weeks, we refund 50% of the programme fee.
Do we have to stop the existing store during migration?: No. Hyvä is built alongside the existing theme on a staging environment. Production traffic continues uninterrupted. The cutover at week 8 is the only moment of risk and we run it inside a planned maintenance window with a tested rollback path.
Can you migrate Luma-only third-party modules?: Modules with a Hyvä-compatible release are migrated as part of the programme. Luma-only modules without a Hyvä equivalent need either a swap to a Hyvä-compatible alternative or a custom compatibility layer; we quote that separately during discovery so you can decide.
What if our team wants design changes during the migration?: We accommodate one round of in-flight design refinement during week 4 at no extra cost. Larger redesigns become a separate engagement quoted after the migration ships; trying to redesign and migrate at the same time always costs more than doing them in sequence.
Do you provide post-launch support?: Two weeks of engineering support is included in the programme fee. That covers any issues that surface in real customer traffic after cutover. After week 10 you can move onto our Magento Support and Maintenance retainer or just open ad-hoc tickets.
How much does it cost?: Single-brand standard-customisation migrations are a fixed price in the mid-five-figure GBP range. We share the exact number after a 30-minute discovery call where we look at your current theme. Multi-brand or heavily-customised projects get a longer fixed quote based on the catalogued customisation list.
Will my SEO drop?: URL structure, meta tags, structured data and canonical tags are preserved exactly. Page speed improves, which Google rewards. We have not seen a Hyvä migration cause an SEO drop in any of the 50+ we have shipped to date.

Ready to start?

Tell us about your project.

A member of our team reads every message. Replies within one business day. No sales call required.

See all services

هجرة ثيم Hyvä

What it is.

Deliverables.

What it isn't.

From inquiry to handover.

1. Discovery (Week 1)

2. Foundation (Week 2)

3. Build (Weeks 3-5)

4. Customisations (Week 6)

5. QA + performance (Week 7)

6. Launch + support (Week 8)

Questions we get from people about to book.

Tell us about your project.

هجرة ثيم Hyvä

What it is.

Deliverables.

What it isn't.

From inquiry to handover.

1. Discovery (Week 1)

2. Foundation (Week 2)

3. Build (Weeks 3-5)

4. Customisations (Week 6)

5. QA + performance (Week 7)

6. Launch + support (Week 8)

Questions we get from people about to book.

Tell us about your project.