CMSmigrationchecklist:40stepsforasafemovein2026

Short answer: a safe CMS migration follows six phases — audit, content mapping, build, content migration, SEO and QA, then launch and monitoring. The checklist below covers every step. The two items that protect you most are a complete URL redirect map and a staging review with real editors before launch.

What should you do before choosing a new CMS?

• [ ] List why you are moving: cost, speed, editor experience, security, features.
• [ ] Write down who edits the site and how often.
• [ ] List every integration: CRM, forms, analytics, search, payments, SSO.
• [ ] Compare two or three platforms on those needs. Our platform comparisons help.

Phase 1: How do you audit the current site?

• [ ] Crawl every URL (including PDFs and images) and save the list.
• [ ] Export 12 months of analytics and Search Console data.
• [ ] Flag the top 100 pages by traffic, links and conversions.
• [ ] Inventory content types, taxonomies, plugins or modules, and users.
• [ ] Decide what to keep, merge, rewrite or delete.

Phase 2: How do you map content to the new platform?

• [ ] Map every field and template from old to new.
• [ ] Agree on the new URL structure.
• [ ] Build the redirect map: every old URL to its best new URL (one-to-one, no chains).
• [ ] Decide how images, authors, dates and categories will move.

Phase 3: What matters during the build?

• [ ] Build in staging, never on the live domain.
• [ ] Rebuild components, not pages — editors should assemble pages from blocks.
• [ ] Reconnect integrations and test each one.
• [ ] Carry over structured data (Organization, Article, Product, FAQ, Breadcrumb).
• [ ] Hit Core Web Vitals targets before content goes in.

Phase 4: How do you move the content?

• [ ] Run a test import on a sample and check formatting.
• [ ] Run the full import with scripts or migration tools, not copy-paste.
• [ ] Fix broken internal links and embedded media.
• [ ] Have real editors review their own sections in staging.

Phase 5: What should the SEO and QA pass check?

• [ ] Titles, meta descriptions and H1s match or improve on the old site.
• [ ] Canonical tags point to the page itself.
• [ ] Redirects tested in bulk (every old URL returns a single 301).
• [ ] New XML sitemap and robots.txt ready.
• [ ] Forms, tracking and conversion events fire correctly.
• [ ] Accessibility check on key templates.

Phase 6: What do you do on launch day and after?

• [ ] Launch outside your busiest period.
• [ ] Remove any staging noindex tags.
• [ ] Submit the new sitemap in Google Search Console and Bing Webmaster Tools.
• [ ] Watch 404s, crawl errors and rankings daily for two weeks, weekly for two months.
• [ ] Keep the old site's backup for at least 90 days.

How long does a CMS migration take?

Small marketing sites take 4–8 weeks. Content-heavy or ecommerce sites take 8–16 weeks. Large multi-site, multilingual or government sites can take 4–6 months. See platform-specific plans on our migration hub, such as Drupal to WordPress or WordPress to Webflow.

Want a second pair of eyes on your plan? Talk to DoodleWeb.