How Do I Import My Webflow Site to VeloCMS?
Connect a Webflow site token at Admin → Import → Webflow and VeloCMS walks you through choosing CMS collections, mapping their fields, and importing everything as drafts — or use the CSV fallback if you'd rather not grant API access.
Webflow's CMS lives behind an API, not a public feed, so VeloCMS's Webflow importer connects to it directly instead of scraping pages. Go to Admin → Import → Webflow, paste a site token, and a five-step wizard walks you through choosing which CMS collections become posts or pages, mapping their fields, and importing everything as drafts. No token to mint? A CSV fallback is one click away in the same wizard.
Where do I get a site token?
In Webflow, go to Site Settings → Apps & Integrations → API access and generate a site token scoped to cms:read — that's the only permission VeloCMS asks for. Paste it into Admin → Import → Webflow along with your Site ID, then click Connect & list collections. Your token is encrypted immediately and deleted once the import finishes — it's never stored long-term.
What if I'd rather not grant API access?
Use the CSV fallback instead. In Webflow, go to Collection settings → Export as CSV for each collection you want to bring over, then paste the file's contents into the CSV import panel on the same Admin → Import → Webflow screen. You'll map its columns the same way as the API path — just one collection at a time instead of several at once.
How does the collection mapping work?
After connecting, you choose a destination — Posts, Pages, or Skip — for each CMS collection Webflow returns. For every collection you're bringing in, you then map its fields to VeloCMS's Title, Slug, and Body (all required), plus optional Excerpt, Published date, and Cover image fields. Anything you leave unmapped isn't dropped — it's appended to the post as metadata so you can find it later.
What doesn't come through: archived CMS items are skipped automatically, and staged or unpublished items are excluded by default — the importer only reads what Webflow considers live. Your visual design doesn't transfer either; Webflow's CMS API returns content and field data, not layout, so you'll pick a VeloCMS theme to rebuild the visual side.
What do I see before anything imports?
Once every collection is mapped, the Preview step shows counts for posts, pages, and media before anything is written, along with any warnings — an item skipped because a required field was empty, for example. Nothing is saved to your blog until you click Import now.
Does everything import as a draft?
Yes — every post and page from Webflow lands as a draft, regardless of whether the source item was live on your Webflow site. Review and publish each one from Admin → Posts when you're ready.
Can I run the import again without duplicating content?
Yes. Re-running an import skips anything already brought in from that collection rather than creating duplicates, so it's safe to connect again later if Webflow content changes or a collection was left mapped to Skip the first time.
What should I do once the import finishes?
Head to Admin → Posts to review and publish what came in. Since your Webflow visual design doesn't transfer, pick one of VeloCMS's 39 themes to rebuild it — Atelier, Serif, and Curator are built for the same design-forward, studio-and-agency feel Webflow sites tend to have.