What if the import goes wrong?

It tells you first. Your file is read in your own browser and checked before a single byte is uploaded, and then a practice run resolves every row against your real data and reports what would happen without saving anything. You only press the real button once you have seen the numbers.

Can I bring it in twice?

Yes. Records are matched on their natural key (SKU for products, email for customers, order number for orders) so running the same file again updates rather than duplicates. Fix something in the spreadsheet and re-drop it.

For most businesses there is nothing to do. It is a file and a button. If your data is genuinely awkward, email migrate@sparx.works and we will do the move with you.

← Every platform we move you from

Growing should not move you into a more expensive plan

Products with their variants and option sets, categories, customers and order history: from the CSV exports in your BigCommerce dashboard.

Start moving →What it costs

Three files, most of an afternoon for a catalog with real variant depth.

products.csv

read locally

This is a BigCommerce products export

We can tell from the columns and the file name.

Products

128 of 129 ready

128 products ready: 1 row will be skipped.

Must fix

Row 84: this record has no name.

Nothing has been saved yet.

A good year costs you money in a way that makes no sense.

Your plan is priced on how much you sell

Cross a sales threshold and the bill goes up, for exactly the same software you were using the day before. You did not get more product. You got a better year, and an invoice that treats it as a problem.

The features you grew into are on the tier above the one you are on

Abandoned cart, faceted search, customer groups, price lists. Each is a real thing a growing shop needs, and each is the reason to move up a plan rather than something you simply have.

It is still only the shop

BigCommerce sells well and knows nothing about the rest of the business: the quotes, the trade accounts, the mailing list, the stock in the second unit.

What comes across

Everything in this list is something an importer we maintain actually reads out of your BigCommerce export. It is generated from that importer, so it cannot promise you something we do not do.

ProductsCustomersOrders

The files you need from BigCommerce

Products

Products → Export → Bulk Edit template → Export to CSV

products.csv

Customers

Customers → Export → Export to CSV

customers.csv

Orders

Orders → Export → Export to CSV

orders.csv

Pay for capability, not for succeeding.

sparx charges per module you switch on, not per pound you take. A record year costs exactly what a quiet one does. And the modules are not just commerce: the CRM, the stock system, the email and the site are the same product, so the shop stops being an island.

What that changes

Your bill is the same in December as it is in February.
Trade pricing, price lists and customer groups are the B2B module, not a tier.
One place for a customer, whether they bought online, on a quote or over the phone.

What does not come across

Every migration leaves something behind. Here is ours, so it is not a surprise halfway through.

Option sets become product options, and complex option RULES (surcharge this combination, hide that one) do not come across. They are re-created where you need them.
Blog posts and web pages are rebuilt in the builder; BigCommerce has no export for them.
Gift certificate balances stay behind.

Before you start

Still curious? Read the platform docs, browse the API spec, or book a 20-min architecture call. We don't do high-pressure demos.

No. Everything happens on a copy. You export a file, and your BigCommerce account carries on exactly as it is. Plenty of people run both for a few weeks before switching their domain over.

Bring it over

Export the file BigCommerce already makes for you, drop it in, and look at what would happen before anything is saved. Three files, most of an afternoon for a catalog with real variant depth.

Get started →Ask us to do it