| name | sales-store-migration |
| description | Ecommerce store-migration strategy — the tool-agnostic playbook for replatforming (Shopify ↔ WooCommerce ↔ Wix ↔ BigCommerce ↔ PrestaShop ↔ Magento and beyond): choosing between automated migration tools (LitExtension, Cart2Cart, Migratly), native importers, CSV, or custom API scripts; migration-order mechanics (products → customers → orders), SEO preservation with 301 redirect maps, delta migration for orders arriving mid-cutover, app/webhook/payment re-wiring, and post-migration verification. Use when switching ecommerce platforms without losing SEO or order history, planning redirect maps before a replatform, deciding migration tool vs doing it by hand, recent orders keep appearing on the old store during cutover, migrated data needs verification (counts, variants, customer passwords), or rebuilding integrations after the move. Do NOT use for choosing the destination platform itself (use /sales-checkout) or LitExtension specifics (use /sales-litextension). |
| argument-hint | [describe your store migration — source, target, and what worries you] |
| license | MIT |
| version | 1.0.0 |
| tags | ["sales","ecommerce","migration","strategy"] |
Ecommerce Store Migration
Help the user replatform an ecommerce store without losing SEO, order history, or sales in transit. Covers approach selection (tool vs native importer vs CSV vs custom scripts), the migration sequence, redirect/SEO preservation, delta handling, integration re-wiring, and verification. Tool-agnostic; platform specifics live in the platform skills.
Step 1 — Gather context
Ask the user (skip anything already answered):
- Source → target? (e.g. WooCommerce → Shopify) — the pair determines available native importers and known mapping quirks.
- Scale? Products / customers / orders counts — drives tool pricing and the order-retention decision.
- Live sales volume? Orders per day during the migration window — determines how much delta handling matters.
- What must survive? (multi-select) SEO rankings/URLs · full order history · customer accounts · subscriptions/recurring billing · reviews · blog content.
- Who's doing the work? Solo founder / dev on hand / agency — selects DIY tool vs done-for-you.
Step 2 — Choose the migration approach
Decision tree
- Active subscriptions on the store? → That's the hard part; route billing continuity to
/sales-subscription-billing (don't double-bill on import) and handle catalog/SEO here.
- Tiny store (≲100 products, no order history worth keeping)? → CSV export/import or the target's native importer. Free; redirects still matter.
- Common pair with a strong native importer (e.g. WooCommerce → Shopify's official importer)? → Try native first; fall back to a tool if variants/orders map badly.
- Real store, real history, uncommon pair, or no dev time? → Automated migration tool: LitExtension (widest cart coverage ~140+, done-for-you tiers, money-back guarantee —
/sales-litextension), Cart2Cart (long-standing, ~85 carts, self-directed automation with detailed logging), Migratly (newer, modern UX, flexible attribute mapping — early-stage, thinner delta support).
- Custom source (homegrown cart, weird schema) or heavy data transformation? → Custom scripts against both platforms' APIs, or a tool's custom/API migration service.
Tool-selection criteria
Cart-pair support and per-pair mapping quality (test with a demo) · delta/re-migration support for live stores · SEO URL handling · entity pricing at YOUR counts · DIY vs concierge · refund terms. Discount review scores: migration-tool review profiles skew implausibly clean — judge by a demo migration on your own data, never testimonials.
