Skip to main content
Use this page for the high-level flow. The canonical product behavior lives in the four step pages below.

​
The 4-Step Process

MigrateKit’s migration workflow is designed to be straightforward while giving you complete control over how your content transforms.
1

Connect Sanity

Add your Project ID, dataset, and API token in ContentWrap
2

Export from Webflow

Download your collection as a CSV file
3

Upload & Map Fields

Upload CSV and map Webflow columns to Sanity fields
4

Import & Verify

Execute migration and review drafts in Sanity Studio

​
What Happens During Migration

You define how Webflow data becomes Sanity documents:
  • Name your Sanity document type (e.g., blogPost)
  • Map each Webflow column to a Sanity field type
  • MigrateKit auto-suggests mappings based on data patterns
  • Skip system fields like Collection ID and Item ID
Rich text fields are automatically converted:
  • HTML tags become Portable Text blocks
  • Headings, paragraphs, lists preserved
  • Bold, italic, links maintained
  • Images embedded in content
  • Unsupported tags wrapped as code blocks
Learn more: HTML Conversion
Images and files are handled automatically:
  • Downloads assets from Webflow CDN
  • Checks for duplicates (reuses existing)
  • Uploads to your Sanity project
  • Creates proper asset references
  • Reports upload status for each file
Learn more: Asset Handling
All content imports as drafts for safety:
  • Documents created with drafts. prefix
  • Published content remains untouched
  • Review and edit before publishing
  • Publish individually or in bulk

​
Migration Flow

​
Step-by-Step Guides

Follow detailed instructions for each phase:

Step 1: Connect Sanity

Link your Sanity project with API credentials

Step 2: Export

How to export CSVs from Webflow correctly

Step 3: Upload & Map

Upload CSV and define field mappings

Step 4: Import

Execute migration and verify results

​
Best Practices

1

Start Small

  • Test with a small collection (10-50 items)
  • Use a development dataset first
  • Verify the workflow works
  • Refine mappings before scaling
2

Keep Backups

  • Save original CSV files
  • Don’t delete Webflow data until verified
  • Export from Sanity for additional backup
3

Plan Your Schema

  • Decide on document type names
  • Choose appropriate field types
  • Consider Sanity naming conventions
  • Think about future content structure
4

Review Before Publishing

  • Check sample documents in Sanity
  • Verify Portable Text formatting
  • Confirm images loaded correctly
  • Test any links or embedded content

​
Current Limitations

Single Collection Per ImportMigrateKit currently handles one collection at a time. For sites with multiple related collections:
  • Migrate independent collections first
  • Note relationships for manual recreation
  • Rebuild references in Sanity after import
Multi-collection support with automatic reference resolution is on the roadmap.
No Reference Field SupportCross-collection references aren’t automatically migrated. You’ll need to manually recreate relationships in Sanity Studio after import.
See Limitations for a complete list.

​
Get Started

Ready to migrate? Choose your path:

Quickstart (10 min)

Fast track migration guide

Prerequisites

What you need before starting

​
Need Help?

Troubleshooting

Common issues and solutions