WordPress to Umbraco Migration
For organisations standardised on .NET. Move off WordPress onto Umbraco — an editor-friendly CMS your IT function already knows how to host, govern and audit.
Why .NET organisations move to Umbraco
Rarely a content decision. Usually that WordPress sits outside every standard the rest of the estate is held to: a different runtime, a different patching process, a different hosting model, and a plugin supply chain nobody has signed off.
Umbraco runs on .NET — currently Umbraco 17 LTS on .NET 10 — so it inherits the hosting, identity, monitoring and patching your organisation already operates. More on the platform.
How the migration runs
- Content audit and document-type design, mapped to your governance model.
- Extraction from WordPress into Umbraco document types, with media and metadata.
- Language variants configured natively for English and Arabic, RTL included.
- URL preservation and redirects, verified before cutover.
- Frontend in Razor, or headless over the Delivery API with a Next.js frontend.
- Editor training, and handover into your existing .NET support process.
WordPress and Umbraco, side by side
| Criterion | WordPress (today) | Umbraco |
|---|---|---|
| Content model | Posts/pages + ACF bolt-ons | Document types |
| Editor experience | Familiar, plugin-dependent | Mature editor UI |
| Frontend freedom | Themes; headless possible | Razor or headless Delivery API |
| Public attack surface | PHP origin + plugin surface | .NET origin, curated packages |
| Who patches, how fast | You — core, plugins and themes | You, on the LTS cadence |
| Supply chain | ~60k plugins, uneven quality | NuGet, curated |
| EN/AR and RTL | WPML or Polylang add-on | Native language variants |
| Custom business logic | Hooks; fights the grain | A full .NET application |
| Hosting and ops | Cheap shared through to managed | .NET host + database |
| Licence and cost shape | GPL core; plugin licences | Open core; Cloud optional |
| Team skills | PHP/WordPress, widely available | C#/.NET |
Already on Umbraco?
This service is specifically about leaving WordPress. If you are already on Umbraco and want development, upgrades or support, that is our Umbraco development service.
When this is the wrong choice
If you have no .NET capability and no plan to acquire it, Umbraco's main advantage disappears. WordPress to Sanity is usually the better fit, and the comparison sets out why.
If your estate runs on .NET and your governance assumes Microsoft tooling, WordPress is the outlier your security team keeps flagging. Umbraco gives editors a mature interface on a stack your organisation can already support, with native multilingual content and an LTS cadence procurement can plan around.
What we do
Document-type design
A content model mapped to how your organisation actually governs content.
Content and media extraction
WordPress content moved into Umbraco with metadata intact.
Native EN/AR variants
Language variants configured in the platform, RTL handled at render.
URL preservation and redirects
Verified against traffic before the switch.
Razor or headless frontend
Server-rendered Razor, or the Delivery API behind a Next.js frontend.
Handover to your .NET process
Documented so your existing support function can own it.
How it runs
The same transparent shape every engagement follows — you always know where you are and what it costs.
Discover
A short, fixed-price sprint: audit, stakeholder interviews and the questions that decide the shape of the work.
Define
Scope, architecture and a fixed estimate — you know what's being built, why, and what it costs before we start.
Deliver
Tight design-build loops with weekly preview releases. You watch it become real on a URL, not in a deck.
Grow
Launch is the midpoint. Measurement, iteration and support keep the work earning after day one.
Fair questions
How long does a migration take?
Eight to sixteen weeks is typical. Umbraco projects usually carry more governance and sign-off than a marketing-site rebuild, and that is generally what sets the timeline.
Will we keep our URLs and rankings?
Yes. URL inventory and redirect mapping are early deliverables, verified against analytics before cutover.
Which Umbraco version will we be on?
New builds go onto the current LTS — Umbraco 17, running on .NET 10 — unless you need something only in the STS line. LTS gives you a supported runway procurement can plan against.
Can we run both during the cutover?
Yes. Sections move behind the same domain while WordPress continues to serve the rest, until the final path is switched.