DRUPAL / WORDPRESS / SEO

Drupal to WordPress Migration: Complete SEO-Safe Guide & Checklist (2026)

A practical Drupal to WordPress migration checklist for 2026: Drupal 7/10/11, content types, ACF field mapping, media, 301 redirects, staging and Search Console.

By BitwiseCode Engineering Detailed migration checklist
Drupal to WordPress SEO-safe migration overview
Plan the content move, images and URL redirects together—not as separate last-minute fixes.

Migrating Drupal to WordPress is rarely a simple export-and-import exercise. Drupal may hold articles, custom content types, entity references, taxonomy vocabularies, media, users and URL aliases that do not map automatically to ordinary WordPress posts. A successful migration starts by deciding what each piece of Drupal content should become—and how visitors will reach it after launch.

MIGRATION ROADMAP / 2026

How to migrate Drupal to WordPress safely

  1. Audit Drupal: identify the version, content types, fields, taxonomies, media, users, forms, URLs and integrations.
  2. Back up everything: take verified database, code and file backups and export search performance.
  3. Design the WordPress content model: plan posts, pages, custom post types, fields and taxonomies.
  4. Test an import on staging: compare counts, relations, media and formatting.
  5. Map old URLs: preserve Drupal aliases where appropriate or implement page-specific permanent redirects.
  6. Launch with a rollback plan: check HTTPS, canonicals, sitemap, analytics and the highest-value paths.
  7. Monitor: resolve 404s and validate index coverage and search performance after cutover.

SEO reality: a site move can cause temporary changes in organic visibility. No migration service can guarantee unchanged rankings; careful URL mapping and validation reduce avoidable losses.

1. Drupal 7, Drupal 10 or Drupal 11? Start with the source version

First confirm the site’s Drupal core version and installed modules. The migration method depends on the data model and database schema; even sites on the same Drupal major version can use very different field and entity structures.

SourceCurrent planning concernMigration approach
Drupal 7Official security support ended January 5, 2025.Prioritize the inventory and security plan. Check legacy field collections, custom modules, aliases and content references.
Drupal 10Drupal.org lists December 9, 2026 as end of life.Assess content entities, media, paragraphs and current integrations; compare the cost of WordPress migration with upgrading within Drupal.
Drupal 11Modern Drupal with complex content and application features.Map modern entity relationships, permissions, paragraphs and reusable components. Rebuild non-content functionality deliberately.

These dates come from the official Drupal release schedule and Drupal 7 end-of-life announcement. Moving to WordPress is one option—not an automatic requirement. If Drupal’s multilingual, permission and workflow capabilities are central to the business, compare the ongoing cost of migration with an upgrade to a supported Drupal version.

Important for Drupal 7: do not expose an obsolete source database or admin interface to the public while staging WordPress. Use restricted access, backups and a defined retirement plan.

2. Audit everything before deciding on the importer

A migration begins with a content and behavior inventory, not a plugin installation. Export a list of all published and unpublished content, URLs, node IDs, aliases and the fields attached to each content type. Record any external services that depend on the Drupal website.

  • Content: Articles, basic pages, custom content types, revisions, publication states, authors and timestamps.
  • Fields: Text, dates, files, images, entity references, paragraphs, repeatable groups and rich-text formats.
  • Taxonomy: Vocabularies, terms, hierarchical relationships and SEO-important term archives.
  • Users: Account counts, roles, editorial access and whether password continuity is required.
  • Media: Files under paths such as /sites/default/files/, reusable media entities, embedded video and PDFs.
  • URL and SEO: System paths, aliases, existing redirects, canonical tags, sitemap, XML feeds, page titles, metadata and highest-traffic pages.
  • Functions: Webforms, content moderation, multilingual translation, search, subscriptions, ecommerce, access rules and custom integrations.

Also record baseline Google Search Console data for the previous three months: top queries, pages with clicks, indexed pages and backlinks. Export the major landing-page URLs into a spreadsheet before editing permalinks or DNS.

Worked example: a content-rich association website

