Skip to main content
Talk to an expert
ServiceHyvä migration

Hyvä migration, planned to keep the store trading.

Migrating an existing Adobe Commerce or Magento frontend to Hyvä is a staged piece of work. The frontend rebuild, extension audit, theme gap analysis and checkout decision all sit in scope; the catalogue, ERP and operational boundary do not move. We plan migrations to keep the store trading throughout rather than relaunching in one event.
600+
Commerce projects
40+
Engineers · on staff
31
Years · systems behind commerce
1995
Founded
Contents · 6 sections
  1. 01What a Hyvä migration covers
  2. 02Selected case studies.
  3. 03How this platform fits the wider commerce estate.
  4. 04Questions we get asked.
  5. 05Clients we build for.
  6. 06Where this fits in the wider estate.
01 · What a Hyvä migration covers

What a Hyvä migration covers

Migration planning before build
Discovery, extension audit, theme gap analysis and a written delivery plan before any frontend rebuild is committed. The plan names what is in scope and what is not.
Extension and module audit
Every Magento extension reviewed for Hyvä compatibility, replacement or removal. Surprise extension work is the biggest Hyvä project risk.
Theme gap analysis
Existing frontend behaviour mapped against the new Hyvä theme: components, blocks, custom UI, third-party widgets and tracking.
Custom modules and frontend hooks
Custom modules that inject frontend behaviour reviewed and reshaped against Hyvä patterns rather than ported wholesale.
Staged rollout, not big-bang
Migration sequenced by domain, traffic share or template family so the store keeps trading. A single relaunch event is rarely the right shape.
Testing under real load
Functional, accessibility, performance and checkout testing under realistic load and traffic shape, not on a clean staging environment.
PIM, ERP and operational systems unchanged
Catalogue truth and commercial data stay where they live. The migration is a frontend change; the integration boundary is preserved.
Search, tracking and SEO continuity
URLs, structured data, sitemaps, redirects and tracking preserved so the migration does not silently cost organic traffic.
Honest "should you migrate" read
Where Hyvä is not the right next step, we say so. The deliverable is a senior, written read on the brief, not a sales pitch.
02 · Relevant iWeb work
03 · Platform fit and estate context

How this platform fits the wider commerce estate.

Fit against operational shape
Catalogue depth, trade complexity, branch logic and ERP integration named honestly before the platform decision is fixed, not assumed from a vendor demo.
Integration boundary with ERP
ERP owns commercial data, pricing and stock. The commerce platform reads the boundary through governed APIs; the boundary itself is the most important design decision in the estate.
PIM as the catalogue system of record
Deep catalogue governance lives in PIM (Akeneo, Salsify or similar). The commerce platform reads from PIM rather than re-modelling product data in the storefront.
OMS and fulfilment surface
Order management, partial dispatch, returns and customer-visible order state live in operational systems. The platform reads what operations actually did.
Search and merchandising
Native search plus specialist engines (Algolia, Constructor.io) assessed against the actual query mix, not a vendor benchmark. Relevance is a continuous activity.
B2B and trade behaviour
Account-only catalogues, customer-specific pricing, depot stock, quote-to-cart and partial dispatch modelled inside the platform rather than patched at the storefront.
Multi-store and multi-territory
Brand, market and territory storefronts modelled with shared catalogue, pricing and operations rather than parallel sites that drift apart.
Total cost over five years
Licence, hosting, engineering and support modelled honestly across the lifecycle, not just year one. The cheap year-one platform is often the expensive five-year one.
Headless and composable trade-offs
Headless or composable storefronts where they earn their place, not as a default. The trade-off between optionality and integration surface is named upfront.
Operational ownership and runbook
Long-term support, releases and integration ownership inside a UK agency that runs platforms day to day, with a written runbook the on-call team can act on.
Replatform sequencing
Where a platform move is on the table, sequencing by domain, traffic share or territory keeps trading live throughout. Big-bang relaunches are rarely the right shape.
Honest "do not move" advice
Where the existing platform is the right answer, iWeb says so on the record. A senior, written read on the brief is the deliverable, not a sales pitch.
04 · Questions we get asked

Questions we get asked.

How long does a Hyvä migration take?

It depends on extension count, catalogue depth and B2B behaviour. A short discovery gives a realistic delivery shape before any build is committed.

Will the migration break our SEO?

Only if URLs, structured data, redirects and tracking are not handled. We plan continuity up front so organic traffic does not silently drop.

Do we have to relaunch the whole site at once?

No. Migration is sequenced by domain, traffic share or template family so the store keeps trading rather than going dark for a relaunch.

What happens to our checkout during migration?

Hyvä Checkout is its own decision inside the migration plan. Many merchants keep Magento checkout on the first cut and revisit checkout separately.

Is iWeb an official Hyvä partner?

We work as experienced Hyvä developers. Official partnership or accreditation is not claimed unless it is set out in our public credentials.

How does iWeb choose between platforms?

Against operational shape: catalogue depth, trade complexity, ERP integration, multi-territory rules and five-year cost. The decision is written down with trade-offs, not assumed from a vendor demo.

Where does ERP integration sit in the platform decision?

It is a primary input. Some platforms make ERP integration straightforward, some make it expensive. iWeb names the trade-off rather than hiding it.

Does iWeb deliver headless or composable storefronts?

Where they earn their place. The trade-off between optionality and integration surface is named upfront; composable is not a default.

How is search handled on this platform?

Native search where the query mix supports it; specialist engines (Algolia, Constructor.io) where the catalogue, volume or merchandising appetite justify them. Relevance is a continuous activity.

Where does PIM sit relative to the commerce platform?

PIM owns catalogue truth (attributes, variants, assets, channel readiness). The commerce platform reads from PIM rather than re-modelling deep product data in the storefront.

Can iWeb take over an existing build on this platform?

Yes, where the brief fits. iWeb will give a senior, written read on what is working, what needs remediation and what is honestly fixable, and the first month on support stays deliberately conservative on change.

How does iWeb size a five-year total cost picture?

Licence, hosting, engineering and support across the lifecycle, including the integration surface and operational ownership. The headline year-one number is rarely the honest comparison.

Accreditations & assurance
Gold Commerce Partner
Specialised in Commerce & AI
ISO certified
27001 · 9001 · 42001
Cyber Essentials Plus
Independently verified security
WCAG 2.2 AA
Accessibility embedded by design
Employee-owned
The same team, long term
Next step

Talk to a Hyvä developer

Send the brief. You'll get a written response from a senior expert on the platform, ERP and operational realities we'd look at first, not a pitch deck.
Talk to an expertor see luma to hyvä migration →