Spocket Migration: Move Catalog & Order Data Without Losing Trust
Migrate into Spocket with an inventory, field map, pilot import, dual-run week, and validation — so history survives and operators trust the new system.
Quick answer
Migrate into Spocket with an inventory of imported products, supplier mappings, and open dropship orders, a field map, a pilot import, a dual-run week, and validation with the people who live in the data — so history survives and the team trusts the new system.
- Inventory source objects
- Map fields before bulk load
- Pilot one site / one role / one team
- Dual-run for a week
- Validate with sceptic users
Spocket migration rules
- Inventory first — Typical objects: imported products, supplier mappings, and open dropship orders.
- Pilot beats big-bang — Prove a small Spocket import before you move everything.
- Integrations after the pilot — Research names Shopify, Woocommerce, Wix, Bigcommerce, and Square on the Spocket side — confirm the connectors your commerce loop depends on.
- Do not migrate the wrong job — Spocket is dropshipping sourcing. Do not import a CRM pipeline or a marketing course catalogue and expect it to become dropshipping sourcing.
Spocket migration map
1. Inventory and map
List imported products, supplier mappings, and open dropship orders. Map required fields and owners. Never invent list prices here — confirm plans, processing, and quote terms on /pricing/spocket/. Worked example: Harbor Studio (Shopify store testing dropship SKUs) discovers duplicate SKUs or customer IDs in the spreadsheet before the first import — and fixes identity before volume.
2. Pilot import
Import one site, one role, or one team. Run import a US/EU supplier product into the connected store and push a test order back to the vendor on the pilot set. Worked example: Harbor Studio (Shopify store testing dropship SKUs) will not schedule a cutover until the pilot can a merchandiser can import within the plan cap and an order routes without copy-paste.
3. Dual-run and cutover
Run old and new in parallel for a week. Spot-check records sceptic users care about, then freeze the legacy source. Worked example: Harbor Studio (Shopify store testing dropship SKUs) keeps the old store or spreadsheet until Spocket matches for seven consecutive days.
Spocket checklist
Bring these questions to every demo
Ask vendors to show the workflow live, not just describe it.
- 1Inventory source objectsimported products, supplier mappings, and open dropship orders
- 2Run a pilot importOne segment first; fix mapping before bulk.
- 3Validate with operatorsSpot-check records they care about before cutover.
4. Inventory what must move into Spocket
List users, historical records, templates, and integrations that must survive migration. Mark nice-to-have exports you can leave behind.
Worked example: Merchants dropshipping with US/EU suppliers on Shopify/Woo migrates active records only and archives the rest as read-only exports.
5. Run parallel cutover with a rollback path
Keep the old system read-only until Spocket passes non-admin proof. Name a rollback owner and maximum parallel window.
Worked example: Merchants dropshipping with US/EU suppliers on Shopify/Woo caps parallel run at two weeks with daily checkpoint notes.
6. Verify counts and permissions after import
Reconcile user counts, role permissions, and a sample of migrated records. Research lists Shopify, Woocommerce, Wix, and Bigcommerce for Spocket. Confirm which are native vs API before go-live.
7. Inventory what must move into Spocket
List users, historical records, templates, and integrations that must survive migration. Mark nice-to-have exports you can leave behind.
Worked example: Merchants dropshipping with US/EU suppliers on Shopify/Woo migrates active records only and archives the rest as read-only exports.
8. Run parallel cutover with a rollback path
Keep the old system read-only until Spocket passes non-admin proof. Name a rollback owner and maximum parallel window.
Worked example: Merchants dropshipping with US/EU suppliers on Shopify/Woo caps parallel run at two weeks with daily checkpoint notes.
9. Verify counts and permissions after import
Reconcile user counts, role permissions, and a sample of migrated records. Research lists Shopify, Woocommerce, Wix, and Bigcommerce for Spocket. Confirm which are native vs API before go-live.
10. Inventory what must move into Spocket
List users, historical records, templates, and integrations that must survive migration. Mark nice-to-have exports you can leave behind.
Worked example: Merchants dropshipping with US/EU suppliers on Shopify/Woo migrates active records only and archives the rest as read-only exports.
11. Run parallel cutover with a rollback path
Keep the old system read-only until Spocket passes non-admin proof. Name a rollback owner and maximum parallel window.
Worked example: Merchants dropshipping with US/EU suppliers on Shopify/Woo caps parallel run at two weeks with daily checkpoint notes.
12. Verify counts and permissions after import
Reconcile user counts, role permissions, and a sample of migrated records. Research lists Shopify, Woocommerce, Wix, and Bigcommerce for Spocket. Confirm which are native vs API before go-live.
13. Before you sign with Spocket
Confirm the qualifying plan, non-admin proof, and integration owners in writing. Store quotes next to /pricing/spocket/ and the evaluation scorecard so finance can audit the same assumptions at renewal.
14. Write the decision memo
Name the job, the qualifying Spocket configuration, and what you are not buying yet. If stakeholders cannot explain why an alternative lost, the trial was not fair.
Frequently asked questions
Can we skip the dual-run?
Only if the dataset is tiny and reversible. Most SMB/mid teams regret skipping a week of parallel use.
What if history will not map cleanly?
Import active records first. Archive messy history as files rather than poisoning the new system of record.
Was this article helpful?
Have more questions? Contact our support team.
SoftwareGlimpse Updates
Want clearer software shortlists? Get buying guides and comparisons by email.
Newsletter coming soon.