You migrate a Drupal site safely by auditing content, backing up files and database, importing into staged WordPress, then fixing URLs and features. In this move, Drupal articles, pages, media, users and settings become WordPress posts, pages, files and roles after testing. A Drupal-to-WordPress migration means shifting content management from Drupal to WordPress without losing content, users or search traffic. It takes planning because content models, logins, layouts and URLs differ between systems.
Table of Contents
- What should you map before you move?
- How do you avoid downtime and data loss?
- What will the importer carry over?
- How do you keep traffic and features working?
What should you map before you move?
List every Drupal content type, taxonomy, image, media file, user and permission before you export anything. Then assign each item to WordPress posts, pages, custom post types and roles, as described in the Codeable migration guide.
This map prevents missing content later. For example, a Drupal news type may fit WordPress posts, while staff bios may need a custom post type and role limits.
How do you avoid downtime and data loss?
Back up the complete Drupal files and database before starting, so you can roll back after an error. Drupal.org documentation points to the Backup and Migrate module, mysqldump or pg_dump, and hosting backups in the official backup guide.
Install WordPress separately in a staging environment and keep Drupal live until testing passes. This setup lets you check content and functions without downtime, following the ToolsForge migration checklist.
- Back up Drupal files and database for rollback.
- Build WordPress in staging while Drupal stays live.
- Test content, links, forms and logins before switching.
What will the importer carry over?
The free FG Drupal to WordPress importer moves Drupal articles, pages, categories, tags and images into WordPress. According to the WordPress.org plugin directory, it supports MySQL, PostgreSQL and SQLite and is tested through Drupal 4 to 11 in the plugin listing.
Comments, users and administrators, custom fields and taxonomies, menus, Drupal password login, SEO URL redirects and WP-CLI import need the paid FG Drupal Premium version plus add-ons. Choose the paid path when membership, comments or custom data matter.
How do you keep traffic and features working?
Match WordPress permalinks to old Drupal URLs and add 301 redirects for changed addresses. Pay special care to legacy /node/<id> URLs, then submit an updated sitemap, as explained by WPBeginner in the Drupal-to-WordPress tutorial.
Automated import does not recreate every Drupal feature, layout or user account. Rebuild the theme, replace Drupal modules with WordPress plugins, and test forms, logins and search before launch.




