In a Drupal to WordPress move, structured content breaks first. Long addresses and complex page templates fail next.
A content type is a template that sets the fields for one kind of page. Drupal allows dozens of fields, reference chains, and nested layouts in one type. WordPress has no direct match, so those structures need remapping.
Table of Contents
- Why content types do not fit WordPress
- Why old links stop working
- Why images and internal links break
- Which features need rebuilding?
- What happens to users and permissions?
Why content types do not fit WordPress
A Drupal article can carry dozens of custom fields. It can link to other items through entity references, which are pointers from one item to another. It can nest sections inside Paragraphs, which are reusable section blocks, or field collections. According to the Multidots enterprise migration guide, those chains have no direct WordPress counterpart and must be remapped to posts, custom post types, and post meta in the enterprise migration guide.
Post meta means extra field values stored with a post. A product guide with specs, downloads, and related cases becomes several pieces. The free FG Drupal to WordPress importer handles standard articles, pages, categories, tags, images, and users. WPBeginner notes that custom types, field collections, and Paragraphs need extra work or manual rebuilding after import.
Why old links stop working
Drupal allows multiple long aliases per node, which is one saved content item. An alias can reach 255 characters and include slashes for depth. WordPress stores one shorter slug per post, limited to 200 characters with no slashes. According to MigrateContent, deep or long aliases cannot be copied over and need 301 redirects that send visitors and search engines to the new address in the address-preservation guide.
Without pairing every old alias and node path to its new URL, changed addresses become dead links in search indexes. Those dead links return 404 errors and can depress rankings for months. Taxonomy term pages also carry risk. Taxonomy means grouped labels such as topics or sections, stored at paths like taxonomy/term/[tid]. If those pages are not mapped to category, tag, or custom-taxonomy archives, their traffic and internal links are lost.
Why images and internal links break
Drupal commonly stores uploads under sites/default/files. Body text often points to those paths for images, documents, and internal links. Token markup can also insert file or image references at display time. Codeable reports that those paths stop working unless file locations and image paths are remapped and tested in the migration breakdown.
Orphaned media causes special trouble because no page claims it. A migrated page may look complete while its diagrams, PDFs, or embedded videos return errors. Test downloads, galleries, and cross-links after moving files. Check both logged-in and logged-out views, since missing files can hide behind cached pages.
Which features need rebuilding?
Listings and forms do not transfer directly. Advanced Views listings, which are custom query-based content lists, need new queries or blocks. Webforms need new form tools, especially forms tied to workflows or CiviCRM, which manages contacts and memberships.
Circle Interactive and Multidots state there is no one-to-one match for that logic. Inventory every View, form, and custom module before migration. Keep only what readers still use.
- Rebuild filtered directories, event calendars, and search pages as new queries.
- Rebuild multi-step, conditional, or payment-linked forms from scratch.
- Replace custom modules, hooks, and event subscribers with plugins or custom code.
What happens to users and permissions?
Core users usually transfer. Names, emails, and basic accounts move with the importer. Granular roles do not move with them. Drupal roles can control who drafts, reviews, edits specific fields, or publishes at set times.
WordPress roles are broader and cannot accept that map automatically. Editorial workflows need audit and rebuilding with roles or plugins. Metatag-stored metadata also needs separate handling. RtCamp and Circle Interactive note that titles, descriptions, and social values stored in Drupal fields do not transfer on their own. Export that metadata early so each high-traffic page keeps its title and description.
