Migration setup

1 The old site Address of the old site Add a path to move only that part, e.g. https://www.old-site.com/blog/ Which platform is it on? The run checks this itself at the start and asks you to confirm.

2 Access to the old site

The old store's myshopify domain

The old storefront is password-protected (every development store is; you will set SB_SOURCE_STOREFRONT_PASSWORD: the old store's Admin > Online Store > Preferences)

I will set SB_SHOPWARE_ACCESS_KEY (the storefront page does not carry the key)

WooCommerce: the site is a shop (products, and with a key customers, orders, coupons and reviews)

The crawl export (folder, zip or URL file; path in the project)

3 What to migrate

Each part runs behind its own approval. Every run builds a template per page and the homepage from the theme's existing sections; every part the theme has no section for gets a /sb:build proposal, each behind its own approval, and a line in gaps.md.

4 The new store Target store The run never writes to the live theme; new pages and posts are created hidden and published in one approved pass. Launch theme id (optional) The unpublished theme the store launches with, if it is not the live one. Admin > Online Store > Themes > … > Edit code: the number in the address. Theme folder on your machine A shopify theme pull of the theme the pages are published on, or the theme project checkout: the page templates and the homepage are built from its sections. New public domain (optional) The new storefront is password protected (you will set SB_STOREFRONT_PASSWORD; Admin > Online Store > Preferences) Client mapping or redirect file (optional, path in the project)

Advanced: task name, limits and approvals

Task name (optional) Lowercase letters, digits and hyphens. The task folder is migrate-<name> and the new menus' handles start with it: give a second run of the same old site on one store its own name. Most URLs per run (at most 300; a bigger site runs in batches) Approvals