> ## Documentation Index
> Fetch the complete documentation index at: https://docs.contentwrap.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Migration Overview

> Understand MigrateKit's 4-step CSV migration process from Webflow to Sanity with automated field mapping and HTML conversion.

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.

<Steps>
  <Step title="Connect Sanity">
    Add your Project ID, dataset, and API token in ContentWrap
  </Step>

  <Step title="Export from Webflow">
    Download your collection as a CSV file
  </Step>

  <Step title="Upload & Map Fields">
    Upload CSV and map Webflow columns to Sanity fields
  </Step>

  <Step title="Import & Verify">
    Execute migration and review drafts in Sanity Studio
  </Step>
</Steps>

## What Happens During Migration

<AccordionGroup>
  <Accordion title="Field Mapping">
    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`
  </Accordion>

  <Accordion title="HTML to Portable Text Conversion">
    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](/concepts/html-conversion)
  </Accordion>

  <Accordion title="Asset Migration">
    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](/concepts/field-mapping#image-fields)
  </Accordion>

  <Accordion title="Draft Mode Import">
    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
  </Accordion>
</AccordionGroup>

## Migration Flow

```mermaid theme={null}
graph LR
    A[Connect Sanity] --> B[Export Webflow CSV]
    B --> C[Upload CSV]
    C --> D[Map & Preview]
    D --> E[Import to Sanity]
    E --> F[Review Drafts]
    F --> G[Publish]
```

## Step-by-Step Guides

Follow detailed instructions for each phase:

<CardGroup cols={2}>
  <Card title="Step 1: Connect Sanity" icon="link" href="/migration/step-1-connect-sanity">
    Link your Sanity project with API credentials
  </Card>

  <Card title="Step 2: Export" icon="download" href="/migration/step-2-export">
    How to export CSVs from Webflow correctly
  </Card>

  <Card title="Step 3: Upload & Map" icon="diagram-project" href="/migration/step-3-upload-map">
    Upload CSV and define field mappings
  </Card>

  <Card title="Step 4: Import" icon="cloud-arrow-up" href="/migration/step-4-import">
    Execute migration and verify results
  </Card>
</CardGroup>

## Best Practices

<Steps>
  <Step title="Start Small">
    * Test with a small collection (10-50 items)
    * Use a development dataset first
    * Verify the workflow works
    * Refine mappings before scaling
  </Step>

  <Step title="Keep Backups">
    * Save original CSV files
    * Don't delete Webflow data until verified
    * Export from Sanity for additional backup
  </Step>

  <Step title="Plan Your Schema">
    * Decide on document type names
    * Choose appropriate field types
    * Consider Sanity naming conventions
    * Think about future content structure
  </Step>

  <Step title="Review Before Publishing">
    * Check sample documents in Sanity
    * Verify Portable Text formatting
    * Confirm images loaded correctly
    * Test any links or embedded content
  </Step>
</Steps>

## Current Limitations

<Warning>
  **Single Collection Per Import**

  MigrateKit 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.
</Warning>

<Info>
  **No Reference Field Support**

  Cross-collection references aren't automatically migrated. You'll need to manually recreate relationships in Sanity Studio after import.
</Info>

See [Limitations](/reference/limitations) for a complete list.

## Get Started

Ready to migrate? Choose your path:

<CardGroup cols={2}>
  <Card title="Quickstart (10 min)" icon="rocket" href="/quickstart">
    Fast track migration guide
  </Card>

  <Card title="Prerequisites" icon="list-check" href="/prerequisites">
    What you need before starting
  </Card>
</CardGroup>

## Need Help?

<Card title="Troubleshooting" icon="wrench" href="/troubleshooting/common-issues">
  Common issues and solutions
</Card>