PostgreSQL
Firebird

PostgreSQL to Firebird Converter

Move PostgreSQL tables and rows into a Firebird database, with a type-mapping review and saved jobs you can run again.

Version
5.0.53
Release Date
Sept. 30, 2026
Size
22.0 MB
Platform
Windows 10 or later

Rather not run it yourself?

Let us do the migration →

Copy a PostgreSQL database into Firebird without writing the target schema by hand. DBConvert connects to PostgreSQL and to the Firebird server, proposes a Firebird type for every column, and creates the tables before it moves a row.

  • Reads PostgreSQL on your own server, Amazon RDS / Aurora, Azure Database for PostgreSQL, Google Cloud SQL, or Supabase.
  • Writes to a database on a local or remote Firebird server, named by its path on that server or by its alias.
  • The same download is the Firebird to PostgreSQL converter, so a database can go out and come back with one product.
  • Runs on Windows as a desktop application.
How it runs

A Windows application that talks to both servers

You install it, point it at PostgreSQL and at the Firebird server, and transfer directly between the servers. Connections, tables, and mappings remain available on separate screens as you refine the job.

A path, not a database name

Firebird has no list of databases to pick from. You enter the server's host and the target database's path on that server, or its alias, together with the connection character set - UTF8 is offered first.

Choose the dataset

Select the tables you need and apply per-table row filters when only part of the PostgreSQL data belongs in Firebird.

Saved and repeatable

A job stores both connections, the table selection, and the options. Run it again from the interface, or start it by name from a batch file or Task Scheduler with --run-job.

What needs attention

How DBConvert handles the PostgreSQL → Firebird differences

Every mapping below is a default you can review or override per column before the run.

In PostgreSQL Why it does not carry over What DBConvert does
NUMERIC(p,s) Firebird 4 and 5 support up to 38 digits; Firebird 3 supports up to 18. DBConvert checks the destination server version. On Firebird 4 or newer, NUMERIC(38,10) becomes DECIMAL(38,10). On Firebird 3, wider declarations are limited to 18 digits and reported before the run. Resolve the capacity mismatch before loading: values requiring more digits may be stored incorrectly.
SERIAL, BIGSERIAL PostgreSQL draws the next key from a sequence; Firebird needs a generator and a trigger, or an identity column. Created as INTEGER or BIGINT with the key values copied. No generator is created, so add one before the application starts inserting.
TEXT, JSON, JSONB Firebird has no unbounded text column and no JSON type. Become BLOB SUB_TYPE TEXT. Use a UTF8 target connection for the text-BLOB writer. JSON arrives as text; PostgreSQL's JSON operators need application-side changes.
BYTEA, arrays Firebird has native arrays, but DBConvert does not map PostgreSQL arrays to them. Both become BLOB SUB_TYPE BINARY. If the application needs the array elements one by one, plan a child table.
UUID, enum types Firebird has neither a UUID type nor user-defined enums. Become VARCHAR, holding the value as text.
TIMETZ, INTERVAL A time with an offset, and a duration - neither has a Firebird column type chosen for it here. TIMETZ becomes TIMESTAMP and INTERVAL becomes VARCHAR(255), holding the interval as text.

Procedural code stays behind

The migration covers tables - their fields, types, defaults, and indexes. PL/pgSQL functions, triggers, and extension-backed objects stay in PostgreSQL and are rewritten by hand in Firebird PSQL, along with application SQL that uses ILIKE, ON CONFLICT, or :: casts.

Where this tool stops

There is no SSH tunnel on the Firebird side: the Firebird server's port, 3050 by default, has to be reachable from the machine running DBConvert. Run a test job on a copy before switching the application to the Firebird database.

Supported versions and services

PostgreSQL

  • PostgreSQL 8.x through 17.x
  • Amazon RDS / Aurora for PostgreSQL, Azure Database for PostgreSQL, Google Cloud SQL, Supabase
  • PostgreSQL schemas (public, custom schemas)

Firebird

  • Firebird 2.x, 3.x, 4.x, 5.x and InterBase

How to migrate PostgreSQL to Firebird

DBConvert opens in GUI mode and walks the job from connection to commit:

1

Connect to PostgreSQL source database

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

Connect to PostgreSQL source database from DBConvert

PostgreSQL source

Read from self-hosted PostgreSQL, Amazon RDS / Aurora for PostgreSQL, Azure Database for PostgreSQL, or Google Cloud SQL.

2

Connect to Firebird destination database

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

Connect to Firebird target database from DBConvert

Firebird target

Enter the Firebird server's host and the path of the target database on that server, or its alias — Firebird target settings.

Steps 3-6: the same for every database pair

Source and target are connected - steps 1 and 2 above. What follows is identical whichever two databases you picked, so it lives in one place. Each step below opens at its own section.

Open the full guide

All four steps in one page, plus software features, command-line mode, scheduler, and system requirements.

See all features

Move PostgreSQL data into Firebird

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

Windows Windows 10 or later · 22.0 MB