Imagine an association running Drupal with 420 news articles, 35 staff pages, 80 events, 12 downloadable reports and multilingual content. WordPress’s standard posts importer may handle news articles, but it won’t automatically reconstruct the staff profile fields, events calendar, translated relationships or event registration flow. Those become explicit workstreams in your migration plan.

Drupal sourceNews · Staff · Events · Media · Taxonomy
WordPress modelPosts · Staff CPT · Events CPT · Media Library · Terms
ValidationContent · Relationships · URLs · SEO

3. Design your WordPress content model

WordPress and Drupal use different models. Define the destination data structure before the import, particularly for custom fields and repeatable content. WordPress custom post types and Advanced Custom Fields may be useful, but the correct model depends on how content must be edited, searched and displayed.

Example Drupal dataPossible WordPress destinationWhat must be checked
Article nodesPostsBody, title, date, author, category and permalink
Basic pagesPagesHierarchy, URL, navigation placement
Staff content typeCustom post type + custom fieldsJob title, portrait, department and profile relationships
Topic vocabularyCategories or custom taxonomyTerm hierarchy, archive URL, canonical rules
Paragraphs / referencesFlexible content, blocks or custom relationshipsRepeatable sections, ordering, embedded items
File/media entitiesMedia Library + attachment metadataFile URLs, metadata, captions and references

In this example, a staff profile might have Drupal fields named field_position, field_department and field_photo. An agreed WordPress model could include a staff custom post type with ACF fields named position, department and portrait. The importer needs an explicit mapping rather than simply copying field names and expecting the theme to know what to display.

4. Choose the migration method: plugin, structured export or custom script

There are three broad ways to move data. The right choice depends on source access, amount of content, complexity, supported modules, and how repeatable the migration needs to be.

Option A: FG Drupal to WordPress importer

The FG Drupal to WordPress plugin offers database-based migration of core content such as articles, pages, terms and images. Its documentation states compatibility with Drupal 4–11, but you should test the specific installed version on staging.

Typical setup involves installing the plugin in WordPress, opening Tools → Import → Drupal, supplying the source database parameters from the correct Drupal configuration, and running an initial import. The destination environment must be allowed to connect to the Drupal database.

Pay attention to the free and Premium distinction: the plugin’s WordPress.org listing identifies users, comments, custom fields, custom post types, some SEO URL redirection features and various advanced modules as Premium features or additional add-ons. Do not assume a basic free import will recreate your complete business website. Confirm current licensing and plugin support before purchasing or deploying.

Option B: Structured export and transformation

For restricted databases or unusual content, export Drupal records to JSON or CSV through a controlled pipeline, map fields and relationships, then import them into WordPress. This is often suitable for sites that need deterministic field mapping and repeatable test runs.

Option C: Custom migration scripts

For complex websites, a custom process can create or update WordPress posts and metadata through authenticated APIs, WP-CLI or server-side code. The script should track the original Drupal node ID, map references, handle retries without creating duplicates and log validation failures. Build rollback and dry-run capability into the design.

Engineering principle: importing 1,000 posts successfully is not the same as migrating 1,000 posts correctly. Always compare content counts, field values, dates, media and page destinations.

5. Run a controlled staging import and verify the result

Start from a backed-up WordPress staging installation with the destination fields and post types already registered. Use a small, representative subset first—simple pages, long articles, an item with images, an item with custom references and one with difficult formatting.

  1. Confirm source connectivity and inspect the importer’s supported Drupal version.
  2. Import the sample records with media enabled where appropriate.
  3. Check publication status, titles, HTML formatting, dates, authors and taxonomy assignments.
  4. Check custom fields and linked entities against the original Drupal records.
  5. Verify image URLs, alt text, captions and PDF attachments.
  6. Run a full import once the sample mappings are reliable; compare actual record counts by type.
  7. Document failures and repeat from a controlled checkpoint rather than running duplicate imports blindly.

For a larger site, build a reconciliation report. If Drupal contains 420 published news nodes but WordPress contains only 414 mapped news posts, investigate the six missing records and understand whether they were filtered, unpublished, errored or incorrectly assigned.

6. Preserve Drupal URLs and SEO signals

