1: Introduction to content migrations
Gain the technical know-how to successfully migrate content to Sanity, adapting to unique project needs and confidently handling transactions and mutations.
2: General migration principles
A developer guide to content migration covering idempotent scripts with incremental complexity and considered error handling.
3: Content normalization
Migrating is an opportunity not only to move your content to Sanity, but your content strategy to structured content.
4: Deterministic and consistent IDs
Reusing existing values from your content source helps prevent duplicate data and optimistically set strong references.
5: Setting created and modified dates
While the Content Lake stores date time values for document operations, it may be better to write your own for editorial purposes.
6: Validating incoming content
Never trust your existing content source. Validate all data during a migration to avoid future headaches.
7: Scripting content migrations
Sanity's API-first design allows you to write content – even in huge volumes – however you prefer. The CLI Migration tooling offers several conveniences that make it a great fit.
8: Uploading assets efficiently
Effortlessly manage and transform high-resolution images with Sanity's asset pipeline, avoid unnecessary uploads, and optimize content migration with metadata and in-memory cache.
9: Migrating to block content
Convert HTML to presentation-agnostic Portable Text, even handling complex block content from WordPress' Gutenberg editor.
10: Reducing SEO impact
Confidently migrate content into Sanity, maintain SEO standing, manage redirects, and prevent broken links. Ensure visual consistency with automated testing.
11: Conclusion
You're now equipped to navigate content migration with a unique, well-documented strategy, adopting new technologies smoothly and predictably.