# A Shopify migration plan, so the move is priced on facts.

> The Migration Blueprint is a fixed-fee plan for brands leaving Magento, Salesforce Commerce Cloud, BigCommerce, WooCommerce or a custom platform. We audit the store, map the data, every URL and each integration, then price the move in phases. You decide on the facts, and you own the plan whoever builds from it.

Migrations to Shopify · Migration Blueprint

- **Starts with:** A fixed fee, agreed in writing
- **Typical build:** Phased fixed fees, each priced in the Blueprint
- **You own:** The Blueprint, whoever builds from it

## When is a Migration Blueprint the right first step?
- You have decided to leave your platform, and the quotes you hold disagree.
- Integrations with your ERP, OMS or warehouse are undocumented, or known only to whoever built them.
- Organic search carries real revenue, and nobody has listed every URL that earns it.
- You sell retail and wholesale, and the B2B rules live in extensions or custom code.
- Your board or finance team wants a fixed scope before approving a replatform.

## How does a Migration Blueprint run?
1. **Audit the platform** — Data, integrations, custom code and a rankings baseline, read from the live store.
2. **Map what moves** — The data model, every URL and each integration contract, field by field.
3. **Shape the build** — Theme or headless, plus the apps and Functions that replace platform logic.
4. **Plan the cutover** — Rehearsals, tested redirects, a rollback plan and a date set by your trading calendar.
5. **Price the phases** — Each build phase scoped and given a fixed fee before you commit.

## A plan a capable Shopify team can build from
- A data map for catalog, customers, orders and B2B
- An inventory of integrations, each with its contract
- A URL inventory and a full redirect map
- Where each piece of platform logic lands on Shopify
- A theme or headless recommendation, with the reasons
- A cutover plan with rehearsals and a rollback
- A phased build proposal, each phase at a fixed fee

## What usually goes wrong
- **Pricing the build before mapping the data** — Unmapped data is where migration budgets come apart.
- **Leaving redirects until launch** — Rankings follow URLs; map every one before you build.
- **Copying every old feature across** — Some logic becomes standard Shopify; some should be retired.
- **Picking a launch date that ignores trading** — Cut over in a quiet window, with a rollback ready.

## A retail and wholesale migration to Shopify Plus

We moved a clinical skincare brand’s retail and wholesale business onto Shopify Plus: one consumer storefront and four B2B storefronts on one organisation and one theme, with checkout rules as Shopify Functions, programs as custom apps, and an ERP integration. In production, ongoing.

## Questions
### What is in a Migration Blueprint?

A data map for catalog, customers, orders and B2B; an inventory of integrations and their contracts; every URL with its redirect; where each piece of platform logic lands on Shopify; a cutover plan with a rollback; and the build priced in phases.

### How long does a Blueprint take?

It depends on the size of the catalog, the number of integrations and how many stores are moving. The schedule and the fee are set in writing before work begins. If the scope changes, the change is quoted first.

### Can another team build from it?

Yes. You own the Blueprint, and it is written so a capable Shopify team could build from it, whether that is your own team or another studio. If you want us to build it, the phases are already priced.

### How is it different from an Architecture Review?

The three-week Architecture Review, led by our founder, is for brands still weighing their options; it ends with a prioritised roadmap. The Blueprint is for brands that have decided to move to Shopify; it ends with the move mapped and priced.

### What happens after the Blueprint?

You choose. We can run the build in phases, each at the fixed fee the Blueprint sets, through rehearsal, cutover and hypercare. After launch, an Engineering Partnership can keep the store current. Or you take the plan elsewhere.

[Request a Migration Blueprint](https://www.studioantipodes.com/start-a-project)