Umbraco 13 to 17 Migration Hub

No. Umbraco supports a direct LTS-to-LTS upgrade path. You can go straight from Umbraco 13 to Umbraco 17, all intermediate migrations are applied automatically.

For most mid-sized sites with moderate customization, 4 to 6 weeks end to end including discovery, build, UAT, and cutover. Heavily customized enterprise platforms run longer (8 to 12 weeks). Simple sites with minimal customization can be completed in 2 to 3 weeks.

Custom backoffice extensions. The Umbraco backoffice moved from AngularJS to a modern Web Components architecture in v14, which means any custom property editors, dashboards, or backoffice UI you have will need rebuilding. The discovery phase exists specifically to surface and scope this work before it becomes a problem mid-build.

You can buy extended support directly from Umbraco, but this is meant as a bridge, not a destination. Extended support keeps security patches flowing while you complete a migration that's already in flight. Using it as an indefinite strategy means paying a premium to defer a problem that gets harder every month.

Our discovery audit identifies this early. Most actively-maintained packages have v17 releases or roadmap commitments. For unmaintained or niche packages, we evaluate three options: replace with a maintained alternative, contribute v17 support upstream, or rebuild the functionality natively. We've handled all three.

Yes. Umbraco's migration tooling handles the database schema and content migration automatically when going LTS-to-LTS. The work that needs human judgment is on the code side, custom logic, property editors, integrations.

Yes. We deliver Umbraco migrations across many global clients including UK, US, Europe, Australia, Middle East etc. Our team is set up for distributed delivery with overlapping working hours.

Specialist partners reduce risk in three ways: (1) faster, more accurate scoping because we've seen your situation before; (2) fewer architectural mistakes because we know how Umbraco actually wants to be used; (3) better long-term maintainability because we don't write workarounds for problems that have native solutions. The cost of getting this wrong with a generalist team usually exceeds the savings.