Replace the heavy Luma frontend with Hyvä — Tailwind CSS and Alpine.js instead of RequireJS, Knockout.js and jQuery — while keeping your URLs, content, extensions and checkout working. Since November 2025 the Hyvä Theme itself is free and open source, so the main investment is the migration work, which we scope precisely before we start.
Luma loads RequireJS, Knockout.js, jQuery and many UI components on every page, which makes good Core Web Vitals hard to reach on mobile. Hyvä removes that stack. Pages are rendered server-side with small Alpine.js components and a single compiled Tailwind stylesheet, so far less JavaScript is downloaded and executed.
For merchants that usually means faster Largest Contentful Paint, better Interaction to Next Paint on mobile, simpler frontend development and lower cost for every future change. For developers it means plain PHTML templates, ViewModels and utility CSS instead of LESS inheritance and Knockout bindings.
A migration is not a reskin. Every extension that outputs frontend code must be Hyvä-compatible, and the checkout needs its own decision. That is why we start with a compatibility audit and a written plan.
Everything your customers touch on the storefront is rebuilt or re-tested on Hyvä.
A child theme of Hyva/default (or Hyva/default-csp) with your design system in Tailwind CSS v4: colours, typography, spacing and reusable components.
We check each frontend module against the Hyvä compatibility module tracker, install official compat modules where they exist and build our own where they do not.
Choose between Hyvä Checkout (commercial, built on Magewire), the Luma checkout fallback, or a supported third-party checkout — based on payments, customisations and budget.
Page Builder content, CMS blocks and widgets are reviewed and styled for Hyvä so marketing teams keep working the way they do today.
No URL changes, metadata kept, structured data rebuilt in templates, GA4 and GTM events re-implemented and verified.
Critical images, fonts and third-party scripts are tuned for Core Web Vitals after migration, with Varnish and cache settings checked.
We have migrated stores with dozens of third-party modules, multi-store setups and custom checkouts. The hard parts are predictable when you have done them before.
We list every frontend module, template override and integration first, so the estimate reflects your store, not a template quote.
Custom compatibility modules use ViewModels, Alpine.js and escaped output, and follow Hyvä conventions so they survive upgrades.
We crawl the old and new storefronts and compare titles, canonicals, status codes and structured data before go-live.
We record lab and field Core Web Vitals before and after the migration, so improvements are measured rather than assumed.
Your Luma store stays live throughout. Hyvä is built and tested in parallel.
We inventory frontend modules, template overrides, Page Builder usage, payment and shipping methods, tracking and integrations, and check each against Hyvä.
We create the Hyvä child theme, configure Tailwind and build your header, footer, category, product and CMS templates.
Compatibility modules are installed or built, and the agreed checkout option is implemented and tested with every payment method.
Cross-browser and device testing, accessibility checks, crawl comparison, tracking validation and user acceptance testing.
Theme switched in a planned window, caches warmed, monitoring in place, and Core Web Vitals compared after launch.
Send your store URL and, if possible, a list of installed extensions. We will tell you which modules already have Hyvä support, what needs custom work and the likely timeline.
Within one business day, Mon–Fri
No obligation. We reply within one business day.