Commerce Advisory · Platform Choice & Replatforming
Independent advice on whether to move, where to move and how to move without losing search traffic, tracking or subscribers. We plan, scope and QA the migration. Your developers or build partner carry it out.
Start with whether, not how
Many replatforms are approved for the wrong reason: the site feels slow, a plugin broke, a new hire prefers another platform. Sometimes the fix is a faster theme, fewer apps or better hosting. As part of Commerce Advisory, we compare staying and moving on total cost of ownership, the features you rely on, the integrations you'd rebuild and the revenue at risk during the switch.
We don't build themes or run migrations as a standalone service, so our platform advice has no stake in the answer. When moving is right, we write the plan, review the build partner's scope and QA the launch. Most moves also touch systems integration and the growth roadmap.
The moves we plan most
Brands usually move to get out of hosting, plugin updates and security patching, and to use Shopify's checkout and app ecosystem. More changes than the theme: Shopify uses fixed URL patterns, plugins map to apps or native features, and WooCommerce Subscriptions customers need a path to a Shopify subscription app.
Magento Open Source stores face a three-way choice. Adobe Commerce keeps deep customization, multi-store setups and a native B2B module, with licensing and development costs to match. Shopify Plus trades some flexibility for a hosted platform, Checkout Extensibility, Shopify Functions and Shopify Flow. Staying and re-architecting can be right when the code base is healthy.
Headless commerce separates the storefront from the commerce engine. It can suit content-led brands with their own front-end developers. For most DTC brands between $1M and $50M, it adds a second system to maintain, and apps and tracking have to be rebuilt by hand.
How we plan a migration
Revenue, conversion and AOV by channel and device, organic revenue by landing page, email and SMS revenue by flow, and repeat purchase rate (the retention rate calculator gives a quick read). Twelve months where possible.
Total cost of ownership, feature gaps, the integrations to rebuild and the revenue at risk, with the case for staying put included.
Products, customers with consent status, order history, reviews, gift cards and active subscriptions. Subscriptions usually mean moving payment tokens with your processor and subscription app, plus a fallback for customers who must re-enter a card.
A crawl of the old site, combined with GA4, Search Console and backlink data, mapped one-to-one to new URLs. Retired products go to the closest collection, not the homepage.
A tracking plan, the Klaviyo or SMS flow triggers to rebuild on new events, and every plugin mapped to an app, a native feature or custom work.
Test scripts for every journey, a change freeze before go-live, team training and new SOPs as part of change management, then weekly checks on 404s, rankings, conversion and flow revenue against the baseline.
SEO-safe migration planning
Shopify uses fixed paths, so old URLs can't be kept as they are. Each page that earns traffic or links gets a 301 to its new equivalent.
| Old URL (example) | New Shopify URL | Rule |
|---|---|---|
| WooCommerce /product/merino-crew-sock/ | /products/merino-crew-sock | One-to-one, keep the handle |
| WooCommerce /product-category/socks/ | /collections/socks | Category to collection |
| Magento /socks/merino-crew-sock.html | /products/merino-crew-sock | Drop the .html and category path |
| Discontinued product URL | /collections/socks | Closest collection, never the homepage |
Shopify only applies a redirect when the old path doesn't exist on the new store. Old redirects should point straight to the final URL to avoid chains.
FAQ
It depends on catalog size, custom features, subscriptions and integrations. Many mid-size stores plan for a few months from discovery to launch, plus 30 to 90 days of monitoring afterwards. The longest parts are usually data migration tests, app replacements and QA, not the theme. Our plan sets the timeline after we've inventoried every plugin and integration.
Some movement is normal while search engines process redirects. With a complete redirect map, content kept consistent on top pages and clean technical SEO, you give yourself the best chance of avoiding lasting losses. A steady decline on specific pages after launch usually points to a missing redirect or changed content, which is why we monitor by landing page.
Subscriptions need their own plan. Moving them usually means migrating payment tokens between processors, coordinated with your current subscription tool, the new Shopify subscription app and your payment provider. Not every token always moves, so you need a fallback flow for customers who must re-enter a card, and a way to track who still has to.
No. We don't run migrations or build themes as a standalone service. We decide the platform with you, write the migration plan, redirect map and data plan, review the build partner's scope and QA the launch. Our teams can rebuild tracking, Klaviyo flows and technical SEO, because those protect revenue you already earn.
Run the free audit for a pre-migration baseline, or book a call to talk through the platform decision before anyone starts building.