Drupal can serve the same node using an internal path such as /node/184 and a readable URL alias such as /news/growth-plan. A WordPress import might instead create /insights/growth-plan/. If the old URLs are indexed or linked from other websites, you need to account for those paths as part of your redirect plan.

Old Drupal URLNew WordPress URLRequired check
/news/growth-plan/insights/growth-plan/301 to the relevant post
/node/184/insights/growth-plan/Redirect if indexed or externally linked
/about-us/about/One-to-one page redirect
/taxonomy/term/14/category/research/Ensure the archive serves equivalent useful content
/sites/default/files/2024/report.pdf/wp-content/uploads/2026/11/report.pdfCheck target file and backlinks
Download the Drupal migration URL & content mapping sheet

Sample rows for Drupal aliases, node IDs, taxonomy archives and files. Replace them with your own source URLs, WordPress targets and validation notes.

Download CSV worksheet ↓

Do not redirect every obsolete URL to your homepage. The goal is a relevant destination for each retained resource. When you have control of the domain and server, configure permanent server-side redirects (301 or 308) and keep chains short. Google’s site move guidelines recommend maintaining redirects for at least a year where possible.

Example: simple Apache redirect rule

Redirect 301 /news/growth-plan https://www.example.com/insights/growth-plan/

This is an illustration for a domain whose requests now reach your Apache server. If the site uses Nginx, Cloudflare rules or a WordPress redirect plugin, configure the equivalent there. Check the site’s actual server behavior before adding rules.

Verify the HTTP response directly

curl -I https://www.example.com/news/growth-plan
curl -IL https://www.example.com/news/growth-plan
curl -I https://www.example.com/insights/growth-plan/

The first two commands inspect the initial status and redirect chain; the last verifies that the final page exists. For a correctly migrated changed URL, expect a relevant permanent redirect and a working 200 destination. Don’t treat a pretty-looking browser page as proof the response codes are right.

Aliases, canonicals, metadata and internal links

Export Drupal’s URL alias list, compare it with the site’s XML sitemap and important Search Console pages, then generate a mapping file. Preserve or deliberately rewrite page titles, headings, descriptions and canonical links. Update internal links in navigation and body content so they point directly to the new WordPress URL rather than creating redirect hops.

7. Handle media, users, forms, translations and other non-post data

Many migration defects occur outside the core posts table. Drupal’s file and media systems, especially on complex sites, need separate attention.

  • Media: move actual files from Drupal’s public or private storage, retain appropriate permissions, and update src, attachment, download and responsive-image references.
  • Users: map authors and roles carefully. Never assume Drupal password hashes automatically work in WordPress; use an agreed reset or supported migration procedure.
  • Forms: rebuild Drupal Webform functionality explicitly with an appropriate WordPress solution, including destination email routing and spam protection. Test actual submissions.
  • Multilingual: decide how translation groups, language switchers and localized URLs are represented with your selected WordPress language architecture.
  • Commerce or memberships: treat orders, subscriptions, product options, access rules and customer accounts as specialized data migrations, not basic article imports.
  • Search and analytics: rebuild internal search behavior where needed and confirm Google Analytics, consent and conversion events.
Security warning: never expose Drupal database credentials or private export archives publicly. Store imports securely, rotate temporary credentials after use and remove public staging access after cutover.

8. Launch checklist: technical SEO and Search Console

Once the importer and content model are validated, establish a final content freeze or delta-import plan, then schedule the cutover with a tested rollback path.

  1. Back up the source Drupal database and files and the destination WordPress state.
  2. Confirm production HTTPS, domain routing and canonical URLs.
  3. Remove unintended production noindex and staging-only blocks.
  4. Test the top twenty old URLs, then sample each content type and path pattern.
  5. Check WordPress sitemaps, language alternates (if any), navigation and internal linking.
  6. Check images, PDFs and media files used by important landing pages.
  7. Submit the sitemap to Google Search Console and inspect representative new pages.
  8. Verify GA4 traffic, forms and essential integrations.
  9. Monitor 404s, search indexing, click and impression trends over the following weeks.
