To migrate a Drupal site to WordPress safely, back up all files and the database, then move content into a fresh WordPress install on staging. Drupal, a content management system for building and managing websites, stays intact while you test imports, redirects, and forms before going live. A safe move follows the same order each time: prepare, import, extend, protect traffic, and fix gaps. Each step has a clear checkpoint, so a failure does not touch the live site.
Table of Contents
- What should you prepare before you move?
- How does the basic content transfer work?
- When do you need the premium upgrade?
- How do you keep traffic after the switch?
- How do you close the remaining gaps?
What should you prepare before you move?
Create a complete restore point first. According to Invedus, back up files plus the database with Backup and Migrate or phpMyAdmin before migration, as described in the Invedus migration guide.
Set up a separate staging home for WordPress. According to WPBeginner, install a fresh copy on staging hosting with a matching theme and required plugins, and avoid importing into live production until testing passes, as explained in the WPBeginner migration tutorial.
- Copy Drupal files and export the database
- Confirm the backup restores in a test location
- Install fresh WordPress on staging hosting
- Add the theme and plugins you will use at launch
How does the basic content transfer work?
Use a dedicated importer rather than copying pages by hand. According to WordPress.org, the free FG Drupal to WordPress plugin moves Drupal 4-11 articles, basic pages, categories, tags, images, media links, and internal links into current WordPress, as listed in the FG Drupal to WordPress listing. The same source notes support for MySQL, PostgreSQL, and SQLite sources.
That range matters because older Drupal installs may not use MySQL. Connect the plugin to the Drupal database from WordPress staging. Run the import, then check article counts, page counts, images, tags, and internal links before changing anything else.
When do you need the premium upgrade?
The free import covers basic content, not full site behavior. Sites needing users, comments, custom post types, custom fields, menus, password authentication, media entities, or URL redirects need FG Drupal to WordPress Premium, according to WordPress.org and Frédéric Gilles.
Add-ons cover special structures. Examples include Paragraphs, Webform, and Meta tags support for sites that relied on those Drupal features. Decide early by listing logins, member areas, custom content structures, and forms. If any item appears on that list, plan for Premium and the matching add-on before import.
How do you keep traffic after the switch?
Map every old Drupal URL to its WordPress equivalent. According to Hosted.com, configure matching permalinks, create permanent 301 redirects with Redirection or AIOSEO, then submit a new sitemap in Google Search Console, as outlined in the Hosted.com migration guide. Do this mapping before launch, not after traffic drops.
Keep a spreadsheet with old addresses, new addresses, and redirect status. Test the redirects as a visitor would. Click search results, bookmarks, menu links, and image links, then confirm each lands on the right WordPress page.
How do you close the remaining gaps?
Automated import leaves details behind. According to Codeable, remap custom fields to ACF, import Metatag-module metadata into a WordPress search plugin, fix missed media paths, and test forms, logins, and checkout. Give extra attention to file paths and embedded media.
A page can import correctly while its images still point to Drupal folders. Urgency is higher for Drupal 7 sites because Drupal 7 reached end of life and no longer receives security updates, according to Pantheon. Remaining sites face unpatched security risk until upgraded or migrated, so finish staging tests and schedule launch without long delay.
