Database Migration Software for Cross-Engine Transfers

Run compatibility checks, generate versioned migration plans, transfer data locally, and verify every table without sending credentials to external servers.

Architecture built on a shared Rust core

Database Migration Studio separates inspection, planning, execution, and verification into explicit stages. Both the Tauri v2 desktop application and the standalone dbmigrate CLI execute the same Rust engine, storing checkpoints and logs in local SQLite.

ComponentResponsibilitySecurity behavior
Database InspectorReads tables, columns, keys, indexes, views, triggers, and server collationOpens source in read-only mode; never writes to source
Compatibility AnalyzerClassifies findings as BLOCKER, ACTION REQUIRED, or WARNINGFlags unknown types instead of guessing conversions
Migration PlannerTopologically sorts tables by foreign keys and builds target DDLStrips passwords from exported plan.json files
Migration ExecutorStreams batches with Primary Key checkpoints for safe resumeBlocks non-empty targets by default; zero automatic DROP
Verification EngineChecks 9 mandatory invariants plus SHA-256 normalized row digestsVerifies source fingerprint invariance before and after transfer

Supported migration routes and current status

RoutePriorityStatusNotes
MySQL / MariaDB to PostgreSQLP0SupportedHandles UNSIGNED, TINYINT(1), DATETIME, DECIMAL, JSON, ENUM, zero dates
PostgreSQL to PostgreSQLP1SupportedVersion upgrades and cloud consolidation with pgcopydb command export
MySQL to MySQLP1SupportedCollation checks, single-transaction snapshot, PK checkpoint resume
SQLite to PostgreSQLP1SupportedDynamic type affinity normalization and autoincrement sequence reset
CSV / SQL Dump to MySQL or PostgreSQLP2ExperimentalDDL and INSERT fixture ingestion for offline evaluation
SQL Server / Oracle routesP2 / P3PlannedTracked on public roadmap; not enabled for production cutover yet

Frequently asked questions

Does Database Migration Studio require Docker to run?

No. Desktop and CLI users install a standalone native binary without Docker. Docker Compose is used only in CI integration tests against real MySQL, MariaDB, and PostgreSQL containers.

How are database passwords handled?

Passwords remain excluded from serialized plan.json files, HTML and JSON verification reports, and job logs. CLI runs accept credentials through environment variables or OS key storage.