01
Getting the content out
On Headless / React (Next.js), content leaves through CMS APIs (GROQ, GraphQL, REST) and dataset exports. 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 Headless / React (Next.js) to Drupal, export your content through CMS APIs (GROQ, map it to the Drupal content model, import it with repeatable scripts, and 301-redirect every old URL before switching DNS. For a mid-size site this takes 6–10 weeks and typically costs CA$26,000–$51,500. 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 Headless / React (Next.js) to Drupal 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 Headless / React (Next.js), content leaves through CMS APIs (GROQ, GraphQL, REST) and dataset exports. We script the extraction so it can be re-run for a final delta just before launch.
02
On Drupal, we load content with Drupal Migrate API (migrate_plus, migrate_tools) with YAML mappings and rollback. Scripts are idempotent, so we can wipe and re-import on staging as often as needed.
03
Headless / React (Next.js) stores content as schema-defined document types with structured fields, references and portable rich text. Drupal uses content types, fields, paragraphs, taxonomy vocabularies, media entities and entity references. The gap between the two decides how much transformation and manual clean-up is needed.
04
Headless / React (Next.js) URLs typically follow fully custom routing defined in code, while Drupal uses /node/123 system paths aliased by pathauto patterns. Metatag, Pathauto, Redirect and Simple XML Sitemap modules hold SEO data; the redirect table must be preserved.
05
Headless / React (Next.js) relies on npm ecosystem and cms plugins; Drupal offers 50,000+ contributed modules. Each feature in use is listed, then mapped to a native feature, an app or custom code, or retired.
06
Expect CA$100–$2,500/month hosting depending on scale on Drupal, compared with CA$0–$1,500/month hosting and CMS depending on usage on Headless / React (Next.js). 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 Headless / React (Next.js) site lands in Drupal.
| Headless / React (Next.js) | Drupal | How we handle it |
|---|---|---|
| Document schemas | Content types, fields and paragraphs | 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 | Drupal SEO fields and JSON-LD | Needs server-side rendering or static generation for crawlability; redirects and sitemaps are handled in code or at the edge. |
| URLs | /node/123 system paths aliased by Pathauto patterns | 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. |
Crawl the Headless / React (Next.js) site, export analytics and Search Console data, and inventory every template, feature and integration.
Design the Drupal content model and templates, then approve designs for each page type.
Build Drupal 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$19,500–$38,500 | 5–8 weeks |
| Mid-size site | 150 | CA$26,000–$51,500 | 6–10 weeks |
| Large site | 600 | CA$42,500–$85,000 | 11–17 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. |
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