sanity-migrationlisted

# Sanity Migration Use this skill for CMS-to-Sanity migration work. Treat migration as a content strategy and ETL project, not a blind lift-and-shift. ## Required Workflow 1. Read `references/general.md` first. 2. If the source platform is known, also read its guide: - AEM / Adobe Experience Manager: `references/aem.md` - Contentful: `references/contentful.md` - Strapi: `references/strapi.md` - Webflow: `references/webflow.md` - WordPress / WXR / Elementor: `references/wordpress.md` - Payload: `references/payload.md` - Drupal: `references/drupal.md` - Markdown / MDX / frontmatter files: `references/markdown.md` 3. Before writing code, produce a short migration plan covering source access, content scope, schema decisions, extraction, transformation, import, validation, redirects, and cutover. 4. Prefer deterministic, repeatable scripts for real migrations. Write and review migration scripts, mappings, and validation checks; do not rely on one-off content operations for large content volumes. ## Deliverables to Produce For implementation or planning tasks, produce these artifacts or explain why they are not needed: - Content inventory: source types, counts, locales, status/draft scope, assets, and relationship types. - Source-to-Sanity mapping: document types, object types, references, Portable Text fields, asset fields, IDs, and skipped content. - Extraction approach: credentials/access needed, API/export commands, raw snapshot location, and known