cms-migration
Use when user wants to migrate content from another CMS (WordPress, Contentful, Strapi, Sanity, Webflow, etc.) to Payload CMS
Install
With your agent
Install OMGSkills skill "payloadcms/skills:cms-migration" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/payloadcms/skills /tmp/skills && ln -s /tmp/skills/skills/cms-migration ~/.claude/skills/cms-migrationFrom README
CMS Migration to Payload Interactive workflow to design Payload collections from source CMS data. Config-first approach: establish the data structure through conversation before any data import. Workflow Phase 1: Data Analysis When user provides data (JSON, CSV, or describes their schema): Identify field types - text, number, date, relationships, media, rich text Spot patterns - IDs, timestamps, nested objects, arrays Note relationships - foreign keys, embedded refs, linked content types Flag ambiguities - fields that could be multiple types, unclear purposes Phase 2: Propose Collection Config Present a Payload collection config based on analysis: Explain your reasoning for each field choice. When something could go multiple ways (group vs JSON, text vs textarea, select vs relationship), ask rather than assume. Phase 3: Iterate with User Work through uncertainties: required fields, hasMany relationships, rich text vs HTML, custom timestamps vs built-in.