Bring your history. Keep your sleep.

Your past, in the new system

Moving platforms shouldn’t mean starting your customer list from zero. Import customers and their order history from:

• CSV or TSV, up to 500 MB or 500,000 rows,
• Excel workbooks (.xlsx, .xlsm, .xls),
• BigCommerce and Shopify exports, with the mapping pre-filled and each platform’s quirks handled — BigCommerce’s packed product column, Shopify’s continuation rows, and both platforms’ status values.

Files upload straight to storage, so a large export doesn’t time out in a browser tab.

Nothing is written until you’ve seen it

1. Map. Throttle reads a sample, detects the format, and suggests a field for every column. Date order — day-first or month-first — is something you choose, never something guessed.
2. Dry run. Validation reports exactly what would be created, updated, skipped, or rejected, and writes nothing. Row errors download as a CSV you can fix.
3. Commit. Only after a dry run has passed.

Undo, carefully

Changed your mind? Undo removes what the import created — but keeps any record that has since picked up a payment, fulfillment, or quote, and tells you what it kept.

Run in parallel before you switch

Imports land in whichever environment you choose, so you can rehearse a migration in a non-production environment, check it, and repeat it in production. The migration playbook walks the whole cutover — what moves, what stays, and how to run both systems side by side before touching DNS.

Good to know

• Imports cover customers and orders. Throttle doesn’t hold a product catalog, so there is no catalog import.
• Saved cards can’t come across in a file; moving them is a processor-to-processor transfer we coordinate with you, with lead time.
• The dry run counts top-level rows; addresses and line items are validated but not yet tallied.