Skip to Content
Getting startedYour first migration

Your first migration

This walks through the New Migration wizard end-to-end. By the end you’ll have a migration object in draft status with credentials set and resources enabled — ready for an extract run.

Have the source platform credentials and a Shopify Admin API token ready before you start. The wizard validates them before letting you finish.

Step 1 — Basics

From the Migrations page, click New migration.

FieldWhat to enter
Migration nameThe merchant’s brand name (e.g. Northwind Home Goods). Shows up in the migrations list.
SlugAuto-derived from the name. Used in URLs and internal references. Edit if the auto value collides.
Source platformPick the platform the merchant is migrating away from. Today: Magento or Shopify. WooCommerce and BigCommerce are listed as coming soon.

Step 2 — Connect destination

The destination is always Shopify. Enter the Admin API access token for the destination store — the shpat_… value from a custom Shopify app installed on that store.

The token must have read+write scopes for every resource you plan to load. See Destination → Shopify for the exact scope list per resource.

Step 3 — Choose resources

Select which resource types this migration will move. The most common combination is products + collections + customers. Orders and gift cards are opt-in because they involve PII and money.

For each enabled resource, the wizard pins the current default mapping template version. You can fork or swap mappings later from the Mappings tab on the migration.

After the wizard

You’ll land on the migration’s detail page. The migration is in draft status — meaning it can be edited freely, but no run has executed yet.

From here:

  1. Verify credentials by triggering an extract-only run. See Runs → Phases for what that does.
  2. Inspect a few rows from the extracted source data. See Monitoring → Inspecting run items.
  3. Iterate on mappings if anything in the extract surprises you.
  4. Promote to active and run a full extract → transform → load.

Don’t run a load against a production destination until you’ve at least extracted and transformed once and reviewed the staged payloads. The platform makes this safe, but you still want to look.

Last updated on