Migration AtlasMigration Atlas reads SQL migration files and turns them into clear Markdown reports before you run them: what the migration does and whether it runs in a transaction, the destructive operations (DROP, TRUNCATE, DELETE or UPDATE without WHERE, dropped columns and constraints), the tables it touches, the PostgreSQL operations that block reads or writes or rewrite a table, with the safer way to write them, and a rollback plan with a down migration for what can be reversed. Everything runs on your computer. There is no telemetry. The only network request the extension ever makes is the licence check for the optional Pro tier (see Privacy).
What it does
Free, trial and Pro
The free reports need no key, no account and no network connection, and they will not be moved behind the licence key later. The first Pro command starts a free 14-day trial on this computer. After that, Pro is a one-time purchase, not a subscription: Pro Personal USD 19 (one person, use at work allowed) or Pro Business USD 39 per user (one key per user of an organisation). A key works on up to 3 computers. The checkout page shows the final price and any taxes for your country. Licence keys are sold by Dodo Payments, the merchant of record. Details: licence, terms. CommandsOpen the Command Palette and type
Settings
FAQDoes Migration Atlas connect to my database? No. It reads the text of the open file only. Nothing is sent anywhere, and no database connection is made. Which databases does it support? The summary, destructive operations, tables and rollback plan work for any SQL migration; quoted names in double quotes or MySQL backticks are recognised. The lock-risk review and the SQL of the down migration follow PostgreSQL rules. Which lock risks does it find? Indexes built without CONCURRENTLY, CONCURRENTLY inside a transaction, foreign key and check constraints validated under lock, unique and primary key constraints that build their index under lock, SET NOT NULL, column type changes, volatile defaults and serial columns that rewrite a table, NOT NULL columns without a default, renames, and VACUUM FULL, CLUSTER and REINDEX without CONCURRENTLY. Tables created earlier in the same file are not checked, because they are still empty. Can I run the down migration as it is? It is a starting point: it reverses what can be reversed automatically, and lists the statements that cannot be reversed, such as dropped tables or deleted rows. Review it and test it on a copy of your data first. For IT and procurement
SupportRun Migration Atlas: Report A Problem or open an issue at https://github.com/small-steps-studio/migration-atlas/issues. Never post a licence key or confidential data in a public issue. PostgreSQL is a trademark of the PostgreSQL Community Association of Canada; MySQL is a trademark of Oracle; Migration Atlas is an independent product and is not affiliated with or endorsed by either. |

