Migrating a Webflow CMS Collection is not a copy-paste job. Here's what transfers cleanly, and where reference fields and dynamic templates need manual rebuilding.
Key takeaways
- Plain text, rich text, images and simple select fields migrate cleanly between CMS platforms.
- Reference and multi-reference fields encode relationships between Collections that have to be rebuilt in the destination CMS's own structure, or they resolve to nothing.
- A Webflow Collection template exports as flat HTML per item, not as a template – the destination CMS needs its own equivalent template built before migrated content has anywhere to render.
Migrating a Webflow CMS Collection is not a copy-paste job, and the field-by-field detail is exactly where a DIY attempt or a rushed agency quote tends to go wrong. Here is what actually maps cleanly, and what needs manual rework.
What maps cleanly
- Plain text, rich text and number fields transfer close to 1:1 into most modern CMS structures, ours included.
- Images and files migrate with their alt text and captions intact, as long as the export process pulls the actual asset URLs rather than just the field references.
- Single-select and switch fields map directly onto equivalent field types almost everywhere.
Where it gets harder: reference fields
A Reference field (this blog post belongs to this author) or a Multi-reference field (this product belongs to these three categories) encodes a relationship between two Collections, not just a value. Recreating that relationship means the target CMS needs an equivalent relational structure already in place before the content lands – otherwise the reference resolves to nothing, silently, and nobody notices until a page renders a blank author byline.
Dynamic templates need to be rebuilt, not migrated
A Webflow Collection page template – the layout that renders every item in a Collection – does not export as a template at all; it exports as one static HTML file per item, with the templating logic gone. The destination CMS needs its own equivalent template built by hand, matching field-for-field, before the migrated content has anywhere to render into.
What we actually do
Our Astro + CMS – Collections package migrates the Collection data itself, rebuilds the reference relationships in our CMS's structure, and builds the equivalent Astro templates so the migrated content renders exactly where it used to. It is priced at $1,390 and takes 8–16 working hours depending on how many Collections and how many cross-references you're carrying – a single blog Collection is a very different job from five Collections referencing each other.
See the Collections package in detail, or tell us how your Collections reference each other and we'll scope it properly.