Roll Out Hyvä Across Magento Stores

How to Roll Out Hyvä Across Magento Stores by Market

Ecommerce replatforming
7 min read Published: Last Updated:
Ecommerce replatforming
Multi-Store Magento to Hyvä Migration Plan

Summary

Key takeaways

  • An international Magento operator can move to Hyvä one market at a time. Release Hyvä to one eligible store view or website, keep a known-good path for neighboring storefronts and expand only when the pilot produces evidence the next market can use.
  • Choose the pilot by the workflows it covers, not by traffic. The best pilot is the smallest market that exercises the buying journeys the other markets depend on.
  • A low-traffic store view with a different payment provider or no trade accounts leaves important routes untested, even if it uses the same currency.
  • Hyvä and Luma store views can coexist on one Magento instance, but shared modules, caches, checkout settings and account scope can still link markets together.
  • Map the Magento scope hierarchy before calling any storefront isolated. Websites, stores and store views can share customer accounts, base currency and transaction configuration.
  • Theme fallback and store-view deployment are separate mechanisms. If the pilot uses both, for example Hyvä for the catalog and Luma for checkout, verify both in the same transaction.
  • A rollback must work at the same level at which the release can break, and it must preserve placed orders, payment references and queued export events.
  • A captured payment with no order, a duplicate order export or a wrong trade price is an immediate reason to pause expansion.
  • Longer-term results show what to measure over several months. Gabriel & Co. reported 42% lower page weight and a 28% relative conversion increase after its migration and follow-up work.
  • The working test before expansion is a completed, acknowledged order in both the pilot market and a neighboring store.

When this applies

This guidance is for merchants that run several websites, stores or store views on one Magento Open Source or Adobe Commerce installation and want to move from Luma or another storefront to Hyvä without stopping trade. It fits international operators with different languages, currencies, payment gateways, tax rules and carriers per market, and businesses that run consumer storefronts alongside trade or retailer portals that share accounts, contract catalogs and ERP or OMS integrations. It is most useful when the team needs to decide which market goes first, what must be proven before the next wave and how to roll back a single market without losing orders or search visibility.

When this does not apply

A phased, market-by-market rollout adds little for a single-storefront Magento site, where one well-tested release is usually simpler. It is also not the right approach when Hyvä is not the target, for example if the store is moving to Adobe Commerce as a Cloud Service or replatforming completely. If the installed versions or modules cannot support Hyvä and Luma store views side by side, or if shared modules mean that a change in one market always affects the others, the release has to be planned for the wider scope instead. Finally, project results such as page weight, conversion or LCP gains come from specific engagements with their own baselines, so they should not be used as targets for a short pilot.

Checklist

  1. Map the Magento hierarchy of websites, stores and store views with their domains, locales and root categories.
  2. Record the base and display currency, payment gateway, tax, shipping and guest checkout rules for each market.
  3. Note whether customer accounts are shared globally or scoped by website, along with contract catalogs and trade roles.
  4. List the OMS or ERP endpoints, stock sources, carrier labels and retry owners each market depends on.
  5. Inventory extensions by the interaction they affect and the store views that use them.
  6. Choose the smallest pilot market that exercises the buying journeys the other markets depend on, then check its traffic and exposure.
  7. Assign Hyvä at the pilot store view or website and set a website-level theme as recommended in Hyvä’s installation guidance.
  8. Decide whether checkout uses Hyvä or a Luma fallback, and test both rendering paths in the same transaction.
  9. Run guest and returning-customer orders in both the pilot and a neighboring store, plus a market-switch journey where supported.
  10. Confirm that the charge currency and amount match across the storefront, the payment gateway and the order export.
  11. Check that trade buyers see their assigned terms and can recover their order history.
  12. Save examples of category, product, CMS and alternate-language URLs, then compare status codes, canonicals, hreflang and sitemaps after release.
  13. Define hard stop criteria for payments, duplicate exports and wrong prices, and rehearse rollback while preserving orders and queued exports.
  14. On release day, reconcile payments and order exports and have operations trace every live smoke-test order.
  15. Review checkout completion and real-user Core Web Vitals against a comparable baseline before approving the next wave.

