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.
When tables-and-data mode is the simpler choice
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.
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