Illustrative comparison of two language versions of a website.
A multilingual Umbraco migration can look straightforward until the same content node turns out to have a different URL, copy and publishing state in each language. The migration needs to preserve the relationship between those versions so editors can maintain them and visitors can reach the right page.
Choose one branch with at least two languages and a known exception. A sample like that provides a clearer starting point for an estimate than the number of content nodes alone.
Build an inventory at the culture-variant level
Record the source version, site roots, domains and cultures. Export the available source values and compare them with routes and content seen on the public site. A culture may inherit some fields, use a localised path or remain unpublished. Track shared and localised values separately.
Give every planned destination a reproducible mapping from the source record and its culture. Collect the current URL, type, publication decision and translated fields for each variant. Verify what the site’s installed version makes available. Umbraco culture variants and multilingual setup.
Decide how WordPress will represent translations
Agree on the multilingual setup, whether languages live under directories or separate domains, and who can edit each translation. Use the chosen implementation to link the versions. A translation should have the right locale, parent, template and media references. Test menus, language switchers and form messages as well as page bodies.
Decide where a field is shared and where it needs an independent value. The same photo can be used across the site while its caption and alt text are localised. Ask editors to update the French heading on the pilot page and confirm that the English heading stays as approved.
Test a published pair and a missing translation
Consider a fictional manufacturer with English and French services. Its French service slugs are translated, an older French support page has been replaced and another French page is still in review. Each example tests a different part of the migration.
| Variant | Destination decision | Launch check |
|---|---|---|
| Published EN and FR service | Import both as linked translations with their approved localised URLs. | The language switcher opens the corresponding service from either version. |
| French support page with a successor | Map the old path to its relevant French replacement. | The old address resolves to the approved French page in one redirect. |
| French page still in review | Keep the destination translation unpublished. | Navigation and published alternates omit the draft until approval. |
Validate redirects, canonicals and language alternates together
Where URLs change, test old locale-specific paths individually. Map the actual replacements. If there is no corresponding page, agree how to handle the retired URL and what the language selector will offer. Keep the redirect inventory distinct from the translation inventory because several older URLs may point to one approved destination.
For a site using hreflang, verify that each published equivalent references itself and its counterparts and that the links are reciprocal. Check that destinations load and have the intended canonicals. Review the sitemap, navigation and in-content links for the right locale. Google’s guidance on localised page versions.
Have editors and reviewers run the same checks in staging
Give reviewers a published pair, an unlisted draft and a localised URL that changed. Ask them to edit a field, follow the language switcher and open an old bookmarked link. Rerun the sample import and confirm that the translated entries retain their relationships without duplicates. Agree which edits need exporting again before cutover.
If the site uses structured blocks, follow the Umbraco content block mapping guide for that part of the build. The redirect mapping brief helps scope old URLs and launch checks.
Send a pair of localised URLs and one exception
Share your Umbraco version, languages, approximate page count by culture and two live equivalents. Add an example of a missing translation, inherited field or changed URL. I can review the source and estimate a first migration slice with publishing, editing and URL checks.
