Magento to Hyvä Migration Checklist

Timeline at a glance

Porto, PWA Studio and heavily customised stores usually take 3–5 weeks in total; most of the extra time goes into phases 2 and 5.

Print this checklist

1. Check requirements

• Magento Open Source or Adobe Commerce is 2.4.4-p9, 2.4.5-p8, 2.4.6-p7, 2.4.7-p1 or later; if not, plan the upgrade first
• PHP is 8.1, 8.2, 8.3 or 8.4
• Your development or CI environment has Node.js 20+ for the Tailwind build (don't build on production)
• You have a free Hyvä licence key from your hyva.io account
• A staging environment with a recent copy of production data is available

2. Audit your current store

• Export the list of enabled extensions and mark those with storefront features
• List every template override, layout change and custom JavaScript in your current theme
• Benchmark mobile Core Web Vitals (PageSpeed Insights field data) for home, category, product and cart
• Crawl the site and save URLs, titles, meta descriptions, canonicals, hreflang and structured data
• Note analytics, tag manager, consent and other third-party scripts

3. Plan extensions and licences

• Backend-only extensions: no work, just test
• Extensions with a vendor or community Hyvä compatibility module: install and test (available with the free licence key)
• Extensions with no compatibility: estimate a custom compatibility module (typically 1–5 days each)
• Outdated or redundant extensions: remove or replace
• Checkout: keep the Luma fallback, or budget for Hyvä Checkout (€1,000 one-time licence per Magento installation, set by Hyvä)
• Components: decide whether you need Hyvä UI (a separate paid product for new users)

4. Decide on design

• Rebuild the current design pixel-perfect, refresh it, or start from a ready-made Hyvä theme
• Capture brand colours, fonts and spacing as Tailwind configuration
• List every page type and component: header, menu, footer, product cards, filters, gallery, mini-cart
• Approve mobile layouts first; most traffic is on phones

5. Build on staging

• Install Hyvä and create a child theme in version control
• Add the Tailwind build to your deployment pipeline
• Rebuild templates in order of traffic: home, category, product, cart, account
• Install and build compatibility modules
• Keep CMS blocks, banners and menus editable in the admin
• Block staging from search engines

6. Protect your SEO

• Crawl staging and compare titles, meta descriptions, canonicals and hreflang with the original crawl
• Validate product, breadcrumb and organisation structured data on every template
• Check headings, image alt text and internal links
• Keep robots.txt, XML sitemaps and redirects unchanged

7. Test everything

• Search, category filters and sorting
• All product types: simple, configurable, bundle, grouped, downloadable
• Cart, coupons, mini-cart, customer account and wishlist
• Checkout with every payment and shipping method
• Transactional emails and order flow into ERP or fulfilment
• Real devices and browsers, keyboard navigation and screen-reader basics
• Lighthouse and Core Web Vitals on staging against your benchmark

8. Launch

• Pick a low-traffic window and freeze content changes
• Back up code and database
• Deploy, run static content deploy and warm caches
• Smoke-test key journeys and place a real test order
• Keep a rollback plan ready

9. The first 30 days

• Monitor errors, uptime and checkout conversion daily for two weeks
• Watch Search Console for crawl errors and indexing changes
• Compare Core Web Vitals field data after 28 days (Google's reporting window)
• Remove the old theme and unused extensions once stable
• Put a maintenance plan in place so the store stays fast

Sources

• Hyvä documentation: Getting started (version requirements)
• Hyvä Checkout (licence terms)