The upgrade that is really a rebuild

If your website runs on Umbraco 7, you have probably been told it needs upgrading, and you have probably assumed that means a routine update. It does not. Moving from Umbraco 7 to Umbraco 8 is not an upgrade in the normal sense. Umbraco’s own documentation is explicit: you cannot upgrade a version 7 site to version 8, because the underlying codebase was fundamentally rewritten. Only your content can be carried across. The site itself has to be rebuilt.

That single fact changes the decision entirely, and it explains why so many Umbraco 7 sites are still live years after they should have moved.

Why it is a rebuild, not an update

Most software updates preserve your investment. You install the new version, your existing setup keeps working, and you gain some improvements. Umbraco 8 did not work that way. The architecture changed underneath, which means the custom code your site was built on — the templates, the controllers, the bespoke functionality your developer wrote — does not simply carry over. It has to be rewritten against the new platform. Most third-party packages your site relied on also needed updating before they would work at all.

So the question is not “shall we update Umbraco.” It is “shall we fund a rebuild of the site, migrating the content across to a new build.” That is a different size of decision, and it deserves to be treated as one rather than slipped through as maintenance.

It is worth knowing that the same pattern repeated again afterwards: the move from Umbraco 8 to 9 re-platformed onto the modern .NET foundation, another significant step rather than a simple version bump. The platform has moved on twice. A site still on 7 is two architectural generations behind.

What being stranded on Umbraco 7 actually costs you

Umbraco 7 is long out of support. A site running on it still works, which is exactly why the problem gets ignored — nothing is visibly broken. But “still works” and “still safe” are different things. An unsupported platform stops receiving security fixes. It runs on older underlying technology that is itself ageing out of support. The packages it depends on are frozen. With every month that passes, the gap between your site and a secure, current platform widens, and the eventual rebuild gets larger.

If the site takes enquiries, processes any customer data, or is the main way customers find you, this is a business risk, not a technical footnote. A compromise on an unsupported CMS is a data exposure and a reputational event, and “we never got round to upgrading” is not a defensible position after the fact.

The two wrong responses

There are two common mistakes once the penny drops. The first is to do nothing, because the site still works and a rebuild sounds expensive. That defers a cost that only grows, and gambles on nothing going wrong in the meantime. The second is to panic into a like-for-like rebuild — recreate exactly what you have on the new platform, including the parts you never used and the decisions that made the old site hard to maintain. That spends real money to reproduce old problems on newer software.

The rebuild is a forcing function, and a forcing function is an opportunity. It is the natural moment to ask what the site should actually do now, what content genuinely needs to come across, and what was only there because it always had been.

What to do

Start with an honest assessment of what you have: the version you are on, the custom functionality the site depends on, the packages in use, and what the site genuinely needs to deliver going forward. That assessment turns a vague “we need to upgrade Umbraco” into a defined, costable piece of work, and it usually reveals that the rebuild can be leaner than the original because it leaves the accumulated cruft behind.

Crucially, this assessment should be done by someone whose interest is your outcome, not the size of the build. An agency that will do the rebuild has a reason to make it large. An independent view fixes the scope first.

If your site is still on Umbraco 7, the clock is not ticking loudly — which is precisely the danger. I will tell you where you actually stand and what the move genuinely requires.

Start a Conversation