Move a structured Drupal website into WordPress without flattening its content into hard-to-edit pages. Norml maps content types, fields, relationships, and taxonomies before building the destination. We review multilingual routes and editorial permissions alongside the public website so the team can keep publishing after the move.
The Drupal content model determines the migration work. We start with the entities and workflows your site uses, then define a WordPress model that preserves the required relationships.
Articles, profiles, resources, and other bundles receive an agreed destination structure. We map field types and repeated values, preserve source identifiers during import, and distinguish published content from drafts or revisions. A representative sample proves the model before the whole archive is transferred.
Entity references need to become connected records in WordPress. We resolve dependencies between content, people, media, and taxonomy terms, then check the resulting links on rendered pages. Missing or inaccessible referenced records are reported instead of silently replaced with plain text.
Each language variant needs content, metadata, and a destination URL. We map language relationships and prepare redirects for changed paths. Images, documents, captions, and embedded files are checked for accessible source assets and suitable ownership in the new media library.
We identify who may draft, edit, approve, and publish each content type, plus what visitors can view. Drupal moderation rules and permissions need an explicit WordPress implementation. The agreed workflow is tested with representative roles before editors receive production access.
Provide the Drupal version, module list, field definitions, hosting or approved API access, and a restorable backup. Include custom entities, private files, multilingual content, and the editing tasks that depend on contributed modules.
An entity export does not reproduce custom modules, search behavior, access rules, or all revision history. We agree which records and behavior need to survive. Restricted material remains protected while its destination access model is verified.
Review entities, bundles, field cardinality, taxonomies, and references. Define the import order and destination content types, including translations and media dependencies.
Import a representative set with linked records and translated variants. Compare field values, rendering, editor controls, and access behavior against the agreed source examples.
Run the full scoped migration, compare record counts and relationships, and apply final content changes. Verify redirects, forms, search, and publishing permissions before and after the domain switch.