Skip to main content

What are the key considerations when planning Umbraco upgrades?

SQL Server compatibility, database schema changes, backup strategy, and why a successful Staging test doesn't guarantee a safe Live upgrade.

Written by Joana Knobbe

Type: Reference
​Category: Umbraco CMS > Versions & Upgrades
​Tags: upgrade planning, SQL Server compatibility, database schema changes, database migration, backup strategy, testing environment, staging, Live upgrade, major upgrade, breaking changes
​

Product: Umbraco CMS, Umbraco Cloud
​Version: All supported versions

Key Considerations When Planning Umbraco Upgrades: SQL Server Compatibility and Database Changes

When upgrading Umbraco, particularly concerning database compatibility and potential changes, it's essential to understand the version requirements and anticipate any impacts on your SQL Server setup. This article provides guidance on these considerations.
​

Umbraco Version Compatibility with SQL Server

  • Supported SQL Server Versions: Up to Umbraco version 10, the platform is compatible with SQL Server 2012. However, starting with Umbraco 13 and onwards, SQL Server 2012 is no longer supported. Users running older versions of SQL Server will need to upgrade their database software to meet the requirements of their desired Umbraco version upgrade.

  • Recommendation: Always verify the specific SQL Server version compatibility before planning any upgrades to prevent system incompatibilities.

Impact of Upgrading Umbraco on Databases

  1. Database Schema Changes: Upgrading from Umbraco v13 to newer versions will lead to schema updates in your SQL database. These updates may include modifications to tables, data structure, and migration of certain data types.

  2. Preparation Guidelines:

    - Review Release Notes: Always check the release notes and any documented breaking changes for the specific upgrade version. This step ensures that you understand the database schema updates and their implications.

    - Backup Strategy: Create a full backup of your database before initiating the upgrade process. This ensures data safety and allows for rollback if necessary.

    - Testing Environment: Before applying the update to your live environment, perform the upgrade on a testing environment to identify and address any issues beforehand.

Why Testing on Staging Isn't Enough for Major Upgrades on Live

A major upgrade that completes cleanly on a testing or Staging environment can still fail once it reaches Live. Staging usually carries little or no real visitor traffic, so nearly all server capacity is free for the database migration. Live carries real traffic at the same time, and that traffic competes with the migration for the same resources — so an upgrade can pass on Staging and still take your Live site down, even when the content is identical.
​
​

d1 diagram


For major version upgrades to a Live environment, don't push directly from Staging to Live without a plan. Instead, see Planning Major Upgrades Safely on Umbraco Cloud for the three self-service options — running it on your existing plan, a controlled local migration, or moving to dedicated resources for the upgrade window — and pick the one that fits your project's size and importance.

By following this information and guidance, you can confidently plan for an Umbraco upgrade while minimizing database-related challenges and ensuring compatibility.

Related Topics

Last updated on August 3, 2026

Did this answer your question?