Your Umbraco estate, resolved.
Builds, upgrades and Cloud migrations on Umbraco. Our Umbraco practice is three years old; the company behind it has been delivering for over a decade. We would rather you knew both numbers than neither. Start by finding out whether the version you are on is still receiving security fixes. Most people are surprised.
Which Umbraco are you on?
Umbraco's release cadence is tied to .NET. Long-term-support majors get eighteen months of fixes plus twelve months of security-only patches; standard releases get six. Version drift can become material before it is visible. Pick your version to see the published support schedule.
Your current major version
—
What we would tell you
We run the assessment before you commit. You get a written report on your own instance — package compatibility, required code adaptations and a realistic duration. The assessment is included before commitment.
Get an assessment for Umbraco 13 →Dates from Umbraco's published long-term support and end-of-life schedule. Versions 7 and 8 are long past end-of-life and are not listed individually.
See the upgrade before we scope it.
Upgrade ranges often reflect limited estate-specific evidence. We take a copy of your instance, attempt the upgrade path, and hand you a written assessment of what needs changing — package compatibility, custom property editors that need rewriting for the new backoffice, and integrations that need attention.
We scope against that document, and payment follows milestones you define.
Estate-specific evidence lets us produce a narrower upgrade quote and stand behind it.
What we do on Umbraco
01
Version upgrades
From versions 7, 8 and unsupported standard releases onto the current LTS. Includes the backoffice rewrite work that Umbraco 14 onwards requires.
02
Umbraco Cloud migration
On or off Cloud, with a straight answer about which is right for you. Cloud is excellent for some estates and an unnecessary cost for others; we will tell you which you are.
03
New builds
Fixed-cost Umbraco builds scoped against a working prototype rather than a specification document. Multi-site and multi-language architectures included.
04
Platform migrations
WordPress, Drupal, Sitecore and bespoke CMS onto Umbraco — with URL structures and redirects preserved so the SEO position you have paid for survives the move.
05
Integrations
CRM, ERP, payment, analytics and identity. Built as maintainable code in your repository rather than as configuration only we understand.
06
Support & retainers
Monthly retainers covering fixes, enhancements and developer time, with the hours reported rather than assumed. Cancellable at any milestone boundary.
How an Umbraco engagement runs
00
Assessment included before commitment
We take a copy, attempt the work, and give you a written report on what needs changing and what it will take. The assessment is yours to keep and makes every number below more reliable.
01
Architecture & planning
Document types, composition strategy, environments and deployment, decided against the content model running in your estate.
02
Delivery in sprints
Two-week cycles with a working environment at the end of each. Editors get access early, while feedback is quick to incorporate.
03
Launch & hold
Cutover, redirect verification, performance baseline, and a ninety-day stability period against thresholds agreed in advance.
Questions we are actually asked
Can you migrate our existing CMS to Umbraco without losing search rankings?
Yes — from WordPress, Drupal, Sitecore or a bespoke system. URL structures are preserved where they can be and redirected where they cannot, and the redirect map is tested before cutover rather than after. We treat rankings as an asset you have already paid for.
We are on Umbraco 8. Is upgrading or rebuilding cheaper?
Sometimes rebuilding. Umbraco 8 to a current version is not an upgrade in the ordinary sense — the backoffice, the APIs and much of the package ecosystem have changed underneath. The assessment exists precisely to answer this question with evidence, and we have told clients to rebuild when that was the honest answer.
Do you handle multi-site and multi-language?
Yes. Language variants versus separate trees is an architectural decision with long consequences; we make it deliberately and document the reasoning.
Can you build an MVP and the CMS together?
Yes. Product and content platform are architected to share data, user flows and marketing content rather than being bolted together afterwards.
Are you an Umbraco partner agency?
We currently operate independently of Umbraco's partner programme. Our evidence is an assessment run against your own instance before commitment — your version, integrations and upgrade path, written down for you to inspect.
Next
Send us the URL. We will map the safest upgrade path.
Get the upgrade assessment →United Kingdom · European Union · India