SQLite to SQL Server Converter

Need more context? Compare DBConvert and DBSync side by side →

• Dynamic typing. Inspects actual column values during read and proposes a strict SQL Server target type in the type-mapping review — a SQLite column declared INTEGER that holds text in real rows is flagged so you pick nvarchar instead of taking the declaration at face value.
• Generated keys. Maps SQLite INTEGER PRIMARY KEY / AUTOINCREMENT (tied to ROWID) to SQL Server IDENTITY on the PK column, and reseeds with DBCC CHECKIDENT above the loaded maximum key value — so the application's next insert does not collide.
• Dates and booleans. Detects SQLite columns that store booleans as 0/1 integers or dates as ISO-8601 text and maps them to SQL Server bit and datetime2 respectively — overridable per column when the source uses a non-standard format.
• GUID values and Unicode. Validates SQLite text GUIDs and maps them to SQL Server uniqueidentifier on the target, and creates string columns as nvarchar so Unicode round-trips safely without the source needing a VARCHAR(n) CHARACTER SET hint.
• Triggers, CHECK constraints, and other procedural code — outside DBConvert's scope. DBConvert's migration covers tables (with their fields, types, defaults, and indexes), views, and foreign keys. SQLite triggers, CHECK constraints, partial indexes, expression indexes, and WITHOUT ROWID table specifics stay in the source and are recreated manually in T-SQL where the equivalent feature exists (SQL Server has filtered indexes for partial-index semantics; CHECK constraints port one-for-one when the expression is portable).