How to Migrate Your Webflow CMS Content Without Losing a Single Post

The Content Problem Nobody Talks About

When people plan a Webflow migration, they focus on the design. The layout, the animations, the colors. That's the visible part. But the real challenge — the one that can make or break your migration — is the content.

If your Webflow site has a blog with 200 posts, a portfolio with 50 projects, or product collections with 500 items, that content needs to come with you. And Webflow's export tools are... limited.

Here's the reality: Webflow gives you a CSV export of your CMS collections. That CSV contains your text fields, reference IDs, and some metadata. What it doesn't contain:

• Rich text formatting. Your carefully formatted blog posts — with headers, bold text, lists, embedded images — come out as plain text or raw HTML blobs in a single CSV column. The structure is there but it's messy.
• Uploaded images. The CSV contains Webflow CDN URLs for your images. Those URLs work today, but they won't work forever. And they're serving unoptimized images at Webflow's CDN pricing.
• Multi-reference relationships. If your blog posts reference categories, authors, or tags through multi-reference fields, those come out as comma-separated IDs that mean nothing outside Webflow.
• Collection page templates. Your CMS collection templates — the layouts that render each blog post or portfolio item — don't export at all. You're rebuilding those from scratch.
• Dynamic visibility rules. Any conditional visibility you set up (show this if field X is not empty) is gone. Those rules need to be recreated as code logic.

Step 1: Export Everything Before You Start

Before you touch anything, create a complete backup:

1. Export every CMS collection. Go to each collection's settings in Webflow and export the CSV. Do this for every collection — blog posts, categories, authors, products, everything.
1. Download all images. Use a tool like wget or a browser extension to batch-download all images from your Webflow CDN URLs. Don't skip this — those URLs will break when you decommission the Webflow site.
1. Screenshot every collection page template. You'll need these as visual references when rebuilding in your new CMS.
1. Document your URL structure. Map every collection URL pattern. If your blog posts are at /blog/[slug] in Webflow, you need them at the same path in the new site. URL changes kill SEO.

Step 2: Choose Your New CMS

Your Webflow CMS replacement should match your team's technical comfort and your content needs:

Payload CMS (Our Recommendation for Most Teams)

• Open source, self-hosted, full TypeScript support.
• Visual editor that non-technical team members can use.
• Unlimited content types and relationships.
• Built-in image management with automatic optimization.
• Runs alongside your Next.js app — one deployment, one codebase.

Sanity

• Hosted service with a generous free tier.
• Real-time collaborative editing (like Google Docs).
• Extremely flexible content modeling.
• Great for teams that want zero infrastructure management.

Markdown/MDX Files

• No CMS service needed. Content is files in your Git repo.
• Version-controlled alongside your code.
• Best for developer blogs and documentation.
• Not suitable for non-technical content editors.

Step 3: Transform Your Content

This is the tedious but critical middle step. Your Webflow CSV needs to become structured data in your new CMS. Here's the process:

Clean the Rich Text

Webflow exports rich text content as HTML blobs in your CSV. This HTML is Webflow-specific — it uses Webflow classes, non-semantic markup, and embedded Webflow image URLs. You need to:

1. Parse the HTML from each rich text field.
1. Strip Webflow-specific classes and attributes.
1. Convert to your target CMS's format (Lexical JSON for Payload, Portable Text for Sanity, Markdown for file-based).
1. Replace Webflow CDN image URLs with your new image paths.
1. Validate that formatting survived the conversion — check headers, bold, italic, lists, code blocks.

AI tools like Claude Code are excellent at writing these conversion scripts. A typical transformation script is 50-100 lines of code and handles the entire collection.

Migrate Images

Every image referenced in your content needs to be:

1. Downloaded from Webflow's CDN.
1. Uploaded to your new CMS's media library (or your own storage).
1. Re-linked in the content. Every image reference in every post needs to point to the new URL.

This sounds painful because it is. For a blog with 200 posts averaging 3 images each, that's 600 images to migrate. Automation is essential. Write a script that:

• Reads the CSV and extracts all Webflow CDN URLs.
• Downloads each image.
• Uploads to your new storage.
• Returns a mapping of old URL to new URL.
• Replaces all URLs in the content.

Rebuild Relationships

If your blog posts reference categories, authors, or tags, you need to:

1. Create the referenced collections first (categories, authors, tags) in your new CMS.
1. Import those items and get their new IDs.
1. Map old Webflow reference IDs to new CMS IDs.
1. Update the blog post data with the new reference IDs.
1. Import the blog posts with corrected references.

Step 4: Build Your Collection Templates

In Webflow, collection page templates define how each CMS item looks. In Next.js, these become dynamic route components. For example:

• Webflow blog template at /blog/[slug] becomes app/blog/[slug]/page.tsx in Next.js.
• Your template fetches the post data from your CMS and renders it with your React components.
• Dynamic metadata (title, description, OG image) is generated per post using Next.js Metadata API.
• Related posts, author info, and category navigation are pulled from CMS relationships.

This is actually an upgrade. In Webflow, every collection item uses the same rigid template. In Next.js, you can have different layouts for different content types, conditional rendering, and dynamic components. If you want the full technical migration guide, check our Webflow to Next.js Migration Playbook.

Step 5: Verify Everything Before Launch

Content migration verification checklist:

1. Post count matches. Count the posts in Webflow and in your new CMS. They must be identical.
1. Rich text formatting preserved. Spot-check 10-20 posts for correct headers, bold, italic, lists, and code blocks.
1. All images load. Check that every image in every post renders correctly. Broken images are the most common post-migration issue.
1. URLs match. Every post should be at the same URL path as it was on Webflow. Check 301 redirects for any that changed.
1. Relationships work. Categories, tags, and author pages should filter and display correctly.
1. Meta tags are correct. Check title, description, and OG image for each post — especially your highest-traffic posts.
1. RSS feed works. If you had an RSS feed, make sure the new one is at the same URL (or redirect the old one).

The Time Investment

Here's how long content migration typically takes:

• 10-50 CMS items: 1-2 days. Manual migration is feasible.
• 50-200 CMS items: 3-5 days. You need automation scripts.
• 200-1000 CMS items: 1-2 weeks. Full automation with batch processing and verification.
• 1000+ CMS items: 2-4 weeks. Enterprise-level migration with staging, testing, and rollback plans.

This is one area where outsourcing often makes sense. Content migration is repetitive, error-prone, and critical to get right. A team that's done it 50+ times will be faster and more reliable than doing it for the first time. Read our Complete Outsourcing Guide for Webflow Migrations if you want to evaluate that option.