Skip to main content

​
Export Your Collection

1

Navigate to CMS Collections

In Webflow Designer or Editor, click CMS → Collections
2

Select your collection

Click the collection you want to migrate
3

Export as CSV

Click the settings icon (⚙️) → Export → CSV fileWebflow downloads a file named Collection Name.csv
4

Save the original

Store the file safely and make a backup copy
You should now have a CSV file with all your collection’s content, including all fields and metadata.

​
Critical: Don’t Edit These Columns

MigrateKit relies on Webflow’s system fields to prevent duplicates and track content. Never modify or delete:
Required Webflow Columns
  • Collection ID - Identifies the source collection
  • Item ID - Unique identifier for each item (used to prevent duplicates)
  • Locale ID - Language/locale information
If these columns are missing or modified, ContentWrap cannot properly track and update documents.

​
Don’t Rename Headers

Keep all column headers exactly as Webflow exports them:
❌ Wrong✅ Correct
Post TitleName
Article BodyPost Body
HeroMain Image
Renaming headers breaks MigrateKit’s auto-mapping feature.

​
Safe Modifications

You CAN make these changes without breaking the migration:
Remove rows for content you don’t want to migrate:
  • Draft items
  • Test content
  • Archived posts
Better approach: Import everything and delete unwanted drafts in Sanity instead. This gives you more flexibility.
Delete columns that are completely empty (no data in any row):
  • Blank columns added by spreadsheet software
  • Trailing empty columns
Only delete if every single row is empty in that column!
Delete empty rows at the end of the file after all your data

​
Understanding Webflow CSV Structure

Knowing how Webflow formats different field types helps you plan your Sanity mapping:

​
Text Fields

Plain text exports as simple strings: 
Name,Slug
My Blog Post,my-blog-post

​
Rich Text (HTML)

Rich content exports as HTML in quoted cells: 
Post Body
"<h2>Introduction</h2><p>This post has <strong>formatting</strong>.</p>"
ContentWrap automatically converts this to Portable Text during import.

​
Images

Images export as Webflow CDN URLs: 
Main Image
https://uploads-ssl.webflow.com/123abc/456def-image.jpg
ContentWrap downloads these and uploads them to your Sanity project. ###Multi-Image Fields Multiple images are comma-separated: 
Gallery
"https://cdn.webflow.com/img1.jpg,https://cdn.webflow.com/img2.jpg"

​
Dates

Dates export in ISO format: 
Published Date
2024-01-15T10:30:00.000Z
Excel will corrupt dates! Excel auto-formats dates, changing 2024-01-15T10:30:00.000Z to 1/15/2024. This breaks the import.Solution: Use Google Sheets or open CSVs in a text editor. If you must use Excel, import as text.

​
Booleans

Checkboxes export as text: 
Featured
true
MigrateKit converts "true", "yes", and "1" to true.

​
Reference Fields

Not Currently SupportedReference fields export but can’t be automatically imported. You’ll need to manually recreate relationships in Sanity after migration.See Limitations for details.

​
Common Issues

Problem: Seeing é instead of é or ’ instead of '.Cause: Encoding issue (not UTF-8).Solution:
  • Re-export from Webflow
  • MigrateKit handles UTF-8, UTF-16, and most encodings
  • If it persists, the source data in Webflow may be corrupted
Problem: Excel removed leading zeros, changed dates, or modified large numbers.Solution:
  • Don’t open CSVs in Excel
  • Use Google Sheets or LibreOffice Calc
  • OR import in Excel as text: Data → From Text/CSV → set columns to Text format
Problem: File looks broken in text editor with strange line endings.Solution: This is normal! CSVs can use different line ending formats (Windows vs. Mac vs. Unix). MigrateKit handles all formats correctly.
Problem: Content with commas creates extra columns.Solution: This shouldn’t happen—Webflow wraps fields containing commas in quotes. If you see this, the CSV may be corrupted. Re-export from Webflow.

​
Pre-Upload Checklist

Before uploading to ContentWrap, verify:
  • First row contains original Webflow headers (not renamed)
  • Collection ID, Item ID, and Locale ID columns present
  • No obviously corrupted data (garbled characters)
  • Dates are properly formatted (if visible)
  • Image URLs are complete (start with https://)
  • File saved with .csv extension
  • Backup copy created

​
Next Step

Once your CSV is ready:

Step 2: Upload & Map Fields

Upload your CSV and define field mappings

Migration Overview

See the complete migration process

Troubleshooting

CSV issues and solutions