CMS Migration & Replatforming
Everything about migrating between CMS platforms, replatforming strategies, and content migration best practices.
Start Here
New to CMS Migration & Replatforming? Start with these fundamentals.
How to Build a Business Case for CMS Migration
Build a CMS migration business case by quantifying the costs of your current platform (hosting, maintenance, developer time, lost productivity), projecting migration and new platform costs, and calculating expected benefits (faster publishing, reduced maintenance, new capabilities). Include both hard costs and soft costs — editor frustration and slow delivery have real dollar values. Present ROI over a 3-year horizon to show long-term value, not just upfront investment.
IntermediateQuick AnswerHow to Calculate ROI of a CMS Migration
Calculate CMS migration ROI by comparing total cost of ownership (TCO) before and after migration over 3 years. Include direct costs (licensing, hosting, development) and indirect costs (maintenance hours, content team productivity, downtime losses). Factor in benefits like faster time-to-market, reduced developer maintenance, improved conversion rates from better performance, and new revenue from omnichannel capabilities. The formula: **ROI = (Net Benefits − Migration Cost) / Migration Cost × 100%**.
IntermediateQuick AnswerHow Much Does a CMS Migration Cost?
CMS migration costs range from $5,000–$25,000 for small sites, $25,000–$100,000 for mid-size sites, and $100,000–$500,000+ for enterprise projects. The total includes platform licensing, development fees, content cleanup, QA, and team training. The largest variable is developer time — content modeling, migration scripting, integration work, and testing account for 60–70% of most migration budgets.
BeginnerQuick AnswerHow to Handle Content Freeze During CMS Migration
A content freeze is a period during CMS migration when editors stop making changes in the old CMS so the final migration run captures all content accurately. Keep the freeze as short as possible — ideally 1–3 days — by running multiple rehearsal migrations beforehand. Communicate the freeze schedule well in advance, have editors front-load urgent content updates, and consider a delta migration approach that only migrates changes since the last full run to minimize the freeze window.
IntermediateQuick AnswerHow to Export Content from Drupal
Drupal content can be exported via JSON:API (enabled by default in Drupal 9+), the Views Data Export module for CSV/XML exports, the Migrate API for structured exports, or direct database queries. JSON:API is the most modern approach, providing RESTful access to all entity types with their fields and relationships. For complex sites with paragraphs, media entities, and custom field types, you may need to combine multiple methods.
IntermediateQuick AnswerHow to Export Content from WordPress
WordPress offers four export methods: the built-in XML export (Tools → Export), the WP REST API for programmatic access, WP-CLI for command-line exports, and direct database queries for complete data extraction. The built-in export works for basic posts and pages, but for custom post types, ACF fields, and WooCommerce data, the REST API or direct database access gives you more control and complete data.
BeginnerQuick AnswerHow Long Does a CMS Migration Take?
Small sites (under 500 pages) typically take 2–6 weeks. Mid-size sites (500–5,000 pages) take 6–16 weeks. Enterprise migrations with complex integrations, large content volumes, or regulatory requirements can take 3–12 months. The biggest variables are content volume, content complexity, number of integrations, and team availability — not the CMS platforms themselves.
BeginnerQuick AnswerHow to Import Content into a Headless CMS
Importing content into a headless CMS means using the platform's management API or CLI tools to create documents programmatically. Prepare your content as JSON matching the target schema, write an import script that creates documents in batches (handling rate limits), upload media assets separately, and then link assets to their parent documents. Most headless CMS platforms support bulk operations for efficient large-scale imports.
IntermediateQuick AnswerHow to Migrate CMS Content Without Losing SEO
Build a complete URL map, implement 301 redirects before or at go-live, preserve all meta titles and descriptions, maintain internal link structure, and submit an updated sitemap to Google Search Console on launch day. Monitor organic traffic and crawl errors daily for 4–8 weeks. Expect a temporary 10–20% traffic dip in the first two to four weeks — this is normal and recovers if redirects are implemented correctly.
IntermediateQuick AnswerHow to Migrate CMS Plugins and Extensions
CMS plugins and extensions don't migrate directly between platforms — you need to identify what each plugin does, determine if the new CMS has equivalent built-in functionality or its own plugins, and rebuild custom functionality where needed. Audit all active plugins, categorize them by function (SEO, forms, analytics, security, custom logic), find equivalents in your new CMS ecosystem, and plan custom development for any gaps. Many legacy CMS plugins address limitations that modern headless CMS platforms solve natively.
AdvancedQuick AnswerHow to Migrate CMS Workflows and Permissions
Migrating CMS workflows and permissions requires documenting your current editorial workflows (draft → review → publish), user roles, and permission rules, then recreating them in your new CMS. Workflow logic doesn't transfer automatically — you'll configure roles, define document-level permissions, and set up approval chains from scratch. Treat the migration as an opportunity to simplify permission structures that accumulated over years of ad-hoc changes.
AdvancedQuick AnswerHow to Migrate Content with Custom Fields
Migrating custom fields requires mapping each source field to a corresponding field in your new CMS schema. Export custom field data alongside your content, write transformation scripts to convert data types and formats — date strings, relationship IDs, select options — and validate that all field data imports correctly. Repeater fields, flexible content blocks, and relationship references need special handling and should be tested thoroughly before production cutover.
IntermediateQuick Answer
CMS Migration Checklist
A complete CMS migration checklist covers four stages: pre-migration (content audit, stakeholder alignment, platform selection, content modeling), execution (export, transform, media migration, URL mapping), testing (content verification, link checking, SEO validation, performance benchmarking), and post-migration (301 redirects live, monitoring active, team trained, old system decommissioned). Check off every item — skipped steps are the leading cause of SEO loss and data gaps after launch.
IntermediateQuick AnswerCMS Migration Project Plan Template
A CMS migration project plan should include six phases: Discovery (2–4 weeks for content audit, requirements, and platform selection), Design (2–4 weeks for content modeling and frontend architecture), Build (4–8 weeks for migration scripts, frontend development, and integration setup), Migrate (1–2 weeks for content import, media migration, and redirect setup), Test (2–3 weeks for QA, UAT, and performance testing), and Launch (1 week for cutover, monitoring, and training). Assign owners to each phase and build in buffer time for unexpected issues.
IntermediateQuick AnswerWhat Are the Risks of a CMS Migration?
The five major CMS migration risks are: SEO loss from missing or incorrect 301 redirects, data loss from incomplete field mapping, unplanned downtime during cutover, scope creep that extends timelines and budgets, and editor resistance to new workflows. Each risk is manageable with the right preparation — staging environments, comprehensive redirect maps, automated content validation, and change management planning.
IntermediateQuick Answer