Current Limitations & Roadmap

​

What’s Supported Today

MigrateKit currently provides robust CSV-based migration from Webflow to Sanity:

​

Current Limitations

​

Single Collection Per Import

Status: ⚠️ Limitation MigrateKit handles one Webflow collection at a time. Impact:

• Must import collections separately
• Can’t resolve references automatically
• Manual reference recreation required

Workaround:

1. Import independent collections first
2. Note relationship data
3. Import dependent collections
4. Manually link references in Sanity Studio

Future: Multi-collection support with automatic reference resolution is on the roadmap.

---

​

No Reference Field Support

Status: ⚠️ Limitation Cross-collection relationships aren’t migrated automatically. Impact:

• Reference fields can’t be mapped
• Relationships must be recreated manually
• Multi-reference fields not supported

Workaround:

• Map reference columns as string (preserves ID/slug)
• After import, manually link references in Sanity Studio
• Document relationships before migration for easy recreation

Example: Webflow: Post → Author (reference field) MigrateKit: Map author as string (stores author ID) After import: Convert to Sanity reference manually Future: Reference resolution with deterministic ID matching coming soon.

---

​

Webflow-Only Sources

Status: ⚠️ Limitation MigrateKit is optimized for Webflow CSV exports. Impact:

• Other CMS exports (WordPress, Contentful, etc.) not officially supported
• May work if CSV structure is similar, but no guarantees

Future: WordPress and other CMS support planned for Q3 2025.

---

​

System Timestamps

Status: ⚠️ Limitation Sanity controls _createdAt, _updatedAt, and _publishedAt fields. Impact:

• Can’t preserve original Webflow timestamps in system fields
• Imported documents get new Sanity timestamps

Workaround:

• Map Webflow timestamps to custom fields:
  • Created On → webflowCreatedAt
  • Published On → webflowPublishedAt
• Preserve original dates for reference

Note: This is a Sanity limitation, not a MigrateKit limitation.

---

​

No Schema Generation

Status: ⚠️ Limitation (MVP) You define schema during mapping, but MigrateKit doesn’t generate Sanity schema files. Impact:

• Must manually create schema in Sanity Studio if you want:
  • Custom validation
  • Field configurations
  • UI customizations

Current approach:

• Map fields in MigrateKit (defines structure)
• Import creates documents
• Manually create matching schema in Sanity if needed

Future: Automated schema generation coming soon—MigrateKit will create Sanity schema files based on your mapping.

---

​

Limited Batch Size

Status: ⚠️ Practical Limitation Very large imports (>5,000 rows) may be slow. Impact:

• Large migrations take longer
• Memory/timeout constraints for massive datasets

Workaround:

• Split large collections into batches
• Import during off-peak hours
• Consider ContentWrap Pro for larger limits

Note: Most Webflow collections are well under this limit.

---

​

Feature Comparison

​

Roadmap

​

Phase 1: Core Migration ✅ (Complete)

• CSV upload and parsing
• Visual field mapping
• HTML to Portable Text conversion
• Asset migration
• Draft mode import
• Webflow-optimized workflow

​

Phase 2: References & Multi-Collection 🚧 (In Progress)

• Automatic reference resolution using deterministic IDs
• Multi-collection import in single workflow
• Relationship mapping interface
• Cross-collection validation

​

Phase 3: Schema & Automation 📋 (Planned)

• Automated Sanity schema generation
• Export schema files for Studio
• Schema validation and best practices
• Reusable mapping templates

​

Phase 4: Multi-CMS Support 📋 (Planned)

• WordPress CSV/XML import
• Contentful export support
• Generic CSV import (any CMS)
• Custom mapping for non-standard formats

​

Phase 5: Advanced Features 📋 (Future)

• Incremental sync (update changed content)
• Scheduled migrations
• Migration preview/rollback
• Bulk operations API
• Custom transformation scripts

​

Get Updates

​

Working Within Current Limitations

​

Best Practices

​

Request Features

Have a specific use case or need? We’d love to hear from you:

​

Enterprise Support

Need capabilities beyond current limits?