Shopify Hydrogen migration: how long should you plan for?
Contents
It’s often the first question asked, even before budget: how long does this take. The honest answer is “it depends,” but that answer deserves to be broken down rather than left vague.
The general range
A Hydrogen headless migration generally takes between 4 and 12 weeks, from the initial audit to the switchover. The range is wide because it depends directly on three factors: the size of the catalogue, the number of third-party integrations to rebuild, and the level of customisation expected on the storefront.
Timeline and budget move together, for the same reasons. If you’re scoping both at once, how much a Shopify Hydrogen migration costs breaks down where the money goes across the same phases.
The phases, and how long each one takes
| Phase | Typical duration | What happens |
|---|---|---|
| Audit and scoping | 1–2 weeks | GA4 and Clarity analysis, full map of the existing site, dependency inventory, mockups of key pages |
| UX and design | 1–3 weeks | Only if a redesign is in scope; runs partly in parallel with architecture |
| Storefront build | 2–8 weeks | Product pages, navigation, search, cart, checkout connection, native rebuild of app features |
| Integrations | 1–4 weeks | ERP, PIM, marketplaces, tracking; often the least predictable phase |
| SEO and tracking | 1–2 weeks | URL mapping, redirect plan, structured data, event verification |
| QA and acceptance | 1–2 weeks | Cross-device testing, performance checks, client sign-off |
| Switchover | A few days to a week | DNS switch and redirects in off-peak hours, with reinforced monitoring |
| Post-launch support | Often 4 weeks | Performance and conversion adjustments once real traffic hits the new version |
These phases overlap in practice, which is why the totals below are shorter than the sum of the rows. Design and architecture typically run alongside each other, and SEO work starts during the build rather than after it.
Two of them deserve a word. The audit isn’t wasted time: it prevents discovering constraints mid-build that should have been anticipated, and it forms the basis for the final quote. And the switchover is short in duration but critical in preparation, because most of the work for that phase actually happened upstream.
Three scenarios
Simple storefront: 4 to 6 weeks. A standard catalogue, a design that carries over largely as-is, few external tools, and a handful of apps that are either dropped or rebuilt quickly. The audit is short because there isn’t much to untangle, and the build phase stays at the low end. This is the profile where a Hydrogen project can genuinely move fast.
Established store: 6 to 8 weeks. A Shopify Liquid store with real history: custom UX expectations, a dozen apps to triage, tracking that marketing depends on, and an SEO footprint worth protecting. The build phase stretches because features that used to be apps now need to be written, and the SEO phase carries actual risk. This is the most common profile.
Complex project: 10 to 12 weeks or more. A CMS replatform, a custom ERP, marketplace sync, a deep category hierarchy, international markets, or advanced search with business rules. Here the integrations phase, not the storefront, sets the pace. Scoping usually needs to be done case by case rather than from a range.
What most often extends the timeline
Poorly documented third-party integrations. An in-house ERP, a marketplace sync, a repricing tool: when these pieces have existed for years without up-to-date documentation, the time needed to understand them before reconnecting them often exceeds initial estimates.
A complex catalogue hierarchy. A deep catalogue with many nested categories requires upfront modelling work, particularly when migrating from a CMS like PrestaShop to Shopify.
Back-and-forth on validation. A client who validates each stage quickly moves faster than a project where every step waits on approval that drags on for days. This is the single factor most under the client’s control.
Scope added mid-build. A redesign that grows during development is legitimate, but it should be treated as new scope with its own timeline rather than absorbed silently into the original estimate.
What should never be compressed
The time spent on the initial audit and on preparing SEO redirects are the two stages where cutting corners costs the most afterwards. A fast migration that loses 20% of organic traffic because the redirect plan was rushed is never a net time saving, it creates a cleanup project longer than the time saved at the start.
The same goes for QA on mobile. A storefront validated only on desktop tends to reveal its problems on the traffic that actually converts.
In summary
For a Shopify Liquid to Hydrogen project on a medium-sized catalogue, plan for 6 to 8 weeks. For a CMS to Shopify replatform with a custom ERP and integrations, the range more naturally climbs to 10 to 12 weeks. These are orders of magnitude: the precise schedule always depends on the initial audit specific to each site.
To assess the real timeline for your project, the Shopify to Hydrogen migration path details how the initial audit establishes a reliable schedule before any commitment.