What this prompt does
This prompt plans a migration from WordPress to [target_cms] for a site with [content_volume]. It produces a content audit mapping WordPress types to [target_cms] types, an ACF and custom-field migration strategy, a media plan for [media_count] files, a URL-preservation and 301 redirect map, an SEO migration checklist, a target content model, a migration script for [migration_approach], a staging workflow, a team training plan, and a rollback strategy — all within a [timeline_weeks]-week plan that preserves [seo_metrics].
The structure works because the danger in a CMS migration is losing traffic, not moving data. Mapping content first means nothing falls through the cracks, and the redirect map plus SEO checklist are what protect rankings. The [migration_approach] defines how automated versus manual the move is, while the content-freeze window and post-migration verification checklist keep the cutover clean and reversible.
When to use it
- You're moving off WordPress to
[target_cms]and can't afford to lose traffic - You need a 301 redirect map to preserve URLs and protect
[seo_metrics] - You have
[content_volume]and[media_count]to migrate without manual drudgery - You want a
[migration_approach]defined — automated script versus manual review - You need a content-freeze window and rollback plan for a safe cutover
- You want a target content model designed before any data moves
Example output
Expect a migration plan: a content audit and type mapping, a custom-field strategy, a media migration plan, a URL and 301 redirect map, an SEO checklist, a [target_cms] content model, a migration script outline for [migration_approach], a staging workflow, a training plan, a rollback strategy, a risk assessment, a content-freeze window, and a post-migration verification checklist over [timeline_weeks] weeks.
Pro tips
- Treat the 301 redirect map as the highest-priority artifact — broken URLs are the fastest way to lose
[seo_metrics] - Be honest about
[content_volume]and[media_count]; underestimating them wrecks the timeline and script scope - Use
[migration_approach]to flag which content needs manual review — complex layouts rarely migrate cleanly automatically - Keep the content-freeze window short but real; editors changing content mid-migration causes drift and data loss
- Test the rollback plan before cutover, not after something breaks
- Run the post-migration verification checklist before announcing — verify indexed pages, redirects, and Core Web Vitals first
