Improve Educations
An eLearning platform migrated from Umbraco 7 to 13, preserving course content and student access. Administrators manage learning materials independently, while partner companies sell courses through branded profiles.
Umbraco 8 reached end of life on 24 February 2025. Critical security patches are available through a separate paid XLTS agreement with Umbraco HQ; without this coverage, new vulnerabilities require independent mitigation.
Without vendor assistance, your team or support partner has to investigate CMS issues independently. Problems involving unsupported packages may take longer to resolve.
Sites handling personal data need a documented approach to securing an end-of-life CMS. Security reviews require evidence of the safeguards in place.
Payment platforms, CRMs and other connected services continue to evolve. Packages built for version 8 need compatibility checks when those systems change.
Older Umbraco APIs and .NET Framework can limit compatibility with newer tools. Adapting them takes extra development time, and some changes may need reworking during migration.
AI search and editorial tools built for newer Umbraco versions are not directly compatible with version 8. Similar functionality can be added through custom integrations, with extra development and maintenance effort.
UKAD is an Umbraco Silver Partner and a Microsoft Solutions Partner. Our engineers work across the CMS and .NET code, addressing custom functionality from the start.
Over 15 years of Umbraco work have included upgrades of live websites across major versions. That experience covers adapting custom features for supported releases.
A technical audit and estimate make the scope visible early. The migration is divided into manageable stages with agreed checks, so you can see what is ready for launch.
Many UKAD Umbraco specialists work with the same clients for 5+ years. A consistent team retains knowledge of the platform across releases, reducing repeated handovers as the website evolves.
UKAD can provide one Umbraco specialist, a dedicated team, or a fully managed migration project. QA and project management are included when the scope calls for them.
Our engineers can build custom support assistants and personalisation features around your content and business systems. The scope includes integration requirements and ongoing running costs.
We discuss your Umbraco 8 setup and whether you need support now or want to migrate. The outcome is a clear direction: maintain the existing platform or assess the work involved in an upgrade.
Our engineers examine the .NET Framework code, content types, packages and integrations. You receive a route to Umbraco 17 LTS and an effort estimate showing which parts can be reused or need rebuilding.
The team transfers content and adapts or rebuilds custom functionality for modern .NET. You can review the migrated pages in a staging environment while the existing platform remains live.
QA checks editorial workflows and critical customer journeys; engineers verify integrations and URL redirects. After launch, UKAD provides technical support under agreed response priorities.
News and articles from the UKAD team.
Yes. Your website can continue running after Umbraco 8 reached end of life on 24 February 2025. However, standard security updates and official support are no longer provided. New vulnerabilities may remain unpatched, and compatibility issues can arise as third-party packages and connected systems change.
If an immediate migration is not practical, UKAD can maintain existing functionality and resolve production issues while you prepare for the move. This work does not replace security updates from Umbraco HQ. Continued access to critical security patches requires a separate paid Extended Long-Term Support (XLTS) agreement with Umbraco HQ.
Staying on Umbraco 8 can give you time to plan the budget and scope of a migration, but moving to a supported release remains the long-term approach.
Yes. If a feature solves an immediate business need, UKAD can develop it for your existing Umbraco 8 website. The main consideration is whether that work will need to be repeated during migration. A change closely tied to version 8 may require redevelopment, while functionality built separately from the CMS may be reusable.
If migration is already scheduled, it may be more practical to include the feature in the new website. For urgent requirements, UKAD can assess the additional effort of delivering it now and adapting it later, so you can weigh the earlier benefit against the cost.
For a migration from Umbraco 8, Umbraco 17 LTS is generally the preferred target. Its official support lifecycle runs until 27 November 2028, including a final year of security-only updates. Umbraco 13’s end-of-life date is 14 December 2026, making it a short-term option for a new migration.
An interim release may be considered if a critical dependency prevents an immediate move to 17. In that case, the migration plan should explain why the intermediate step is needed and when the website will move to the intended long-term version.
There is no direct in-place upgrade from Umbraco 8 to Umbraco 17 LTS. However, version 17 can be the final destination without launching your website on intermediate releases.
When retaining the existing database, the documented route passes through Umbraco 10 and 13. These steps take place in a separate migration environment without interrupting live operation. Alternatively, a new Umbraco 17 installation can be built and the content transferred into it using migration tools.
Both approaches involve adapting or rebuilding functionality for modern .NET. Package compatibility and custom backoffice extensions also need assessment.
Yes. UKAD can migrate Umbraco 7 websites to a supported release, including Umbraco 17 LTS. The existing implementation is reviewed first to establish what can be retained and how much redevelopment is needed.
Moving from version 7 involves more than updating the CMS. Content needs to be mapped to the new platform, while custom functionality may need rebuilding for modern .NET. Depending on the approach, intermediate content migrations may be required. A redesign is optional: the project can focus on replacing the underlying platform while keeping the familiar website experience.
The scope covers moving your website to a supported Umbraco release, including content transfer and the development work needed to retain its existing functionality. Package replacements and changes to integrations are included where required by the new platform.
A redesign or new features can be added to the project, but they are not required for the migration. Hosting changes and ongoing support are agreed separately, so the estimate makes clear what is included.
The functionality your business relies on can often be retained, even when the code behind it needs to change. Code tied to Umbraco 8 or .NET Framework must be adapted or rebuilt for the new platform. Business logic that does not depend on those older APIs may be reusable.
For each package, UKAD checks whether a compatible version exists. If it is no longer maintained, the required functionality may be covered by a native Umbraco feature or a replacement package. Custom backoffice editors need particular attention because the editor interface has changed.
Where a replacement uses a different storage format, data conversion may be required. Any feature that cannot be carried over as it stands is discussed with you before a replacement is agreed.
The migration is planned to preserve your existing content. Transferred pages and media are checked against the original website. If older content formats need conversion, the result is reviewed to make sure information remains accessible and displays correctly.
For search visibility, existing URLs are retained where possible. When an address changes, a permanent redirect points visitors and search engines to the corresponding page. SEO metadata is carried over, and indexing checks are completed before launch.
Search rankings cannot be guaranteed. Temporary fluctuations can occur while Google processes the changes, particularly when URLs differ. This preparation reduces avoidable disruption, but it does not remove every migration risk.
Yes. Development and testing take place in a separate environment while your current Umbraco 8 website continues serving visitors. Your editors can usually keep publishing during this period.
Before launch, a short pause in content editing may be needed to transfer the latest changes. Websites that receive orders or member registrations need additional planning to keep those records consistent during the switch. Any required maintenance window is agreed in advance; zero downtime cannot be guaranteed for every setup. UKAD can also help with Umbraco Cloud and hosting if the migration includes a change of infrastructure.
UKAD’s indicative timeframe for a migration from Umbraco 8 to Umbraco 17 LTS is four weeks or more, depending on the redevelopment required.
What affects the timeline | Why it matters |
|---|---|
Custom functionality | Features tied to older APIs need adapting or rebuilding. |
Unsupported packages | Replacements may require changes to the way content is stored. |
Connected systems | Existing integrations need compatibility checks and testing. |
Client review and launch | Feedback and release approval need time in the schedule. |
UKAD provides a project-specific timeline after reviewing the website.
UKAD’s pricing for migration from Umbraco 8 to Umbraco 17 LTS starts at US$9,000. This is an indicative starting price, rather than a fixed fee for every website. The final quote reflects the development work identified in the technical assessment.