Common pitfalls

  • Choosing the pilot market only because it has low traffic, even though it skips payment, tax or trade-account workflows used elsewhere.
  • Assuming a store view is isolated when it shares customer accounts, base currency, modules or caches with other markets.
  • Forgetting to set a website-level theme when Hyvä is assigned at store or store-view level.
  • Testing only the pilot storefront and not a neighboring Luma store that shares order and integration services.
  • Combining theme fallback and store-view deployment without testing both in one complete transaction.
  • Planning a rollback that resets the theme but loses placed orders, payment references or queued export events.
  • Expanding to the next market while a captured payment without an order, a duplicate export or a wrong trade price is still unresolved.
  • Judging a short pilot on long-term conversion or page weight gains instead of on order and integration correctness.
  • Leaving hreflang, canonical tags and sitemaps unchecked for alternate-language URLs after the release.
  • Keeping the extension inventory as a raw module list instead of linking each module to the interaction at risk and the store views that use it.

Gabriel & Co. kept trading while Elogic Commerce moved its Adobe Commerce storefront to Hyvä. The New York jewelry brand ran a consumer store and a retailer portal with six integrations for product data, fulfillment and order processing. Elogic Commerce completed the cutover with zero production downtime and followed it with three to four months of structured performance work. Gabriel & Co. case study

An international Magento operator can take the same principle one step further. Elogic Commerce recommends starting with the smallest market that exercises the buying journey the other markets depend on. Release Hyvä to one eligible store view or website. Keep a known-good path for neighboring storefronts, verify the shared order and integration services, and expand only once the pilot produces evidence that the next market can use.

A small market is useful when it resembles the larger one. A low-traffic view that sells in the same currency but uses a different payment provider or has no trade accounts leaves important routes untested. Pick the pilot by the workflows it covers. Check traffic and exposure after you establish that the order paths are representative.

The multi store rollout moves from a measured baseline to one pilot market, through a review of live evidence, and into the next wave.
A phased Hyvä rollout: measure a baseline, release one pilot market, review live order and performance evidence, then expand to the next wave.

Hyvä documents that Hyvä and Luma store views can coexist. Plan the effect of shared modules and account scope before choosing a pilot. Hyvä layout documentation

Pick the right scope before choosing a country

Magento has a global, website, store and store-view hierarchy. A store can have its own root catalog category. A store view commonly carries a language and display currency. The base currency used for transactions can be set at website scope on a multisite installation. Customer accounts can be shared globally or scoped to a website. Several apparent markets can therefore depend on the same account and transaction configuration. Put that relationship on paper before calling any storefront isolated. Adobe Commerce scope hierarchy · Currency configuration · Customer account settings

Where the installed versions and modules support it, Hyvä and Luma can run on different store views of the same Magento instance. Hyvä’s installation documentation advises setting a website-level theme as well when assigning Hyvä at the store or store-view level. Treat that as part of the configuration you rehearse. Run a guest order and a returning-customer order on both sides of the pilot. Test a market-switch journey on implementations that support it so the customer reaches the expected catalog, account and currency. Hyvä theme installation

What to mapWhat to recordWhat must hold in the pilot
Magento scopeWebsite, store, store view, domains, locale and root categoryPilot theme resolves on the intended storefront and shared services still resolve on neighboring views.
Checkout mixBase and display currency, local gateway, tax, shipping and guest rulesExpected charge currency and amount match storefront, gateway and order export.
Trade buyersAccount share scope, contract catalogs and rolesBuyers see their assigned terms and can recover their order history.
Organic discoveryIndexable URLs, canonicals, hreflang links, sitemaps and robots rulesEligible URLs return the expected status and language relationships.
Operational handoffOMS or ERP endpoint, stock source, carrier labels and retry ownerA test order creates one acknowledged fulfillment record.