Before launchFull backup; content and URL maps; representative import QA; rollback plan.
Launch dayDNS/HTTPS; highest-value redirects; canonical links; sitemap and forms.
First weekRecheck redirects, missing files, failed imports and search-index signals.
Days 30–90Compare landing-page traffic with baseline, investigate coverage issues and refine internal links.

Where you change the site’s domain, Google’s Change of Address tool may apply; when only the CMS or hosting changes and the domain stays the same, focus on the URL/redirect and sitemap checks. Follow Google’s documentation for your specific move.

9. Printable Drupal-to-WordPress migration checklist

Discovery

  • □ Source Drupal version and modules documented
  • □ Database, code, uploaded files and configuration backed up
  • □ Content types, fields, taxonomy, media, users, languages and forms inventoried
  • □ Search Console baseline and URL alias export saved
  • □ WordPress data model and permalink strategy agreed

Migration testing

  • □ WordPress staging secured and backup verified
  • □ Sample import tested for every major content type
  • □ Field mapping, relationships and media validated
  • □ Import counts reconciled with source records
  • □ One-to-one redirects tested for important aliases and node paths

Go-live and aftercare

  • □ Staging robots rules removed from production
  • □ HTTPS, canonical URLs, titles and sitemap verified
  • □ Forms, consent, analytics and integrations checked
  • □ 404s, images and downloads checked after cutover
  • □ GSC performance monitored against the original baseline

10. Troubleshooting frequent Drupal migration issues

Only article nodes imported, but custom content is missing

Check the importer’s supported scope. For FG Drupal to WordPress, the plugin lists custom post types and custom fields among its Premium capabilities. You may need add-ons or a custom mapping for Drupal field collections, entity references or paragraphs. Do not overwrite existing good data with repeated imports.

Imported pages look correct, but image URLs point to Drupal

Inspect each image URL and Drupal file scheme. Some files may need a separate media migration or download step. Update attachment references, validate protected files and confirm the destination’s actual HTTP responses.

Search Console reports old /node/ pages and missing aliases

Reconcile the old system paths and friendly aliases with the WordPress destination and any existing redirect rules. Fix exact mappings for high-value pages first; eliminate loops and irrelevant homepage redirects.

Authors or multilingual relationships disappeared

These may be unsupported features of the chosen importer rather than missing database records. Compare the content model, required plugin capabilities and original relationships before rerunning the move.

Frequently asked questions

Can Drupal 7 migrate directly to WordPress?

Yes, a direct content migration is possible using compatible importers or custom workflows. The source Drupal 7 site’s schema, modules, files and security risks still need review.

Can you move Drupal 10 or Drupal 11 to WordPress?

Yes, but evaluate modern Drupal entities, paragraphs, workflow and custom integrations carefully. A marketing website with standard content may be simpler to move than a complex Drupal application.

Will a Drupal-to-WordPress migration preserve Google rankings?

No one can guarantee that. Preserving content, mapping aliases, keeping URLs where sensible, testing permanent redirects and monitoring Search Console are the controllable parts of the process.

Is there a free Drupal-to-WordPress migration plugin?

FG Drupal to WordPress has a free version covering core content and media, while its listing identifies additional capabilities such as user, field and SEO URL migrations with Premium options. Always verify current plugin documentation and test on staging.

Do Drupal fields automatically become WordPress ACF fields?

Not automatically. Define field names, types, repeaters, references and template output on WordPress, then map imported data into those structures.

How long will migration take?

It depends on the number of content records, custom modules, relationships, media, languages, forms and SEO-critical URLs. A proper estimate requires a source inventory and a test import rather than a fixed promise.

NEED A STRUCTURED MIGRATION PLAN?

Move from Drupal to WordPress with a documented plan.

BitwiseCode can help review content types, field mapping, existing URLs, WordPress architecture and staging QA for your migration. Explore our Drupal-to-WordPress migration service or share your current site for an estimate.

Discuss your migration →

References and documentation

Reviewed November 2026. Drupal support schedules, importer compatibility and plugin features can change; validate the details for your actual source site and versions.