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

A beautiful site is not a business

Your CMS collections with every custom field intact, and your products: from the CSV exports Webflow makes per collection.

Start moving →What it costs

One file per collection, a few minutes each.

Products.csv

read locally

This is a Webflow 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.

The site is excellent. Everything behind it is missing.

1

The CMS has limits you keep bumping into

Item caps, collection caps, reference-field caps. You design around them, which is a strange way to spend design time.

2

Commerce is bolted on, and it shows

No stock across locations, no trade pricing, no purchase orders, no customer record beyond an email address and an order.

3

There is no CRM, so there is a spreadsheet

Inquiries go to an inbox. Deals live in a spreadsheet. The person who filled in the form and the person who bought are, as far as the system is concerned, strangers.

What comes across

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

ProductsPages and posts

The files you need from Webflow

Products

Ecommerce → Products → Export

Products.csv

A CMS collection

CMS → pick a collection → Export

Blog Posts.csv

Keep designing. Stop stitching.

sparx has a real visual builder, and behind it the commerce, CRM, stock and email that Webflow expects you to buy elsewhere and wire together. The form that captures an inquiry writes to the same place the order does.

What that changes

Custom collection fields come across as custom properties rather than being dropped: a Case Studies collection is not a blog post with three fields missing.
The inquiry, the quote and the order are the same customer, automatically.
No item caps.

What does not come across

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

Interactions, animations and the visual design do not transfer. The structure and the content do.
One CSV per collection, so a site with six collections is six files.

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 Webflow 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 Webflow already makes for you, drop it in, and look at what would happen before anything is saved. One file per collection, a few minutes each.

Get started →Ask us to do it