Map purpose-built mechanisms separately. Theme fallback can give a route such as checkout a Luma rendering path while the catalog uses Hyvä. Store-view deployment decides where the new theme is active. If the pilot depends on both, verify both in the same transaction. A release needs to be reversible at the same level at which it can break. Hyvä documentation on Luma checkout

Review the storefront as real traffic reaches it

Elogic Commerce’s Gabriel & Co. case reports a 42% decrease in page weight and a 28% relative increase in conversion after the migration and associated changes. Organic traffic rose 36% during the subsequent optimization period. The program included image and caching work, checkout simplification and ongoing refinements. It gives teams a good example of what to measure over several months while a short pilot has a different job. It needs to expose breakage quickly enough to contain it. Gabriel & Co. results

Kiwop’s Loviux case gives a separate view of scale. Its Magento site supported 15 store views, nine languages and more than 12,000 SKUs. Kiwop reported mobile LCP of 4.2 seconds before and 1.8 after its Luma-to-Hyvä work. The same project incorporated custom language fallback and checkout work. Those figures are project observations with their own baselines and test method. Kiwop’s Loviux architecture

Gabriel and Co. page weight moves from an indexed 100 to 58. Kiwop reports Loviux mobile Largest Contentful Paint moving from 4.2 to 1.8 seconds.
These two panels show different measures from separate project reports. Gabriel & Co. · Loviux

During the pilot, read order events and customer experience data at their natural speed. Reconcile payments and order exports on release day. Use scripted journeys to check each launch-critical scenario, then review live event data at a comparable baseline by device and payment method. Measure real-user speed at the 75th percentile when there is enough traffic. Google’s Good Core Web Vitals thresholds are LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less. Keep the laboratory checks useful for diagnosis and collect real-user data for the post-launch assessment. Google Web Vitals · Elogic Commerce Magento performance optimization

Define the decision to expand or roll back

A launch owner should be able to name exactly what they can restore. For a theme assignment problem, restore the previous assignment for the approved scope, refresh the appropriate caches and retest the route. If a shared module changed, the affected scope can include several views. Rehearse how the engineering team will revert a release while preserving placed orders, payment references and queued export events. An order ledger and an export reconciliation are part of the cutover record.

Use hard criteria for money and order errors. A captured payment with no order, a duplicate order export or a wrong trade price is an immediate reason to pause expansion. Check localized order totals from the storefront to the fulfillment record. Have a named owner clear each failure before the next wave.

Compare noisy signals with a baseline. Review the pilot’s checkout completion against the same market and payment mix, and set the acceptable movement with the merchant during release planning. For a simple structured test, require all critical rows to pass in staging and have operations trace every live smoke-test order. A thin live sample leaves the team more dependent on the scripted evidence.

Keep an SEO record by URL type. Save examples of the category, product, CMS and alternate-language URLs the market depends on. Compare the status, canonical target, reciprocal hreflang and sitemap membership after the release. If URLs do change in the project, include the approved redirects in the check. Google localized page guidance

In a public r/Magento discussion about moving from Luma to Hyvä, practitioners raised frontend customization and implementation scope as part of the migration conversation. Use that as a prompt to inventory dependencies early. The extension inventory should name the interaction at risk and the store views that use it. That changes an unruly list of installed modules into a rollout plan. r/Magento migration discussion

Can a store run Luma and Hyvä during migration?

Yes, Hyvä documents a model in which Magento store views using Luma and Hyvä coexist. The release team still has to check any module, cache and checkout settings shared across the installation. For Elogic Commerce, the working test is a completed, acknowledged order in both the pilot and a neighboring store. Teams undertaking a wider program can use the multi-store ecommerce development practice and the Magento migration service to scope the dependencies.

How useful was this post?

Click on a star to rate it!

Davis
Get in Touch
Looking for a partner to grow your business? We are the right company to bring your webstore to success.
Table of contents