If you have searched for a Drupal to WordPress migration plugin, you have found one name: FG Drupal to WordPress. It is the only purpose-built plugin for this migration in the WordPress repository. It works well for what it was designed to do. It also has a clearly defined ceiling, and a significant number of Drupal sites sit above that ceiling. This review covers both honestly.
What the FG Drupal to WordPress Plugin Actually Is
FG Drupal to WordPress is developed by Frédéric Gilles and has been available on WordPress.org since 2012. It has been tested with Drupal versions 4 through 11 and works with the latest versions of WordPress. The plugin connects directly to the Drupal database, reads the content, and writes it to WordPress. It does not scrape rendered pages. It reads from the source database, which is the correct approach to content migration and the reason it performs better than generic import tools.
The connection is configured by entering the Drupal database credentials, which you can find in the sites/default/settings.php file on a Drupal 7 installation. The plugin includes a connection test tool. Once connected, it imports content in stages: first pages and posts, then media, then taxonomies. It is straightforward to run and does not require developer involvement for a standard Drupal installation.
Free Version: What You Get
The free version of FG Drupal to WordPress, available without charge from WordPress.org, imports the following from a Drupal site: articles, stories, basic pages, categories, tags, and images. It uploads all media from the Drupal posts to the WordPress uploads folder and updates the internal links in content to point to the new WordPress media URLs. It has been tested across a wide range of Drupal versions and handles standard content structures reliably.
For a personal blog, a simple brochure site, or a Drupal installation that uses only the default content types with no custom configuration, the free version handles the migration cleanly. Content arrives in WordPress, images are attached, and categories are mapped. For this use case, the plugin is genuinely good.
Premium Version: What the Upgrade Adds
The premium version of FG Drupal to WordPress extends the migration to cover several areas the free version does not handle: comments, user accounts including both registered users and administrators, custom post types, custom taxonomies, custom fields, custom user fields, user photographs, navigation menus, and blocks as inactive widgets.
For sites that need users migrated or have any custom content structure, the premium version is necessary. The comment and user migration in particular are features that most Drupal sites will need, since Drupal comment and user data sits in tables that the free version does not read.
Where the Plugin Runs Into Trouble
The plugin is designed for standard Drupal installations. When a Drupal site uses modules and content structures beyond the standard set, the plugin’s coverage becomes partial. Independent testing has documented specific failure modes.
According to testing documented by Freshy Sites (April 2026), the free version of the plugin successfully imported basic content but failed to handle custom nodes and custom taxonomies correctly. The plugin’s architecture is optimized for Drupal’s built-in content types; when a site has defined its own content types with custom field structures, the mapping between those fields and WordPress custom post type fields requires manual configuration that the plugin does not automate.
The Paragraphs module is a significant limitation. Paragraphs is one of the most widely used Drupal modules for building flexible page layouts, allowing editors to add different types of content blocks to a single page. The plugin does not handle Paragraphs natively. The premium add-on ecosystem does include a Paragraphs add-on, but it requires additional configuration and does not fully automate the mapping for complex Paragraph structures. Sites that have built their editorial workflow around Paragraphs will need developer involvement beyond what the plugin provides.
Entity references, which are used in Drupal to create relationships between content items (a news article referencing a related report, a product referencing a manufacturer profile), are handled by the premium version with an add-on but require explicit mapping configuration. The free version does not attempt entity reference migration at all.
The Drupal Forum module is not covered by the plugin. Forum topics and replies stored as Drupal content objects are not migrated to any WordPress forum plugin. If your Drupal site had an active forum community, that history will not transfer using FG Drupal to WordPress. This is a gap that affects a specific but significant subset of Drupal migrations, particularly for associations, educational institutions, and organizations that built community discussion on their Drupal platform.
What the Plugin Cannot Handle At All
- Drupal Forum module content. Forum topics, replies, and author attribution stored in Drupal’s forum content type are not migrated. This data does not transfer to wpForo or any other WordPress forum plugin through the FG plugin.
- Webform submission data. Contact form submissions stored in Drupal’s Webform module are not imported. The form field values accumulated over years of operation stay in the Drupal database.
- URL alias preservation. The plugin does not systematically read Drupal’s
url_aliastable and create corresponding WordPress slugs or redirect rules. Post slugs are generated from post titles, which may or may not match the original Drupal URL aliases. Custom URL structures built in Drupal may break silently. - SEO metadata from the Metatag module. Custom SEO titles and meta descriptions set per-page in Drupal’s Metatag module are not transferred to Yoast SEO or any WordPress SEO plugin.
- Organic Groups and Commerce data. Drupal’s Organic Groups module (used for multi-group community sites) and Drupal Commerce (for e-commerce) are outside the plugin’s scope entirely.
When the Plugin Is the Right Choice
Use FG Drupal to WordPress when: the site uses only standard Drupal content types (articles and basic pages); there are no custom content type fields beyond the defaults; the Paragraphs module is not in use; there is no forum or Webform data that needs to transfer; you are comfortable manually setting up URL redirects after the migration; and the content volume is manageable enough that manual review of every imported item is feasible.
For a personal site, a simple blog, or a small Drupal installation that was never heavily customized, the plugin delivers exactly what you need at no cost. It is genuinely well-built for this use case.
When You Need a Professional Migration Service
A professional migration service is the right choice when any of the following apply: the site uses custom Drupal content types with custom field structures; the Paragraphs module is in use; there is forum history that needs to transfer with author attribution intact; Webform submission records have business value and need to be preserved; the site has hundreds or thousands of URL aliases that need to be either preserved as slugs or turned into 301 redirects; SEO metadata set in Drupal’s Metatag module needs to transfer to WordPress; or the site’s complexity or content volume means silent data loss during migration is unacceptable.
The practical dividing line is usually this: if the site was running Drupal because of its content modeling capabilities (custom content types, Paragraphs, Views-driven archives, complex taxonomy structures), those are exactly the features that fall outside what any automated plugin can handle reliably.
How gConverter Handles Complex Drupal Migrations
gConverter migrates Drupal sites by reading the source database directly. Every content type is mapped explicitly: content nodes to WordPress posts or custom post types, custom field values from Drupal’s Field API tables to ACF Pro fields, taxonomy vocabularies and terms to WordPress categories and custom taxonomies, URL aliases to WordPress slugs and 301 redirects, SEO metadata to Yoast SEO, user accounts with role mapping, and Drupal Forum content to wpForo 360° AI with full topic, reply, and author attribution preserved.
Before any access to your database, we sign a Data Processing Agreement. Your credentials are stored in AES-256 encrypted vaults, transferred over TLS 1.3, and all client data is deleted within 30 days of delivery. We are US-registered with full EU GDPR compliance and a documented breach notification process.
Read the full data protection documentation →
What Clients Say
Went FAR above and beyond to help us work through this project. We are thrilled with the final result and they were professional, great to work with, and responsive every step of the way. Would highly recommend.
Anna P., Wilmington NC – Customer Lobby, January 2026
Extremely professional and efficient, we had very good contact, the work was done in due time.
Timoti F., Berlin DC – Customer Lobby, February 2024
The Bottom Line
FG Drupal to WordPress is the best tool for simple Drupal migrations and it is free. For standard content types on a lightly customized Drupal site, it delivers clean results without developer involvement. For complex Drupal sites with custom content types, Paragraphs layouts, forum history, Webform data, or meaningful URL alias structures, it is the starting point of a longer conversation, not the ending one.
Knowing which category your site falls into before you start the migration is worth more than any tool review. Check your content type list, count your URL aliases, look at whether Paragraphs is installed, and see if there is Webform submission data worth keeping. If any of those boxes are checked, plan for a service rather than a plugin.