Firebird to SQL Server Converter

Schema and rows into SQL Server, Azure SQL, or Amazon RDS - with editable mappings and checks before the first transfer.

Version: 5.5.0
Release Date: Oct. 31, 2026
Size: 48.1 MB
Platform: Windows 10 or later

Rather not run it yourself?

Let us do the migration →

Move a Firebird database into SQL Server without writing the target schema by hand. DBConvert creates the selected tables, indexes, and foreign keys, maps their columns, and transfers the rows directly between the two servers.

Reads a local or remote Firebird database, including Firebird 4 and 5 types.
Writes to SQL Server, SQL Server Express, Azure SQL Database, or Amazon RDS for SQL Server.
Runs on Windows as a desktop application.
The same download converts SQL Server back into Firebird.

Watch a Firebird to SQL Server migration

One take, from connections and table selection to the verified result.

DBConvert for Firebird & MS SQL, the Windows desktop application. Select 3 tables from a 2,000-table Firebird database and transfer 10 million rows to SQL Server in 36 seconds, then verify the row count. Both servers ran on one host; the app ran in a Windows virtual machine on the same network. Your time depends on hardware, network, and data. Watch on YouTube (3:06).

Prepare the migration before moving data

Connections, tables, and mappings have their own screens. Return to any of them as you refine the job, without restarting the setup.

Select the dataset

Choose tables and use a per-table row filter when only part of the source belongs in SQL Server.

See compatibility issues

The mapping screen flags problem tables. Pre-run checks name columns whose declared numeric capacity exceeds the target's, showing both widths. An unmapped type is named in the log.

Keep the setup

Save connections for reuse and keep the table selections, mappings, and options together in a job. Reopen it for the next test load instead of configuring the pair again.

Convert once, or synchronize during the cutover

Both modes are part of the same DBConvert application.

One-time conversion

Create the target schema and load the selected rows. Use a test database first, validate the result, and run the application's queries before making SQL Server the production database.

Scheduled synchronization

Keep Firebird in use while the SQL Server target is tested. Schedule a synchronization job and define its direction, keys, and conflict rules before allowing writes on both sides.

When SQL Server is the right target

Microsoft reporting and applications

Bring Firebird data into the SQL Server environment used by your reporting tools or a replacement application. Table migration gives those systems a target schema to work with.

Managed database infrastructure

Move the data behind a Firebird application to a managed SQL Server service when you want the provider to handle server infrastructure and routine database maintenance.

How Firebird types map to SQL Server

These defaults apply to a direct transfer into modern SQL Server. Review or override the target type per column, especially where Firebird can store a wider value than the destination.

In Firebird	DBConvert default in SQL Server	What needs attention
`INT128`, wide `NUMERIC` / `DECIMAL`	`INT128` becomes `DECIMAL(38,0)`. `NUMERIC` / `DECIMAL` retain their family and scale; precision is based on Firebird storage capacity and capped at 38.	A 39-digit value will not fit. Resolve the capacity warning before loading; values outside the target range are refused, not silently truncated.
`CHAR`, `VARCHAR`, text BLOBs	Within target length limits, `CHAR` becomes `NCHAR` and `VARCHAR` becomes `NVARCHAR`. Text BLOBs become `NVARCHAR(MAX)`; wider `CHAR` columns also use `NVARCHAR(MAX)`, while wider `VARCHAR` columns use `NTEXT`.	Lengths account for UTF-16 storage; the bounded Unicode types stop at 4,000 units. Choose the correct source connection character set and test target collation and sorting.
`TIMESTAMP`, `TIMESTAMP WITH TIME ZONE`	`DATETIME2(4)` and `DATETIMEOFFSET(4)`, respectively.	An offset is not a named time zone. Check application logic that depends on zone names or daylight-saving rules.
`DECFLOAT`, `TIME WITH TIME ZONE`	`DECFLOAT(16)` becomes `VARCHAR(24)`, `DECFLOAT(34)` becomes `VARCHAR(42)`, and `TIME WITH TIME ZONE` becomes `VARCHAR(19)`.	SQL Server has no matching native types. The application must parse these values if it needs arithmetic or time comparisons.
Generators and trigger-assigned keys	The table's key values are transferred; Firebird trigger logic is not translated into T-SQL.	Plan SQL Server identity or sequence generation separately and verify the next generated value before inserts resume.

PSQL and application SQL need a separate pass

Stored procedures, triggers, and computed expressions need review and rewriting for SQL Server. Schema and row transfer do not convert the application's Firebird-specific SQL.

Supported versions and services

Firebird

Firebird 2.x, 3.x, 4.x, 5.x

SQL Server

SQL Server 2008-2022, including Express editions
Azure SQL Database and Amazon RDS for SQL Server
SQL Server schemas (dbo, custom schemas)
Windows authentication or SQL authentication

DBConvert Studio

30+ databases · cloud · scheduled sync

Need more database pairs? One tool covers 30+ databases.

How to migrate Firebird to SQL Server

Setup: connect Firebird and SQL Server

Pick Convert or Sync, then choose the source and destination connections side by side on one screen. A connection is saved once and reused by every job.

The Setup step in DBConvert: the mode, the Firebird source and SQL Server destination side by side, and the job name

Sync keeps an existing SQL Server database up to date with Firebird: each run carries only the inserts, updates and deletes since the last one.

The Setup step in Sync mode for Firebird to SQL Server: how changes are detected and the direction

Firebird source

Enter the host and the database path on the Firebird server, or its alias, and select the connection character set. See Firebird connection settings. Unsupported requests for connection protection are refused rather than silently ignored.

SQL Server target

Use TCP/IP or Named Pipes, Azure SQL, or Amazon RDS for SQL Server.

Tables & mapping: see every SQL Server type before a row moves

Pick the tables, then open one: each Firebird column shows the SQL Server type it becomes. Change a type or a name in place; the line at the bottom names anything that would fail.

Tables and mapping for Firebird to SQL Server: the table list and one table's columns with their SQL Server types

Execution: start it, and the job is saved

Review what the run will do, start it, and read the log as it goes. The job stays in the list to run again or put on a schedule.

A finished Firebird to SQL Server conversion: the summary and the operation log

Every option, in the guide

Naming rules, table options, row filters, scheduling and the command line work the same for every database pair, so they live in one place.

Open the full guide

See all features

More guides for Firebird ↔ SQL Server

Move Firebird data into SQL Server

Download the current build and run the first job against your own database.

Download DBConvert 5.5.0 Order from US$ 199

Windows 10 or later · 48.1 MB