/handbook/drupal-to-wordpress-migration-guide/content-migration/
What We Do
Digital Platform MigrationsKey SolutionsManaged ServicesStaffing SolutionsIndustriesProducts
Discovery
Strategic consultancy & project roadmap
Growth Services
On demand development & consultation
Site Maintenance
Annual maintenance. Done for you
QE Services
Testing across SDLC for assured quality
Hosting Migration
Move to a performant hosting with zero downtime
WooCommerce
Enterprise commerce delivered without lock-in
AI
Unlock real use cases and integrations
All Services
A suite of services for any need
Technology STACK
eCommerce
Scale your e-commerce with WooCommerce, integrations, and custom extensions for growth.
EasyEngine
Server management tool that makes using WordPress on Nginx easy.
Web Auditor
Performance Audit & Insights for your Website.
rtMedia
A complete media management plugin for WordPress.
Resources
About Us
CLEAR
Resources How Enterprises Migrate from Drupal to WordPress Content migration
Topics
On this page
- How Enterprises Migrate from Drupal to WordPress
- Business case for migration
- Migration process, timeline & team
- Planning the migration
- Frontend migration
- Content migration
- Backend migration
- Quality assurance
- Site launch
- How can rtCamp help
1. Understanding Drupal’s content architecture
2. Mapping Drupal’s Content to WordPress’s ecosystem
3. Exporting your Drupal content
4. Transforming the content for importing into WordPress
5. Importing content into WordPress
Step 6: Setting up redirects (The final step)
Wrapping it up…
Last updated on May 28, 2026
Drupal to WordPress Content Migration
The content migration phase is one of the most complex parts of moving a Drupal site to WordPress. This stage involves transferring your site’s content assets—blog posts, pages, media assets, metadata, and more—to WordPress.
Let’s see how you can approach this Drupal to WordPress content migration.
1. Understanding Drupal’s content architecture
Before migrating content, it is essential to understand how content is modeled in Drupal. Drupal’s flexible content architecture relies heavily on content types, fields, taxonomies, and relationships.
- Content Types: These are the primary structures used to organize content in Drupal. Each content type defines a set of fields (e.g., text, images, file uploads). For example, a “Blog Post” content type may include fields like “Title,” “Body,” “Author,” and “Image.”
- Taxonomies: Drupal taxonomies are used for categorizing content. This can be hierarchical (e.g., a “Product Category” taxonomy) or flat (e.g., tags). Taxonomies help structure content relationships, which are key to organizing and filtering content.
- Fields: Fields in Drupal define specific data types (e.g., text, number, image, file). These fields are highly customizable and can include custom fields like image galleries, file attachments, and related content references.
- Content relationships: Often, Drupal sites use Entity Reference fields to establish relationships between content types (e.g., linking a “Product” content type to “Review” content). These relationships need to be carefully mapped to WordPress during the migration.
- Views: The Views module allows Drupal users to define custom lists of content based on specific criteria. Migrating these custom views requires setting up corresponding filters and queries in WordPress.
- Media: In Drupal, media handling is typically managed using the File Entity module (or the Media module in newer versions) and the file system. In Drupal, media assets such as images, documents, and videos are stored in the file system, usually within the sites/default/files directory. Drupal uses file fields or media fields in content types to reference media assets.
- SEO meta content: In Drupal, SEO is typically managed using modules such as Metatag. This module allows users to define meta tags (e.g., title, description, keywords) for pages, content types, and taxonomies, helping with SEO optimization across the site.
2. Mapping Drupal’s Content to WordPress’s ecosystem
Once you have a comprehensive understanding of your Drupal site’s content structure, the next step is to map this structure to WordPress’s equivalent components. WordPress uses Post Types, Taxonomies, and Custom Fields to organize content.
- Content Types to Post Types: In WordPress, Posts and Pages are the default content types. However, for custom content types, WordPress allows you to create Custom Post Types. For instance, a Case Study content type in Drupal can be mapped to a Custom Post Type in WordPress. You’ll have to set these up in your WordPress before you can initiate the content migration.
- Taxonomies to Categories and Tags: Drupal’s taxonomies can map directly to Categories and Tags in WordPress. If a Drupal site uses custom taxonomies (e.g., Product Category), these can be replicated as Custom Taxonomies in WordPress.
- Fields to Custom Fields/ACF: Drupal’s flexible field system allows for custom data types (e.g., images, file fields, text fields). WordPress has built-in Custom Fields, but for more advanced field types, the Advanced Custom Fields (ACF) plugin is commonly used. A Price Field in Drupal, for example, could map to a Custom Field or an ACF field in WordPress.
- In WordPress, content relationships are typically mapped using Custom Post Types (CPTs) and Custom Taxonomies, combined with Advanced Custom Fields (ACF) or similar plugins for more complex relationships.
- In WordPress, Views in Drupal (which typically generate custom queries to display filtered, sorted, and paged content) would map to Custom Queries or WP_Query in WordPress. WP_Query is the primary tool in WordPress for creating custom queries to display specific content. You can use WP_Query to replicate the functionality of Drupal Views by filtering, sorting, and paginating content. It allows you to fetch specific posts, pages, or custom post types based on custom parameters (like category, tags, meta fields, etc.).
- Media handling: In WordPress, media handling is managed through the Media Library, which is part of the core system. Media assets like images, documents, and videos are uploaded and stored in the /wp-content/uploads/ directory, organized by year and month. WordPress uses the Attachment post type to manage media, where each media file is treated as an individual post. These files can be referenced directly in posts, pages, or custom post types using the Add Media button or through custom fields. Unlike Drupal’s file fields, WordPress allows users to easily insert media into content through the block editor (Gutenberg) or the classic editor.
- SEO metadata: In WordPress, SEO metadata is commonly handled by plugins such as Yoast SEO or Rank Math, which provide tools for preserving metadata like meta titles, descriptions, and focus keywords.
Here’s a quick table summarizing how the Drupal content/data features map to WordPress:
Drupal ComponentEquivalent in WordPressNotesContent TypesPost Types (Posts, Pages, Custom Post Types – CPTs)Drupal’s Content Types map to WordPress Post Types. Custom content types (e.g., Case Studies) must be registered as Custom Post Types (CPTs) in WordPress.TaxonomiesCategories, Tags, Custom TaxonomiesDrupal’s Taxonomies can map to Categories and Tags. Custom Taxonomies (e.g., Product Category) must be registered separately in WordPress.FieldsCustom Fields / ACF (Advanced Custom Fields)Drupal’s flexible field system maps to WordPress Custom Fields. For complex field types, ACF or similar plugins are required.NodesPosts / Pages / Custom Post TypesIn Drupal, all content is a Node, while in WordPress, Nodes map to Posts, Pages, or CPTs depending on their purpose.BlocksWidgets / Gutenberg Blocks / Full Site Editing (FSE) BlocksDrupal Blocks are comparable to Widgets in classic themes and Gutenberg Blocks (or Full Site Editing Blocks) in modern WordPress.ViewsWP_Query / Custom Queries / Page BuildersDrupal Views create custom content lists. In WordPress, WP_Query and Custom Queries achieve similar results. Some use page builders (like Elementor) to recreate Views’ flexibility.MenusNavigation MenusBoth platforms support hierarchical Navigation Menus, but WordPress provides a more user-friendly UI for menu management.User Roles & PermissionsWordPress User Roles & CapabilitiesDrupal’s granular role-based access maps to WordPress User Roles & Capabilities. Additional roles and permissions require custom code or plugins.Media HandlingMedia Library (Attachments, Media post type)WordPress manages media via the Media Library, storing files in /wp-content/uploads/. In Drupal, File Fields need to be mapped to Attachment post types or referenced through Custom Fields.
3. Exporting your Drupal content
Drupal to WordPress content migration starts with exporting content from Drupal, which can be done manually or in an automated way, depending on the site’s complexity.
- Database export: For small to medium-sized sites, exporting content via an SQL dump can be effective. Export tables such as node, taxonomy_term_data, and field_data_*, and convert the data into a suitable format like CSV, XML, or JSON for later processing.
- Drupal’s built-in export tools: The Migrate module can export content in XML, CSV, or JSON formats. These modules allow you to export content types and fields while retaining their relationships.
- Custom exports: For more complex scenarios, you may need to write custom scripts to export data in the appropriate format for migration.
You may also use third-party export tools like Drupal Backup and Migrate that can automate the process of exporting content, creating backups, and ensuring that large volumes of content are prepared for migration.
4. Transforming the content for importing into WordPress
Once content is exported from Drupal, it must be transformed into a format suitable for WordPress import. This stage involves:
- Data format conversion: Depending on the export format (CSV, XML, or JSON), you may need to convert the data into a format that WordPress can accept. For example, if you have a CSV export, you might need to reformat the data to match the WP All Import plugin’s requirements (if you’re using this particular plugin for the import).
- Field mapping: Custom fields in Drupal need to be mapped to Custom Fields or ACF fields in WordPress. For example, a Date field in Drupal should be mapped to a corresponding field in WordPress that uses the correct date format.
- Handling relationships: For content relationships (e.g., related posts or product reviews), custom taxonomies and entity references in Drupal need to be transferred as relationships or custom taxonomy terms in WordPress.
- URL and slug conversion: If the URL structure changes between Drupal and WordPress, slugs must be converted to match the new structure while preserving SEO.
5. Importing content into WordPress
Once content has been exported and transformed, it’s time to import it into WordPress. There are multiple ways to do this:
1. Using the WordPress importer tool: WordPress includes a built-in WordPress Importer tool, which is capable of importing content from XML files. This option is suitable for simpler migrations, especially when the content structure is straightforward, such as basic posts and pages. The WordPress Importer is limited when dealing with complex custom post types, fields, and large datasets.
How to use:
- Export your content from Drupal into an XML file.
- Go to your WordPress admin panel, navigate to Tools > Import, and select the WordPress Importer.
- Upload your XML file and follow the instructions to map content to appropriate WordPress post types and taxonomies.
This method is best for small-scale migrations or straightforward content structures.
2. Using custom migration scripts: For highly customized or complex migrations, creating custom PHP scripts or using WP CLI (WordPress Command Line Interface) might be necessary. These scripts allow you to automate the migration of content from Drupal to WordPress by directly interacting with WordPress’s database and APIs.
How to use:
- Write PHP scripts to extract and process data from your exported file or directly from the Drupal database.
- Use the wp_insert_post() function to import posts, or utilize WP CLI commands for bulk data insertion.
- Handle relationships between content, such as linking custom taxonomies and meta fields, by including custom logic in your scripts.
Custom scripts are the most flexible method but also the most technically challenging. They are best suited for developers with experience in both Drupal and WordPress systems.
3. Using a plugin like FG Drupal to WordPress: The FG Drupal to WordPress plugin is a specialized migration plugin that helps streamline the process of moving content from a Drupal site to WordPress site.
Key features of FG Drupal to WordPress plugin:
- Content import: The plugin supports importing content types from Drupal, such as Articles, Blog Posts, or any custom content types used in Drupal. However, you’ll still need to map custom Drupal fields to WordPress custom fields and post types, which may require additional customization. Also, while the plugin has basic support for ACF fields, custom configuration may be needed to ensure proper mapping to WordPress’s ACF plugin if your Drupal site uses advanced custom fields.
- Media import: It’s capable of importing images, videos, and documents from Drupal’s media library to WordPress. The plugin ensures media is placed in the WordPress media library correctly, and it handles internal image and media links to ensure that they’re redirected properly in the new system.
- Taxonomy mapping: The plugin allows for taxonomies in Drupal to be mapped to WordPress categories and tags. This ensures that content organization, like blog post categories and tags, is preserved. For custom taxonomies, you can map them to WordPress custom taxonomies to ensure continuity of the categorization structure.
- Preserving SEO: SEO metadata from Drupal (like meta titles, meta descriptions, URL structure) can be migrated using the plugin, but you may need additional configuration or third-party plugins (like Yoast SEO or Rank Math) to fine-tune SEO elements once in WordPress.
- Post-import redirection: The plugin can help set up redirections for URLs from the old Drupal site to the new WordPress site. This is critical to ensure that SEO equity is maintained and users are redirected properly, avoiding broken links.
Step 6: Setting up redirects (The final step)
Once your content is successfully migrated from Drupal to WordPress, setting up redirects is the final crucial step. Redirects ensure that both users and search engines are sent to the correct pages on your new WordPress site. Without proper redirects, visitors will encounter 404 errors, and search engines will struggle to index your new site correctly. Here are a few ways to set up redirects.
- Via .htaccess: One of the most common methods for setting up redirects is through the .htaccess file on your server (if you’re using Apache). This method allows for 301 permanent redirects, which pass along SEO authority from the old URL to the new one. For this, you need to add each URL redirection rule in the .htaccess file, ensuring the old URL is correctly mapped to its new WordPress equivalent.
- Redirection plugin (WordPress): If you’re looking for a user-friendly, less code-intensive method, the Redirection plugin is an excellent choice. This plugin allows you to manage redirects from the WordPress admin dashboard without needing to manually edit the .htaccess file. It also keeps track of 404 errors, helping you ensure all pages are correctly redirected and none are missed.
- SEO plugins: If you’re using SEO plugins like Yoast SEO or Rank Math, these often come with built-in tools for setting up redirects. For example, Yoast SEO Premium allows you to easily create and manage redirects directly within the plugin interface. After setting up your redirects, these plugins can also help monitor how well the redirects are working and whether any pages need further adjustments.
- Server-side redirects (Nginx servers): If your site is hosted on a server running Nginx, you’ll need to configure redirects via the server configuration files. The process is similar to .htaccess redirects but requires editing the Nginx config files.
- Using a migration plugin (FG Drupal to WordPress): Some migration plugins, like FG Drupal to WordPress, offer an integrated redirect feature. This plugin can automatically create redirects based on your old Drupal URLs and their corresponding new WordPress URLs, simplifying the migration process.
Wrapping it up…
This wraps up the drupal to wordpress data migration phase, the next step will be testing and validation—which we’ll dive deeper into later. This will ensure that all migrated content is properly integrated, functional, and performing optimally in its new WordPress environment.
Credits
Disha Sharma
Author
Disha Sharma
Author
Disha Sharma is a Content Writer at rtCamp with over a decade of experience at the intersection of technology, digital marketing, and enterprise content strategy. Her WordPress roots run deep, her …
Aviral Mittal
Editor
Aviral Mittal
Editor
Aviral Mittal is the Chief Marketing Officer at rtCamp, where he established and leads the marketing function, building and growing a team of 20+ specialists across content, SEO, design, and growth…
Contributions and Updates: Usama 
Good Work. Good People.
Industry partnerships
Compliance certifications
United States India
© rtCamp Inc. since 2009. All rights reserved.
Terms of Service · Privacy Policy · Trust Center
Company
Solutions
Subscribe to our newsletter and get a few email updates every month.
United States India
© rtCamp Inc. since 2009. All rights reserved.
Terms of Service · Privacy Policy · Trust Center
Cookie Consent
We value your privacy
We use cookies to give you the best possible experience. By clicking “Accept,” you consent to our use of cookies to improve site functionality, analyze usage, and personalize content and communications. Your privacy matters to us, and we are committed to handling your data responsibly and transparently. Please check our Privacy Policy for more details.
Manage PreferencesDon’t AllowAllow All
Why do we use cookies?
×
By clicking "Accept" or "Decline All" at the bottom, you consent to the use of cookies and other tools as described in our Cookie Policy in accordance with your settings and accept our Terms of Service.
Toggle EssentialEssential
Essential cookies enable basic functions and are necessary for the proper function of the website.
Name
Description
Duration
Geolocation Config
This cookie is used to store the consent settings based on the visitor's location.
30 days
Cookie Preferences
This cookie is used to store the user's cookie consent preferences.
30 days
Toggle CloudFlareCloudFlare
CloudFlare provides web performance and security solutions, enhancing site speed and protecting against threats.
Service URL: developers.cloudflare.com (opens in a new window)
Name
Description
Duration
cf_clearance
Whether a CAPTCHA or Javascript challenge has been solved.
session
Toggle CommentsComments
These cookies are needed for adding comments on this website.
Name
Description
Duration
comment_author
Used to track the user across multiple sessions.
Session
comment_author_email
Used to track the user across multiple sessions.
Session
comment_author_url
Used to track the user across multiple sessions.
Session
Toggle GodamGodam
GoDAM" is primarily a specialized WordPress plugin and media management service designed to enhance video hosting, marketing, and asset management directly within the WordPress dashboard.
Service URL: godam.io (opens in a new window)
Name
Description
Duration
user_image
Temporarily stores the path to the user's avatar or profile picture for quick rendering in the website header.
session
user_id
Stores the numerical ID of the logged-in user to maintain session continuity and basic site operations.
session
full_name
Stores the logged-in user's display name to personalize the site interface without needing database queries.
session
system_user
First-party cookie used to store basic application state identifying the current system user role.
session
sid
A generic session ID cookie used to maintain user state and functionality as the visitor navigates through the site.
session
Toggle Google reCAPTCHAGoogle reCAPTCHA
Google reCAPTCHA helps protect websites from spam and abuse by verifying user interactions through challenges.
Name
Description
Duration
_GRECAPTCHA
Google reCAPTCHA sets a necessary cookie (_GRECAPTCHA) when executed for the purpose of providing its risk analysis.
179 days
Toggle Google Tag ManagerGoogle Tag Manager
Google Tag Manager simplifies the management of marketing tags on your website without code changes.
Name
Description
Duration
cookiePreferences
Registers cookie preferences of a user
2 years
td
Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator.
session
Toggle StatisticsStatistics
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.
Toggle Factors AIFactors AI
Factors.ai is a B2B account intelligence and marketing analytics platform that helps Go-To-Market (GTM) teams identify anonymous website visitors, track buyer journeys, and measure the ROI of marketing campaigns.
Service URL: www.factors.ai (opens in a new window)
Name
Description
Duration
_fuid
It is sent to capture session details and track user behavior across your website to provide behavioral data and intent signals.
1 Year
Toggle Google AnalyticsGoogle Analytics
Google Analytics is a powerful tool that tracks and analyzes website traffic for informed marketing decisions.
Service URL: policies.google.com (opens in a new window)
Name
Description
Duration
FPGSID
Stores a session or user identifier to track how visitors interact with a website. This helps Google Analytics measure website performance, user engagement, and usage patterns.
Session
FPLC
Used by Google Analytics to link visitor interactions and sessions across multiple related domains.
20 hours
FPID
A server-side Google Analytics cookie used as an alternative user identifier when third-party cookies are restricted.
2 years
_ga
ID used to identify users
2 years
_ga_
ID used to identify users
2 years
Toggle Jetpack StatsJetpack Stats
Jetpack's built-in visitor analytics. It records page views, referring sites, search terms, and outbound link clicks, and also carries the shared visitor-tracking library used by Jetpack Instant Search and WooCommerce Analytics.
Service URL: automattic.com (opens in a new window)
Name
Description
Duration
tk_aip
Stores a list of anonymous visitor IDs so they can be merged into one identity once a visitor is recognized.
Up to 5 years
tk_tc
Used once per page load to work out which cookie domain the Tracks library should use, then removed as soon as it's read back.
Session (deleted immediately after use)
tk_qs
Queues analytics events for Jetpack's Tracks library so none are lost if the page closes before they can be sent.
30 minutes
tk_ai
Stores a randomly-generated anonymous visitor ID so Jetpack's Tracks analytics library can link tracking events to the same visitor.
Session in wp-admin; up to 5 years on the frontend
Toggle Microsoft ClarityMicrosoft Clarity
Clarity is a web analytics service that tracks and reports website traffic.
Service URL: clarity.microsoft.com (opens in a new window)
Name
Description
Duration
CLID
Identifies the first-time Clarity saw this user on any site using Clarity.
12 months
ANONCHK
Indicates whether MUID is transferred to ANID, a cookie used for advertising. Clarity doesn't use ANID and so this is always set to 0.
Session
_clck
Persists the Clarity User ID and preferences, unique to that site is attributed to the same user ID.
12 months
_clsk
Connects multiple page views by a user into a single Clarity session recording.
12 months
Toggle Parse.lyParse.ly
Parse.ly is a content analytics platform that helps publishers optimize audience engagement and content performance.
Name
Description
Duration
cookies.js_dtest
This cookie determines whether the browser accepts cookies.
session
_parsely_session
JSON document storing information identifying a browsing session according to Parsely’s proprietary definition
30 minutes
_parsely_visitor
JSON document uniquely identifying a browser and counting its sessions
13 months
Toggle SalespanelSalespanel
Salespanel is a B2B marketing and sales software that identifies, tracks, and qualifies website visitors and leads in real-time using first-party data. It helps businesses monitor customer journeys, score leads based on behavior, and syncs this data with CRMs (like Pipedrive or HubSpot) to improve conversion rates.
Service URL: salespanel.io (opens in a new window)
Name
Description
Duration
track_uid
Identify and tracking a lead
12 moths
Toggle MarketingMarketing
Marketing cookies are used to follow visitors to websites. The intention is to show ads that are relevant and engaging to the individual user.
Toggle Bing / MicrosoftBing / Microsoft
Bing, powered by Microsoft, is a search engine providing web, image, video, and map search capabilities.
Name
Description
Duration
MR
Used to collect information for analytics purposes.
6 months
ANONCHK
Used to store session ID for a users session to ensure that clicks from adverts on the Bing search engine are verified for reporting purposes and for personalisation
10 minutes
SM
Used by Microsoft in synchronizing the MUID across multiple Microsoft domains to track users for advertising.
session
MUID
Identifies unique web browsers visiting Microsoft sites. These cookies are used for advertising, site analytics, and other operational purposes.
1 year
Toggle DoubleClick/Google MarketingDoubleClick/Google Marketing
A comprehensive digital advertising platform for managing campaigns, optimizing performance, and analyzing audience data.
Name
Description
Duration
IDE
This cookie is used for targeting, analyzing and optimisation of ad campaigns in DoubleClick/Google Marketing Suite
2 years
ar_debug
Store and track conversions
Persistent
Toggle LinkedInLinkedIn
LinkedIn is a professional networking platform for job seekers, employers, and industry connections.
Name
Description
Duration
bscookie
Used by LinkedIn to track the use of embedded services.
1 year
AnalyticsSyncHistory
Used to store information about the time a sync with the lms_analytics cookie took place for users in the Designated Countries
30 days
bcookie
Used by LinkedIn to track the use of embedded services.
1 year
li_sugr
Used to make a probabilistic match of a user's identity outside the Designated Countries
90 days
lidc
Used by the social networking service, LinkedIn, for tracking the use of embedded services.
1 day
UserMatchHistory
Used by LinkedIn Ads to synchronize and match user IDs across different ad networks and data providers.
30 days
Toggle LinkedIn InsightLinkedIn Insight
LinkedIn Insight is a web analytics service that tracks and reports website traffic.
Service URL: www.linkedin.com (opens in a new window)
Name
Description
Duration
li_sugr
Used to make a probabilistic match of a user's identity.
90 days
lidc
Used for routing and session management.
24 hours
Toggle LiveIntentLiveIntent
LiveIntent provides a platform for email advertising and identity-driven marketing solutions.
Name
Description
Duration
_lc2_fpi_js
Companion cookie to _lc2_fpi used by JavaScript to facilitate cross-domain ad tracking and user identification.
1 year
_lc2_fpi
First-party tracking cookie usually associated with LiveRamp to identify users across devices for targeted advertising.
1 Year
_li_ss
Sets a unique ID for the visitor, that allows third party advertisers to target the visitor with relevant advertisement. This pairing service is provided by third party advertisement hubs, which facilitates real-time bidding for advertisers.
1 month
lidid
Collects data on visitors' behaviour and interaction - This is used to make advertisement on the website more relevant. The cookie also allows the website to detect any referrals from other websites.
2 years
Toggle Cookie PolicyCookie Policy
You can find more information in our Privacy Policy.
Allow AllDecline All
Accept