dbmigrate helps developers compare, promote, and verify database changes—
and refresh lower environments with useful, masked data.
dbmigrate1ALTER TABLE app.orders2 ADD COLUMN status varchar(32)3 NOT NULL DEFAULT 'pending';Pick PostgreSQL or MySQL to see the version support, recovery approach, and workflow for your product.
Compare and promote PostgreSQL schema changes, then refresh lower environments with selected, related, masked data.
Per developer seat for the PostgreSQL edition. Install on up to two devices.
Compare and promote MySQL schema changes with recovery steps designed around MySQL’s DDL behavior.
Per developer seat for the MySQL edition. Install on up to two devices.
Each edition is licensed separately. A PostgreSQL license does not include the MySQL product, or vice versa. The price shown is the current annual list price; online checkout is not available yet.
From one column to an entire schema,
move exactly what you need—with the
context to make the right call.
Compare source and target side by side. Sync a full schema or select individual tables, indexes, views, functions, and more.
FULL & SELECTIVE SCHEMA SYNCbigintPKbigintFKtimestampvarchar(32)Copy whole tables, filter with a WHERE clause, or pick rows from a grid. Include related parents and children in dependency order.
WHERE status = 'shipped'Keep exact SQL, results, snapshots, and generated rollback scripts together in local run history.
Save selections as profiles. Compare, plan, and apply from the desktop or the dbmt CLI, with protection gates intact.
dbmt compareA workflow that gives you the full picture before you commit.
Choose any two connections of the same engine. See what’s new, changed, or only in the target.
Inspect the generated SQL, check warnings, and dry-run the plan before making changes.
Approve the plan, follow each step, and keep the result, SQL, and recovery details in your history.
Promote a reviewed schema to the next environment. Refresh development with the data that makes testing meaningful.
Select changes, inspect SQL, and satisfy the target’s protection gates. After execution, review the run results and compare schemas again.
Filter source rows, include related data, apply reusable masking rules, and set environment-specific column values before copying.
Choose your own connection pairs; these are example workflows, not a fixed pipeline. Source and target must use the same database engine.
Six additions bring discovery, precise data selection, reusable masking, and a more personal workspace to the core workflow.
Discover databases on your server and PostgreSQL schemas as selectable chips. Keep manual entry available when discovery permissions are restricted.
DATABASE & SCHEMA DISCOVERYTest a per-table WHERE condition, pick primary-key rows from a grid, or set a row limit. Review filter badges and estimates before copying.
FILTERS, ROW PICKS & LIMITSSaved connections, settings, and history use a persistent application data location, with migration of legacy settings during upgrades. Published by MoNeel Ventures LLC.
PERSISTENT CONNECTIONS & IDENTITYChoose Light, Dark, or System appearance. Your preference persists, alongside configurable automatic locking and keychain unlock settings.
APPEARANCE & SECURITY SETTINGSSet fixed text, number, Boolean, or SQL NULL values per column. Inspect before-and-after previews, with clearer schema-sync controls in dark mode.
COLUMN OVERRIDES & REFINED SCHEMA SYNCBuild a searchable rule dictionary with wildcard column patterns, categories, deterministic seeds, and a live playground. A consistent app icon completes the desktop experience.
MASKING DICTIONARY & APP ICONReview the final values. Column overrides run after masking; check their final values and database constraints before execution. Masking presets help configure rules and do not certify regulatory compliance.
PostgreSQL 13–17 and MySQL 8.0 / 8.4 LTS; same-engine connections; full or selective schema synchronization; dependency ordering; generated SQL review and dry runs.
Whole tables, WHERE filters, primary-key row selections, row limits, related parent/child rows, conflict handling, masking, and fixed column overrides.
Per-connection protection levels, stronger production gates, pre-apply schema checks, snapshots, exact SQL and run results, and engine-aware rollback scripts. Recompare schemas to inspect the resulting state.
Saved profiles, desktop workflows and the dbmt CLI, database/schema discovery, persistent connections and settings, local run history, encrypted saved secrets, and automatic locking.
Reusable rules for PII, health, financial, security, and custom categories; Faker replacements, salted hashes, regex replacements, fixed strings, and NULL; deterministic seeds and a rule playground; Light, Dark, and System themes.
Scope is based on the v1.2 product specification and six supplied feature implementation notes (FEAT-001–006). It describes the product documentation, not an independent audit of a shipping release. Cross-engine conversion and automatic MySQL DDL rollback are outside this scope.
Set protection per connection, not by a rigid pipeline. Every target gets a review. Sensitive environments get stronger gates.
High-protection targets require a dry run, a snapshot, and a typed database name. Target changed since comparison? Compare again.
Mask sensitive values in memory before copying to a lower-protection environment. Review every column’s rule and use consistent deterministic replacements for related values.
Keep app state on your computer, with AES-256-GCM encryption for saved secrets, a master password, and automatic locking.
No AI service receives your row values.
Engine-aware, down to recovery. PostgreSQL supports rollback within its transactional phase. MySQL schema changes commit step by step; dbmigrate uses shadow dry runs and reviewed rollback scripts. It never promises automatic MySQL DDL rollback.
Two free schema-diff tools. Two enterprise platforms. One side-by-side look at the workflows each covers.
| Workflow / capability | dbmigrateDocumented product scope | pgAdmin Schema DiffFree / open source | MySQL WorkbenchCommunity / GPL | Flyway EnterpriseEnterprise platform | Liquibase SecureEnterprise platform |
|---|---|---|---|---|---|
| Schema comparison focus | PostgreSQL + MySQL; same engine | PostgreSQL databases or schemas; same major version | MySQL live databases, models and SQL scripts | Multi-engine; advanced capabilities vary by engine | Multi-engine; capabilities vary by database |
| Compare & generate SQL | Full or selected objects; review before apply | Object differences + selected synchronization SQL | Schema diff, synchronization + SQL generation | Schema comparison + generated migration scripts | Database diff + changelog-based changes |
| Environment promotion | Reviewed source → target sync; protection per connection | Run generated synchronization SQL | Synchronize chosen objects between sources | Versioned migrations + CI/CD workflows | Versioned changesets + automated deployment flows |
| History & recovery | Local run SQL, snapshots and reviewed rollback scripts | No migration ledger established here¹ | SQL history; no versioned release ledger established here¹ | Migration history, validation + undo migrations | Tracked changesets, history + rollback definitions |
| Drift & verification | Pre-apply schema check; recompare and inspect run results | Compare database/schema state on demand | Compare live database or model state | Drift and change reports | Drift inspection + deployment tracking |
| Lower-environment data | Filtered/selected rows, relations, row limits + fixed overrides | Not established in Schema Diff docs¹ | Data editing/export; migration wizard is separate | Masked refresh workflow not established here¹ | Masked refresh workflow not established here¹ |
| Reusable data masking | Rule dictionary, deterministic seeds + preview playground | Not established in Schema Diff docs¹ | Not established in cited Community feature list¹ | Not established in cited Flyway feature summary¹ | Not established in cited change-automation docs¹ |
| Safety & governance | Local review gates, dry runs, encrypted credentials | Review generated synchronization scripts | Review generated synchronization scripts | Policy checks + automated deployment controls | Policy checks + governed deployment flows |
How to read this comparison. Checked October 1, 2026 against the official documentation linked in each column. dbmigrate reflects the documented scope above. Enterprise capabilities can depend on edition, database, and configuration. This compares the named products, not every product in each vendor’s portfolio.
¹ “Not established” means the cited source does not establish that workflow; it does not prove the capability is unavailable. pgAdmin’s column covers Schema Diff specifically. MySQL Workbench also has a migration wizard; its schema-diff focus here is MySQL. Additional source: Workbench schema comparison documentation.
Areas to evaluate, not announced or available features.
Explore dbmigrate with a 14-day trial.
Bring clarity to your next database change.
macOS · Apple Silicon & Intel / Windows x64
Choose dbmigrate for PostgreSQL if you work with PostgreSQL 13–17, or dbmigrate for MySQL for MySQL 8.0 and 8.4 LTS. They are separate single-engine products; a license for one engine does not include the other.
The current listed price is $99 USD per year per developer seat for one engine edition. One seat may be installed on up to two devices. PostgreSQL and MySQL are licensed separately. Online checkout is not available yet.
Yes. Copy whole tables, test a WHERE condition, select primary-key rows, or apply a row limit. Include related rows, review masking rules, and use fixed column overrides for environment-specific values. Row limits are not a guarantee of a representative random sample.
The reusable masking dictionary supports wildcard column patterns, categories, enabled/disabled rules, deterministic seeds, and a live playground. Rules include Faker replacements, salted hashes, regex replacements, fixed strings, and NULL. Column overrides run after masking, so review final values. Presets are configuration aids, not compliance certification.
Inspect recorded SQL and run results, then compare source and target schemas again. The current documented scope does not promise automated row-by-row reconciliation or checksum verification; those are development opportunities.
The application uses a persistent local data location for saved connections, settings, and history, with migration of legacy configuration during upgrades. Light, Dark, or System appearance preferences are saved. Database and schema discovery also keeps a manual-entry fallback.
PostgreSQL 13–17 and MySQL 8.0 and 8.4 LTS, including self-hosted databases and managed services running those versions. Source and target must use the same engine. MariaDB, MySQL 5.7, SQL Server, and Oracle are outside the current scope.
dbmigrate synchronizes environments of the same engine: PostgreSQL to PostgreSQL, or MySQL to MySQL. It does not convert schemas or data between database engines.
Every run opens Review & Confirm with the change list and generated SQL. High-protection targets require a passing dry run, a pre-apply snapshot, and a typed database-name confirmation. The target schema is checked again before execution; if it has changed, you must compare again.
PostgreSQL changes in the transactional phase roll back automatically on failure; some operations run in a separate phase. MySQL DDL commits one statement at a time and cannot roll back automatically. dbmigrate records applied steps and generates rollback SQL for review. Schema rollback scripts do not reverse copied data; restoring data requires an appropriate data export.
When copying from a higher-protection source to a lower-protection target, every copied column needs an approved masking rule or an explicit “Not PII” decision. Values are transformed in memory before writing to the target. Detection uses column names and local samples, with no AI service.
App state stays in local files on your computer. Saved database passwords and SSH secrets are encrypted with AES-256-GCM, protected by your master password. Run history records the exact SQL and results without credentials. Database connections still communicate directly with your chosen servers.