Your CMS collections with every custom field intact. One CSV per collection.
A few minutes per collection.
Blog.csv
read locallyThis is a Framer a cms collection export
We can tell from the columns and the file name.
A CMS collection
128 of 129 ready128 a cms collection ready: 1 row will be skipped.
Row 84: this record has no name.
Nothing has been saved yet.
It renders a list beautifully. It does not know who bought, who asked, or what is in stock.
Payments, inquiries, email, invoices: four other tools, four other logins, four other bills.
The visitor who filled in the form and the customer who paid are unrelated as far as the software is concerned.
Everything in this list is something an importer we maintain actually reads out of your Framer export. It is generated from that importer, so it cannot promise you something we do not do.
A CMS collection
CMS → pick a collection → ⋯ → Export CSV
Blog.csv
sparx has a visual builder for the front and a real commerce, CRM and email system behind it. The inquiry becomes a customer becomes an order, in one place, with nothing wired between them.
Custom fields land as custom properties rather than being dropped.
Forms write to the CRM instead of an inbox.
One bill instead of five.
Every migration leaves something behind. Here is ours, so it is not a surprise halfway through.
Framer's design and interactions do not transfer: the content and its structure do.
One export per collection.
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 Framer account carries on exactly as it is. Plenty of people run both for a few weeks before switching their domain over.
Export the file Framer already makes for you, drop it in, and look at what would happen before anything is saved. A few minutes per collection.