Move your Umbraco
platform forward.

An older CMS can make every change harder. We help Dubai and UAE organisations plan a move to a maintainable Umbraco platform, with a clear view of the content and integrations that need to come with it.

UmbracoGOLD PARTNER

Where each version stands.

Dates follow Umbraco’s published standard support schedule, reviewed on 21 September 2026. End of life does not switch a site off.

  1. v7 End of life Standard support to September 2023
  2. v8 End of life Standard support to February 2025
  3. v9 End of life Standard support to December 2022
  4. v10 End of life Standard support to June 2025
  5. v11 End of life Standard support to December 2023
  6. v12 End of life Standard support to June 2024
  7. v13 Security fixes only Standard support to December 2026
  8. v14 End of life Standard support to May 2025
  9. v15 End of life Standard support to November 2025
  10. v16 End of life Standard support to June 2026
  11. v17 Supported Standard support to November 2028
  12. v18 Supported Standard support to June 2027

Paid extended support (XLTS) is a separate agreement. It is not included in this schedule and it is not part of a Cold Banana support arrangement unless we agree it with you.

There is more than one route.

The route depends on the version you are on, the custom code, and the add-ons. These examples are starting points.

EARLIER LTS RELEASE

Use v13 as the LTS checkpoint, then continue to v17. Resolve the changes at each stage on a test copy before planning the live release.

Custom .NET code, packages and content editors.

NEWER BACKOFFICE

These versions already use the newer backoffice. Check every intervening release’s breaking changes, update compatible packages and rehearse the database migration.

Rich text, custom extensions and integrations.

REBUILD & CONTENT MIGRATION

One practical route is a new v17 implementation with a planned content migration. Rebuild templates and custom functionality, then map pages, media and redirects into the new site.

Content mapping, functionality and search continuity.

01

Understand the starting point

Review the current Umbraco version, custom code, packages and hosting. Establish which parts can be retained and which need rebuilding before choosing a target release.

02

Give content a clear destination

Inventory pages, media, languages and structured data. Map them to the new content model, run trial migrations and let editors check real examples before cutover.

03

Plan for search continuity

Create a redirect map, review canonical URLs and metadata, and check key landing pages. Monitor the change after launch; a migration should include a plan for search as well as content.

04

Rehearse the release

Test integrations, forms and critical customer journeys in a separate environment. Agree content freeze, backups, responsibilities and rollback criteria before the release window.

A clear way forward.

  1. 01

    Audit

    Review code, content, packages and dependencies.

  2. 02

    Map

    Agree the target platform and migration approach.

  3. 03

    Rehearse

    Trial the move and test the journeys that matter.

  4. 04

    Release

    Coordinate cutover and monitor the new platform.

Related Umbraco builds

All Umbraco case studies

Let’s clear
a few things up.

What’s your
next big thing?

A new platform. A complex integration.
Or an idea you can’t stop thinking about.

Let’s talk about where you want to go.

Start a conversation
WhatsApp