Skip to main content
Preparing a redesign

Moving to Hyvä: what should you plan beyond changing your Magento theme?

You are considering Hyvä to improve your Magento 2 store. The project involves the storefront, but also the functions displayed there: search, configurable products, sales rules and payment. Before estimating a redesign, identify what will be rebuilt, adapted or retained, then organise checks with your team.

MagentoBy Julien BaillyText updated on 4 min estimated read

Illustration of a shopfront being replaced, connected to modules and a separate checkout

Key takeaway

Preparing a Hyvä project means inventorying journeys and extensions, explicitly choosing a checkout and testing a representative range of store behaviour. The budget depends on these adaptations and design ambitions; a theme alone guarantees neither loading times nor commercial gains.

Define what the redesign should improve

Difficult mobile navigation, a theme that has become expensive to maintain and a product journey unsuited to the business call for different work. Record the screens involved and the actions visitors need to complete. These uses will guide priorities and help validate the result.

I recommend separating interface problems from other issues: a broken ERP import or calculation error will not necessarily disappear with a new storefront. If a Magento upgrade is also planned, it should appear as a defined piece of work with its dependencies and checks.

Examine visible functions, not just the module list

Some extensions rely on Luma or Blank theme components. Hyvä provides compatibility modules to adapt these frontend elements. Check whether this adaptation is available for the version actually in use, then test it with your store's customisations.

The inventory should start from actual uses: filters, search engine, variant selection, special pricing, wishlists or customer accounts. A vendor's “Hyvä compatible” label is not enough to validate your combination of modules. Project-specific developments also need examination.

  • Function to preserve and the journey in which it is used
  • Extension, version and customisations supporting it
  • Available adaptation, remaining work and the person responsible for checking it

Choose the checkout during scoping

The Hyvä theme and the checkout solution are two separate choices. The documentation covers Hyvä Checkout, a separate product, and the option to retain a Luma-based checkout using the fallback mechanism. The choice must account for your payment methods and shipping extensions.

Write down the cases that must work: guest or signed-in checkout, address, carrier, discount, accepted or declined payment and return to the store. For B2B sales or specific journeys, add the rules actually used. This helps avoid discovering an essential dependency at launch.

Include content and SEO in the redesign

Mock-ups should cover real cases: a long title, a product without an image, several variants, a filtered category and error messages. Also consider editorial blocks and CMS pages: existing content may need adapting to remain readable with the new theme.

Changing the theme alone is no reason to change URLs. Record important pages, titles, internal links, canonicals and structured data before the switch. If addresses need to change, plan their mapping and appropriate redirects. Google details the checks specific to URL migrations.

Prepare a testable transition and rollback

Prepare acceptance testing in a suitable environment, with test payments and protected data. Compare current and future journeys on mobile and desktop, including keyboard use. Tracking tools and consent are also behaviours to check after a frontend change.

A gradual transition can be considered: Hyvä fallback allows a Luma theme to be retained on certain routes. This requires configuration and testing of the affected pages; it is not a guarantee of general compatibility. Also define how to return to the previous version if a critical journey fails.

Understand what affects the budget

The work depends on the number of templates, the degree of visual customisation, extensions to adapt and specific journeys. Checkout, content to migrate, languages or stores involved and validation time also affect the quote. Any third-party products or services should be identified separately with their current terms.

A useful proposal distinguishes the core redesign, known adaptations and unknowns requiring analysis. Baseline measurements and objectives are defined before work begins; results must then be observed on the actual website, with its content, scripts and hosting.

What to gather for an initial discussion

You can start with a short list. Missing information will be points for us to examine together; you do not need to produce a technical audit before getting in touch.

  • The store address and main reason for the redesign
  • The Magento version, theme and extensions, if you know them
  • Functions and payment methods to preserve
  • Stores, languages and content involved
  • The existing team, deadline and people who will take part in acceptance testing

Sources and references

Documentation consulted when writing this guide. Advice and procedures should be adapted to your own context.