WebzstoreConfiguration export saves structure and settings, not content, so it cannot carry your articles. Drupal's Migrate API is documented as a framework for bringing data into Drupal from sources such as spreadsheet files and databases. It is not an export tool, so it does not solve this move by itself.
Drupal to WordPress Migration
Drupal to WordPress Migration
We move Drupal websites to WordPress by separating what Drupal calls configuration, content and code, then rebuilding each in the way WordPress handles it. Content types, taxonomy terms and the links between them can be mapped. Views, permissions and custom modules are rebuild tasks. Webzstore assesses the site first, then plans and builds the move.
01Choose
Choose what you want to change
Select one part, several parts or the whole project.
Where this startsOur Drupal site is expensive to change and few people understand it. We want WordPress but need to know which parts carry over and which are rebuilt.
In plain terms
- Taxonomy term
- A label used to group Drupal content, such as a category or tag.
- Views
- Drupal's saved lists and filters that build listing pages.
- Module
- A piece of Drupal code that adds a feature to the site.
02Sort
Sort every Drupal part into configuration, content or code
Drupal.org treats these as three different things, and each needs a different route. A node is a single piece of content, such as an article or an event.
Content types and their fields
Type
Configuration
In WordPress
Rebuilt as custom post types and fields
Nodes and taxonomy terms
Type
Content
In WordPress
Exported, then imported with their links
Views (saved lists and filters that build listing pages)
Type
Configuration
In WordPress
Rebuilt as listing templates or queries
Roles and permissions
Type
Settings
In WordPress
Rebuilt as WordPress roles
Custom modules and themes
Type
Code
In WordPress
Reviewed as rebuild tasks
03Export
Get the content out before touching the design
Drupal.org documents a contributed module (an add-on from the Drupal community, outside core) that exports nodes, taxonomy terms and block content with their files. No single core tool that exports every kind of content is confirmed, so we choose the route after the audit. We then write the import around the real relationships, such as an event linked to a venue term.
04Rebuild
Decide what happens to each rebuild task
These tasks depend on decisions, not only on content. The list shows where we ask for yours first.
- Entity relationships: which links between items must survive, and where each lives in WordPress
- Views-style listings: which filtered or sorted pages are used often enough to rebuild
- Permissions: which roles can edit, review or see restricted pages
- Custom modules: which still do something useful and which can go
- Module data, such as form or shop records: how each is handled, since this varies by module
Listings and templates are built through WordPress Website Design. Where a custom module holds real logic, a Headless CMS Development route may be worth comparing.
05Test
Test relationships, listings and roles
A successful import is not a finished site. We open one item for each content type and follow its links to other items. We check a listing against the Drupal View it replaces, using the same filters and sort order, and confirm that a page restricted to one role stays restricted.
A team member then drafts, reviews and publishes a new item under the right role.
06Launch
Plan addresses and the launch window
Drupal can generate addresses from content type, aliases or both, so we gather the real list. A redirect map (a prepared list sending each old address to its new one) is tested before the switch. We keep Drupal running until your team signs off.
After launch, we monitor search performance and clean up broken links. We cannot promise rankings stay the same.
Questions about moving Drupal to WordPress
Does Drupal's configuration export include my content?
No. Drupal.org says configuration management exports structure and settings, such as content types and Views, not the nodes and terms themselves.
Can the Migrate API export my Drupal site?
No. It is documented as an import framework. Exporting content takes another route, which we choose during the audit.
Will my Views be carried across?
No. Views are configuration, so a content export does not include them. We rebuild each one that you still need as a listing in WordPress.
Do Webform or Commerce records transfer?
It depends on the module. How data from contributed modules migrates is not confirmed in general, so each one is assessed separately.
Make the move for a clear reason
Send us your Drupal address, your content types and a list of the modules you rely on. We will assess the content, the listings and the permissions together, using Website Migration Services as the wider process.
Explore the next step
- Website Migration ServicesExplore website migration services with Webzstore. Plan your content, features and launch, then discuss the project on a free 30-minute call.
- WordPress Website DesignBuild or improve a WordPress website with useful page layouts, an agreed editing setup and clear ongoing care responsibilities. Book a free 30-minute call.
- Headless CMS DevelopmentExplore headless cms development with Webzstore. Plan your existing content, features and launch, then discuss the project on a free 30-minute call.