SQL SERVER · WINDOWS · CHANGE PLANNING

Make the move deliberate.
Plan the way back, too.

Create a reviewable checklist for your version change and migration approach.

Migration profile

01 / INPUTS

Changing the profile regenerates the checklist and clears checked items. Progress stays in this page and is lost on reload.

◇ No server connection. No changes applied.

Migration plan

02 / RESULTS

PLANNING TEMPLATE · VERIFY YOUR EXACT CONFIGURATION

0 tasks complete

Read-only assessment query

SELECT SERVERPROPERTY('ProductVersion') AS product_version,
  SERVERPROPERTY('ProductLevel') AS product_level,
  SERVERPROPERTY('Edition') AS edition;
SELECT name, compatibility_level, recovery_model_desc,
  state_desc, is_encrypted
FROM sys.databases;
SELECT name, value_in_use
FROM sys.configurations
WHERE name IN ('max server memory (MB)',
  'max degree of parallelism', 'cost threshold for parallelism');

Run on source and target with appropriate access. This inventories basic configuration; it does not certify readiness.

UNDERSTAND THE CHANGE

A checklist supports
an approved runbook.

This planner highlights the work to review. It does not assess your databases, schedule a migration or execute upgrade commands.

Supported scope

Windows SQL Server 2016–2022 sources, targeting 2019 or 2022. Newer-to-older migration is blocked because native backups cannot be restored to an earlier SQL Server version. Same-version moves are available only through the side-by-side method.

For an in-place move from 2016 to 2022, SP3 or later is a prerequisite. Edition paths, installed features, architecture, OS support and build requirements must be checked against Microsoft's full matrix. Selecting an edition does not certify that path.

Rollback changes after cutover

Once applications write to the new server, redirecting them to the old server can lose those writes. Rehearse reconciliation or reverse movement before cutover and agree the decision deadline. Lowering compatibility level does not make a newer-version backup restorable on an older engine.

Clustered and encrypted workloads

The AG option adds planning tasks, not a rolling-upgrade procedure. Cluster topology and failover sequencing need a separately validated runbook. TDE requires certificate or key material and private keys to be protected and available for restore. Credentials, logins and server dependencies need separate handling.

Microsoft: SQL Server 2022 upgrade paths Microsoft: SQL Server 2019 upgrade paths Microsoft: backup and restore version restrictions

Guidance checked October 5, 2026. Not a licensing, feature compatibility or production-readiness certification.

Make the move deliberate.Plan the way back, too.