Database migration guides: pick your source and target

· 3 min read

dbSlice moves data between the leading databases from a Windows app or the command line, then keeps the new database in sync until cutover and compares both sides key by key. Pick the pair you are moving.

To PostgreSQL

  • Firebird to PostgreSQL

    Move Firebird tables into PostgreSQL from a Windows app or CLI, then keep them in sync until cutover. Upper-case names, charsets and generators covered.

    Read the guide →
  • InterSystems Caché/IRIS to PostgreSQL

    Move tables out of InterSystems Caché or IRIS into PostgreSQL or SQL Server from a Windows app, even legacy tables with no index. Then keep them in sync.

    Read the guide →
  • MySQL to PostgreSQL

    Data migration from MySQL or MariaDB to PostgreSQL: type mapping, unsigned ints, zero dates, MariaDB JSON, pgloader vs dbSlice and a nightly sync.

    Read the guide →
  • Oracle to PostgreSQL

    Move Oracle tables into PostgreSQL from a Windows app or CLI, with no Oracle client to install. Then keep them in sync until cutover. Data, not PL/SQL.

    Read the guide →
  • SQL Server to PostgreSQL

    Move SQL Server tables into PostgreSQL from a Windows app or CLI, keep them in sync until cutover, and compare both sides key by key.

    Read the guide →
  • SQLite to PostgreSQL

    Data migration from SQLite to PostgreSQL from a Windows app or CLI: declared types, 64-bit integers, booleans, dates as text, COPY loads.

    Read the guide →

To SQL Server and Azure SQL

  • Firebird to SQL Server

    Data migration from Firebird to SQL Server from a Windows app or CLI: upper-case names, charsets, BLOBs, generator ids, MERGE upsert, key-by-key compare.

    Read the guide →
  • InterSystems Caché/IRIS to SQL Server

    Data migration from InterSystems Caché or IRIS to SQL Server, no ODBC driver: legacy tables without keys, composite keys, numeric dates, MERGE upsert.

    Read the guide →
  • MariaDB to SQL Server

    Data migration from MariaDB to SQL Server from a Windows app or CLI: unsigned ints, zero dates, IDENTITY ids, MERGE upsert and a key-by-key compare.

    Read the guide →
  • MySQL to SQL Server

    Data migration from MySQL to SQL Server from a Windows app or CLI: JSON, BIT(n), TIMESTAMP time zones, unsigned ints, IDENTITY ids, key-by-key compare.

    Read the guide →
  • Oracle to SQL Server

    Data migration from Oracle to SQL Server from a Windows app or CLI: DATE, NUMBER, RAW GUIDs, empty strings, sequences, MERGE upsert, key-by-key compare.

    Read the guide →
  • PostgreSQL to SQL Server

    Data migration from PostgreSQL to SQL Server from a Windows app or CLI: NUMERIC, arrays, timestamptz, IDENTITY ids, MERGE upsert and a key-by-key compare.

    Read the guide →
  • SQL Server to Azure SQL

    Moving data from SQL Server to Azure SQL Database: copy tables from a Windows app or CLI, keep them in sync until cutover, and check them key by key.

    Read the guide →
  • SQLite to SQL Server

    Data migration from SQLite to SQL Server from a Windows app or CLI: declared types, 64-bit integers, text keys, dates as text, MERGE upsert.

    Read the guide →

To MySQL and MariaDB

  • PostgreSQL to MySQL and MariaDB

    Data migration from PostgreSQL to MySQL or MariaDB from a Windows app or CLI: NUMERIC, timestamptz, arrays, uuid, upsert by key and a key-by-key compare.

    Read the guide →
  • SQL Server to MariaDB

    Data migration from SQL Server to MariaDB from a Windows app or CLI: type mapping, AUTO_INCREMENT ids, upsert by key and a key-by-key compare.

    Read the guide →
  • SQL Server to MySQL

    Migrate SQL Server (MSSQL) to MySQL or MariaDB: type mapping, a T-SQL checklist, MySQL Workbench vs dbSlice, and a nightly sync until cutover.

    Read the guide →

Keep it in sync until cutover

After the initial load, the same job runs on a schedule (upsert, insert-new or incremental by column) while the old system is still in use.

Compare the tools

What dbSlice does not do

  • dbSlice moves data. It does not convert stored procedures, triggers or views; for the table DDL it suggests a CREATE TABLE for your DBA to review.
  • It runs batch jobs, on demand or on a schedule, not real-time replication.

Your pair is not listed? See the supported databases or ask for a free migration assessment.

Try it on your own data: the free Microsoft Store version needs no license key.

In production for 6+ years · 14-day money-back · Runs on your machine