Cold Banana UAE

Choose your website

DubaiUnited Arab Emirates United Kingdomcoldbanana.com
Let’s talk

UMBRACO

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

UMBRACO RELEASES

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.

ON UMBRACO 13?

Plan for 14 Dec 2026.

That's when standard support ends. The current status is security fixes only.

A LONGER PLANNING WINDOW

Umbraco 17 LTS.

Standard support runs to 27 Nov 2028. It is the LTS target used in the examples below.

Status as at

LTS Long-term support STS Standard-term support

  1. Umbraco 7

    Legacy
    Released
    End of life
    End of life

  2. Umbraco 8

    Legacy
    Released
    End of life
    End of life

  3. Umbraco 9

    STS
    Released
    End of life
    End of life

  4. Umbraco 10

    LTS
    Released
    End of life
    End of life

  5. Umbraco 11

    STS
    Released
    End of life
    End of life

  6. Umbraco 12

    STS
    Released
    End of life
    End of life

  7. Umbraco 13

    LTS
    Released
    End of life
    Security fixes only

  8. Umbraco 14

    STS
    Released
    End of life
    End of life

  9. Umbraco 15

    STS
    Released
    End of life
    End of life

  10. Umbraco 16

    STS
    Released
    End of life
    End of life

  11. Umbraco 17

    LTS
    Released
    End of life
    Supported

  12. Umbraco 18

    STS
    Released
    End of life
    Supported

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.

UPGRADE PATHS

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.

FEATURED LTS PATH

Umbraco 13 to 17

  1. v13
  2. v17 LTS

Move from the v13 long-term support release to v17. v14, v15 and v16 do not each need a separate live launch.

Backoffice extensions, packages, .NET 10 and a rehearsed content migration.

  1. 01

    Patch the test copy

    Start from the latest v13 patch on a copy of the site, not the live environment.

  2. 02

    Assess what will not carry over

    Review AngularJS backoffice extensions, retired editors and macros, packages and integrations.

  3. 03

    Target .NET 10

    Plan the framework move with the custom code and hosting the site actually uses.

  4. 04

    Rehearse the content changes

    Run the content and database changes on the test copy and let editors check real pages.

  5. 05

    Test and plan one release

    Agree the release window, rollback and the checks that happen after go-live.

EARLIER LTS RELEASE

Umbraco 10 to 17

  1. v10
  2. v13
  3. v17 LTS

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

Umbraco 14, 15 or 16 to 17

  1. v14 / v15 / v16
  2. v17 LTS

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

Umbraco 7 or 8 to 17

  1. v7 / v8
  2. New v17 build

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.

HOW WE APPROACH IT

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.

OUR WORK

Related Umbraco builds

All Umbraco case studies

GOOD QUESTIONS

Let’s clear
a few things up.

Keep exploring.

Umbraco development Umbraco Gold Partner Umbraco support & maintenance Compare all CMS platforms

LET’S MAKE IT HAPPEN

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