How to Migrate a WordPress Site to Strapi with Claude Code

A Claude Code skill for migrating WordPress sites to Strapi v5 uses the WordPress REST API to export content, infer Strapi content types and components, generate a configurable migration plan, and move entries, media, and relations after human review. The migration separates reusable content such as titles, dates, images, authors, and structured page sections from WordPress theme presentation settings, while encouraging improvements such as typed fields, relations, repeatable components, and dynamic zones for page-builder layouts. Its main caution is that WordPress custom post types and fields may be absent from the REST API unless explicitly enabled, allowing incomplete migrations to appear successful; a temporary helper plugin and authenticated API requests can expose these hidden items. The workflow consists of export, analysis, review, schema generation, migration, and verification, supports repeat runs without duplicates through stored WordPress IDs, and provides reports for unsupported widgets, missing media, URL changes, and old-domain references. Tests on a practice site and a commercial-theme demo migrated content successfully but identified issues including hidden ACF and Meta Box fields, Elementor layouts, unsupported SVG uploads, page-builder widgets requiring reconstruction, tables flattened in rich text, orphaned media, comments, WooCommerce data, and multilingual content that need separate handling. The guidance recommends practicing on a copy, deciding URL and content-model rules before migration, using dry runs and incremental batches, and using database-level tools or custom scripts for very large sites.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.