Is Your Umbraco Platform Healthy? A Practical Health Check Guide
Your Umbraco website may be working perfectly well today.
Pages load. Content gets published. Forms work. Integrations are running.
But underneath the surface, an Umbraco platform can gradually accumulate technical debt, outdated packages, legacy integrations and dependencies on older versions of Umbraco and .NET.
None of these necessarily mean that you need a new website.
But they may mean that it is time to understand the technical condition of the platform you already have.
You may not need a new website
Websites and digital platforms rarely stand still.
Over time, new functionality is added, integrations change, packages are updated or replaced, hosting environments evolve and different developers contribute to the solution.
At the same time, Umbraco and the underlying .NET platform continue to evolve.
Eventually, the website you are running today may be technically quite different from the solution that was originally built.
This isn't necessarily a problem.
The important question is whether you know where your platform stands today – and what needs attention next.
What happens as an Umbraco platform ages?
There are several areas worth keeping an eye on.
1. Umbraco and .NET lifecycle
Older versions of Umbraco and .NET eventually move out of active support.
When this happens, security updates and fixes may no longer be available, while upgrading directly to the latest version can become increasingly complex.
Understanding your current versions, their support status and the available upgrade paths is therefore a good starting point.
2. Technical debt
Technical debt tends to accumulate gradually.
Custom functionality, hard-coded integrations, deprecated APIs, outdated packages and configuration changes can all make a platform more difficult to maintain and upgrade.
Individually, these may be minor issues.
Together, they can significantly increase the effort required for future development.
3. Security
A website is part of an organization's technology infrastructure and should be treated accordingly.
The technical platform should be reviewed for areas such as patch status, known vulnerabilities, authentication and authorization, exposed endpoints and dependencies that may no longer be maintained.
The older and more complex the platform becomes, the more important this becomes.
4. Integrations and dependencies
Most modern websites don't operate in isolation.
They connect to CRM systems, payment providers, analytics platforms, marketing tools, APIs, authentication services and other third-party systems.
Over time, some of these integrations may become outdated, unnecessarily complex or dependent on technology that is approaching end-of-life.
Understanding these dependencies is an important part of understanding the health of the overall platform.
5. Performance and stability
Performance issues aren't always obvious.
Slow API calls, inefficient code, database queries, frontend dependencies or infrastructure configuration can gradually affect response times and reliability.
Identifying these issues can often reveal improvements that don't require a major redevelopment project.
6. Maintainability
Perhaps the most important long-term question is simply:
How easy is the platform to change?
A healthy digital platform should allow developers to make changes, add functionality, update integrations and apply security updates without creating unnecessary risk.
If every small change becomes complicated, expensive or unpredictable, technical debt is probably starting to affect the business.
So what is an Umbraco Health Check?
An Umbraco Health Check is a structured technical review of the existing platform.
The purpose isn't to start with the assumption that something needs to be rebuilt.
It is to establish the current technical condition of the platform and provide a practical basis for deciding what – if anything – should happen next.
At Dark Horse, we typically look at areas such as:
Umbraco and .NET versions and lifecycle status
Architecture and codebase
Packages and dependencies
APIs and integrations
Security and potential vulnerabilities
Performance and stability
Technical debt
Maintainability and future upgrade paths
The scope will naturally depend on the complexity of the individual solution.
Turning technical findings into decisions
A technical audit only creates value if the findings can be turned into action.
For relevant findings, we therefore use a simple structure:
Finding → Risk → Evidence → Recommendation → Effort / Impact
This makes it possible to distinguish between issues that should be addressed immediately and those that can safely remain in the backlog.
The outcome should be understandable not only to developers, but also to the people responsible for deciding where time and investment should be spent.
What should happen next?
There isn't one correct answer.
Depending on what the Health Check identifies, the appropriate next step might simply be a number of quick fixes and updates.
For other platforms, it could make sense to perform a controlled Umbraco or .NET upgrade.
More complex solutions may benefit from phased modernization, where individual components and integrations are improved over time.
And in some cases, the technical architecture may have reached a point where a larger rebuild is the most sensible long-term approach.
The important part is that this decision is based on evidence rather than assumptions.
Experience from real-world Umbraco modernization
At Dark Horse, we have worked with existing digital platforms for many years, helping organizations maintain, improve and modernize solutions rather than automatically replacing them.
One example is BIKS, where we have supported the continued development and modernization of an established Umbraco-based platform over several years.
The work has included frontend and backend development, integrations and platform upgrades – while maintaining and improving an existing business-critical solution.
Our experience from this and other modernization projects has reinforced a simple principle:
Understand what you already have before deciding what to replace.
A healthier platform doesn't necessarily mean a new platform
Addressing the right technical issues can improve security, stability and performance while making future development and integrations easier.
It can also reduce long-term maintenance costs and provide a stronger technical foundation for performance, SEO and future digital development.
But sometimes the most valuable result of a Health Check is simply knowing that much of the existing platform is perfectly capable of continuing to do its job.
The objective isn't to find reasons to rebuild.
It is to understand the platform well enough to make the right decisions about what comes next.
Not sure about the health of your Umbraco platform?
If you're running an existing Umbraco solution and are unsure about its technical condition, support status or future upgrade path, we would be happy to take an initial look.
Dark Horse offers an Umbraco Health Check that provides a structured assessment of your existing platform, identifies relevant risks and opportunities, and provides a prioritized roadmap for what to do next.
Talk to us about your Umbraco platform →
