01
Getting the content out
On WordPress, content leaves through WXR XML export, REST API (/wp-json), direct MySQL access and WP-CLI. We script the extraction so it can be re-run for a final delta just before launch.
CMS migration plan
Short answer
To migrate from WordPress to a headless React (Next.js) stack, export your content through WXR XML export, map it to the Headless content model, import it with repeatable scripts, and 301-redirect every old URL before switching DNS. For a mid-size site this takes 6–9 weeks and typically costs CA$23,500–$47,000. DoodleWeb Canada plans and runs the whole move from Surrey, BC.
A senior engineer reads every message and replies within one working day.
Five stages take your site from WordPress to Headless / React (Next.js) without downtime or lost search traffic.
These are the questions that decide scope, cost and risk. We answer each one in the free audit.
01
On WordPress, content leaves through WXR XML export, REST API (/wp-json), direct MySQL access and WP-CLI. We script the extraction so it can be re-run for a final delta just before launch.
02
On Headless / React (Next.js), we load content with CMS import APIs and scripted transforms (Node.js). Scripts are idempotent, so we can wipe and re-import on staging as often as needed.
03
WordPress stores content as posts, pages, custom post types, taxonomies and custom fields (acf or native meta). Headless / React (Next.js) uses schema-defined document types with structured fields, references and portable rich text. The gap between the two decides how much transformation and manual clean-up is needed.
04
WordPress URLs typically follow /%postname%/ or /blog/%postname%/ permalinks, category and tag archives, while Headless / React (Next.js) uses fully custom routing defined in code. Needs server-side rendering or static generation for crawlability; redirects and sitemaps are handled in code or at the edge.
05
WordPress relies on 60,000+ plugins in the wordpress.org directory; Headless / React (Next.js) offers npm ecosystem and cms plugins. Each feature in use is listed, then mapped to a native feature, an app or custom code, or retired.
06
Expect CA$0–$1,500/month hosting and CMS depending on usage on Headless / React (Next.js), compared with CA$30–$600/month hosting plus plugin licences on WordPress. We include this in the scope so the business case is complete.
07
We rebuild templates to WCAG 2.2 AA and, for Canadian organisations with French content, plan language switching and hreflang before import.
How each part of your WordPress site lands in Headless / React (Next.js).
| WordPress | Headless / React (Next.js) | How we handle it |
|---|---|---|
| Pages and posts | Schema-defined document types | Each source type is mapped field by field in a signed-off content model before any data moves. |
| Categories and tags | Taxonomies | Terms are de-duplicated and merged where the old site accumulated near-identical tags. |
| Media library and images | Media library | Files are downloaded, renamed, compressed and re-linked, with alt text carried over or written. |
| SEO titles, descriptions and schema | Headless SEO fields and JSON-LD | Titles, descriptions and schema usually live in Yoast or Rank Math meta fields, which must be extracted separately from post content. |
| URLs | Fully custom routing defined in code | Every indexed URL gets a one-to-one 301 redirect; pattern rules cover the long tail. |
| Forms and integrations | Native forms or CRM embeds | CRM, email and analytics connections are rebuilt and tested with real submissions. |
| Users and roles | Headless team roles | Editor accounts are recreated and permissions reviewed rather than copied blindly. |
Crawl the WordPress site, export analytics and Search Console data, and inventory every template, feature and integration.
Design the Headless / React (Next.js) content model and templates, then approve designs for each page type.
Build Headless / React (Next.js) templates and run repeatable import scripts onto staging, checking counts and spot-checking content.
Test accessibility, speed, forms and integrations; validate every redirect; train editors.
Final delta import, DNS cutover in a quiet window, sitemap submission and daily Search Console checks for 30 days.
Week 0 → 17
Ranges come from our migration cost calculator and include a design refresh, redirects, accessibility QA and launch monitoring. Your fixed price follows the audit.
| Site size | Approx. pages | Cost (CAD) | Timeline |
|---|---|---|---|
| Small site | 30 | CA$17,500–$34,500 | 4–7 weeks |
| Mid-size site | 150 | CA$23,500–$47,000 | 6–9 weeks |
| Large site | 600 | CA$39,500–$79,000 | 10–16 weeks |
Try the migration cost calculator for your own numbers.
| Risk | Impact | Mitigation |
|---|---|---|
| Lost rankings from broken URLs | High | One-to-one 301 map for every indexed URL, tested with a crawler before and after launch. |
| Content lost or mangled in transit | Medium | Scripted imports with record counts, rollback and side-by-side parity checks. |
| Missing features after launch | Medium | Feature map signed off during discovery, so nothing is dropped by surprise. |
| Pages invisible to search engines | Medium | Server-side rendering or static generation, verified with fetch-as-Google tests. |
A senior engineer reviews your site and replies within one working day. DoodleWeb Canada · Surrey, BC · +1-425-359-0168
Get your free auditQ&A