Firebird
SQL Server

Firebird / Interbase to SQL Server Converter

Move Firebird or Interbase databases into SQL Server, Azure SQL, or Amazon RDS for SQL Server. Schema conversion, type mapping, and optional two-way sync.

Firebird to SQL Server migration moves a Firebird or InterBase database into the Microsoft SQL Server platform.

The hard part is not only copying rows; it is translating Firebird's metadata and server-side code into the SQL Server model.

What DBConvert does on this path: handles Firebird-to-SQL-Server migration as a guided desktop workflow:

  • Connects to Firebird or InterBase sources and SQL Server, SQL Server Express, Azure SQL, or Amazon RDS for SQL Server targets.
  • Maps source metadata to SQL Server tables, columns, indexes, primary keys, and foreign keys.
  • Transfers rows directly or generates a SQL dump file when direct access to the target server is not practical.

What it does not do: Firebird PSQL routines, triggers, and application code should be reviewed and tested as part of the SQL Server migration project, especially when they contain business rules.

Which DBConvert tool fits?

Use DBConvert for planned migration; use DBSync when Firebird must keep running during a staged SQL Server cutover.

DBConvert for Firebird → SQL Server

Best fit for a one-time migration, a repeatable saved session, or a DBA-reviewed SQL dump. Use it when you need schema conversion, type mapping, and row transfer in one workflow.

DBSync for Firebird ↔ SQL Server

Best fit when the Firebird application remains operational while SQL Server is introduced. Synchronization should be planned with clear table ownership and conflict-handling rules.

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

How DBConvert handles the Firebird → SQL Server differences

Firebird and SQL Server differ in identity model, domains, BLOB subtypes, charset, and procedural code. DBConvert maps most of those differences in the wizard with sensible defaults that you can review or override per table; PSQL routines are the one item that still needs a human rewrite.

Generators → IDENTITY / sequences

Creates SQL Server IDENTITY columns (or SEQUENCE objects when the generator is shared across tables) in place of Firebird's generator-based key assignment, and reseeds with DBCC CHECKIDENT above the loaded maximum key value — so the application's next insert does not collide.

Domains

Expands Firebird domains (type, default, NOT NULL, CHECK) into concrete SQL Server column definitions so column behavior is transparent at the table level.

BLOB subtypes

Maps BLOB SUB_TYPE 1 (text) to SQL Server nvarchar(max) and SUB_TYPE 0 (binary) to varbinary(max) by default, overridable per column.

Character sets and collations

Re-encodes Firebird databases created on legacy WIN1252 / ISO8859_1 to Unicode on load and creates SQL Server string columns as nvarchar by default — per-column collations where ordering matters are reviewable in the type-mapping step.

Stored procedures, triggers, and procedural code — out of scope

DBConvert's migration covers tables (with their fields, types, defaults, and indexes), views, and foreign keys. Firebird PSQL stored procedures, triggers, computed-by columns, and event handlers stay in the source and are rewritten manually in T-SQL — PSQL EXECUTE STATEMENT, selectable SUSPEND, and WHEN exception handlers have no direct T-SQL equivalent. Typically a small fraction of the schema, but the one item the tool does not handle.

Supported versions

  • Firebird 2.x, 3.x, 4.x and InterBase
  • 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

Supported in this path

Source Firebird
Target SQL Server
Firebird 2.x, 3.x, 4.x InterBase Microsoft SQL Server SQL Server Express Azure SQL Database Amazon RDS for SQL Server
Firebird

All Firebird Tools

Other directions and pairs
SQL Server

All SQL Server Tools

Migration & sync options

Reverse Conversion

SQL Server to Firebird

Using Firebird to SQL Server Tools

When launching the DBConvert or DBSync application in GUI mode, it guides you through the steps to start database migration or synchronization:

1

Connect to Firebird source database

Specify the username/password and host/port parameters if your source database requires login credentials.

Connect to Firebird source database from DBConvert

Firebird source

Configure Firebird in source and destination settings before mapping tables to SQL Server.

2

Connect to SQL Server destination database

Specify parameters for the destination database similar to the source, defining connection settings and username/password pairs.

Connect to SQL Server target database from DBConvert

SQL Server target

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

More guides for Firebird ↔ SQL Server

Next steps: configure, validate, run

After connecting source and target, the remaining steps are the same for every database pair:

  • Configure migration options — pick tables, fields, indices, views.
  • Issue detection — the built-in checker flags integrity problems before migration starts.
  • Execute — commit the job, monitor progress, save the session for reuse.
  • Schedule and CLI — rerun saved sessions on a schedule or from the command line.
Open the full guide

Steps 3–5, software features, command-line mode, scheduler, and system requirements.

See all features