Drupal to WordPress for Swiss Organisations: Preserve Translated Taxonomy and URLs
A migration brief for preserving the categories and language relationships that help visitors find content on a multilingual site.
In this article
Illustrative workspace. Screens show concepts, not a delivered client system.
A multilingual Drupal site can contain more structure than its page count suggests. Translated categories, language counterparts and archive addresses may be central to how readers find material. For a Swiss organisation planning a WordPress migration, map those relationships before importing content, so the new site preserves useful discovery paths rather than only the visible article text.
Inventory terms and relationships independently
List the content types and the classifications attached to them. Record stable source identifiers, language values and any hierarchy the business wants to retain. Similar translated labels do not necessarily mean two source terms should be merged.
WordPress’s custom post type guidance illustrates separating structured content from presentation. The destination structure should be chosen deliberately, including its classifications and multilingual tooling, instead of squeezing every record into one generic page type.
The mapping is a project decision based on the source site, not a promise that Drupal and WordPress concepts transfer one to one.
Review category archives as public destinations
A category page may have its own introduction, metadata, incoming links and visitor purpose. Treat it as a destination to assess, not merely an internal label. Decide which translated archives remain and which are intentionally consolidated.
Check navigation links, article breadcrumbs and contextual links that reach these archives. A new article can look correct while sending the visitor to an empty or wrong-language category. The migration sample needs to include the surrounding discovery journey.
Map language counterparts and exceptions
Identify which records are translations of the same content and which are independently authored. Preserve that distinction in the new system. If a counterpart is missing, define the language-switching behaviour and publication decision explicitly.
Use approved language reviewers to check the result. A developer can reconcile references and addresses but should not infer that two different-language articles have equivalent meaning from a similar title alone. Record unresolved mappings for review instead of silently assigning a default counterpart.
Build the redirect map from the agreed structure
List old article, archive and language-specific addresses with their intended destinations. Where a classification changes, choose a relevant replacement for each public archive. A broad redirect to the homepage can discard the visitor’s original purpose.
Review redirect chains and canonical destinations on a sample containing each language and important content type. Correct search signals support migration quality, but an unchanged ranking is not something a development proposal can guarantee. Keep existing analytics and search evidence available for the owner’s post-launch review.
Reconcile relationships, not only record counts
A useful acceptance sample includes a nested classification, a translated term, an article in several categories and a missing counterpart. Follow the public links and inspect the editor’s record. Confirm that filters and archives return the intended content.
- Source and destination identifiers are traceable.
- Language counterparts are deliberate.
- Archive introductions and metadata are reviewed.
- Old public addresses reach useful destinations.
- Editors can maintain the chosen structure.
Can we simplify the taxonomy? Yes, but agree the content and address consequences before the import. Simplification should be a documented editorial decision rather than accidental data loss.
For the wider implementation decisions, see the Drupal migration planning guide.
Discuss a scoped implementation
Send the current site, representative content types, category examples and required languages. We can scope a relationship-mapping sample and its redirects before the full WordPress migration.
I’m Jagjeet Singh, based in India and working remotely with businesses and agencies. Discuss your multilingual Drupal migration. Share the current site or workflow and the first outcome you want to review; I can assess the requirements and propose an implementation scope.
Written by
Jagjeet Singh
Full stack development, WordPress engineering and practical web products. I work with businesses, teams and agencies in India and worldwide.
Explore my work
