Renaming a BAK or changing COMPATIBILITY_LEVEL does not make a newer backup readable by an older SQL Server. The schema and data must be converted and backed up again on the target version.
From a newer BAK to a target-version BAK
Upload one BAK file, choose the available target SQL Server version, and provide a new database name. The service validates the source, rebuilds supported definitions, transfers rows, audits the result, and returns a restore-ready BAK.
Start with a compatibility preflight
Inventory tables, columns, collations, keys, indexes, views, procedures, triggers, data types, and version-specific features before creating the target database. Keep the source connection read-only.
Build the target and move the data
Create a new target database and generate T-SQL definitions for the target engine. Transfer rows in controlled batches, preserve identity values, and order dependencies so constraints can be recreated safely.
Rebuild, verify, and deliver
Recreate supported programmable objects, document deferred items, compare row counts and SHA-256 hashes, run DBCC checks, and create a native BAK after RESTORE VERIFYONLY or a test restore succeeds.
Convert your database with a guided workflow
Replace fragile manual scripts with inspection, progress tracking, and evidence-backed verification.
Open conversion dashboard