Most migrations move the data and leave you to rebuild the storefront. That rebuild is the part that actually costs weeks, so it is the part this covers.

Translate the theme

The CLI reads a theme you already have and writes a Mercemur storefront from it.
Nothing is live until you publish, so you can push, look at the preview, and push again without a shopper seeing a half-migrated storefront.
The translation is built from Dawn and Horizon, Shopify’s own reference themes. A theme derived from either translates well. A heavily customised commercial theme will translate partially, and mercemur theme check tells you which sections before you commit to anything.
See Theme workflow for the full command set.

Bring the catalogue

Products, variants, collections, customers and orders come across through the import path rather than by hand. What matters afterwards is the check, not the import: run your top sellers and your most complicated variant setups first, because those are where a mapping difference shows up.

What does not come across

Be realistic about these up front rather than discovering them at launch:
  • Apps and their embedded scripts have no equivalent. Find the Mercemur feature, or the integration, that replaces each one.
  • Discount logic written as a Shopify Script needs rebuilding as a promotion.
  • Anything a theme did through a Shopify-only Liquid object will be flagged by theme check rather than silently dropped.

Finish the job

Do not point DNS at the new storefront until you have placed a real paid order on it. A free or zero-total order exercises none of the payment path.
  1. Connect a payment provider and place a real order.
  2. Check your highest-traffic pages render, especially the product page.
  3. Set up redirects for any URL that changes, so search results keep working.

Reference

  • Theme workflow for pull, check, push, publish and live preview.
  • The Storefront tab for templates, sections and redirects.
  • MCP if you would rather adjust the storefront by asking an assistant.