How it works

How Microsoft SQL Server migration works

A version change is more than changing compatibility level. The database is rebuilt on the target engine and the result is verified.

Inspect

Read metadata and dependencies without executing customer procedures, functions, views, or triggers.

Rebuild

Create supported schema objects, stream data in batches, and recreate accepted modules.

Prove

Compare row counts and hashes, run integrity checks, and restore-test the final backup.

Windows Agent

Transfer from an internal SQL Server

The Agent connects to SQL Server locally. Your server address, SQL user name, and password are used only by the Agent on your computer and are not sent to the website.

Download and run the Agent without installation.
Enter the code, then connect to the internal SQL Server.
Select the database and upload its temporary secure package.

For a consistent export, pause database writes or use a transactionally consistent copy.

Move Only Tables and Data Between SQL Server Versions

If views, stored procedures, functions, or triggers are not required, the Windows Agent can transfer only table definitions and rows. This avoids failures caused by unresolved or environment-specific modules.

Use this mode when the application recreates its own modules or when the immediate goal is data recovery. Identity properties, safe defaults, keys, ordinary indexes, and supported foreign keys are preserved; excluded objects are reported clearly.

Open conversion dashboard

Fix Identity and Default Values After SQL Server Conversion

Applications often fail after a manual conversion when Identity properties or DEFAULT constraints were not recreated. Inserts can then fail because required numeric or bit columns receive NULL.

The Agent preserves original Identity seed and increment values and safe source defaults. In tables-and-data mode it can add a reported DEFAULT 0 only to eligible NOT NULL numeric and bit columns, while excluding ID, computed, key, and unsafe columns.

Identity values and safe DEFAULT constraints are preserved. Eligible NOT NULL numeric and bit columns without a source default receive 0; ID, unique-key, and foreign-key columns are never changed by this fallback.

Open conversion dashboard

Prove

Compare row counts and hashes, run integrity checks, and restore-test the final backup.

Convert database