- Notifications
You must be signed in to change notification settings - Fork 0
Home
A local app that moves data between SQL databases — today SQL Server → PostgreSQL — and
refuses to call it a success until the data verifiably arrived. You run it on your own
machine, it serves a single page on localhost, and no data or credential ever leaves
your computer.
The one-sentence design: the copy and its verification share one transaction, and the commit happens only after verification passes. A failed run leaves the target byte-identical to what it was before.
| Page | What it covers |
|---|---|
| Getting Started | Download or build, first run, the five screens |
| How It Works | The pipeline, the single-transaction decision, type mapping |
| Safety Guarantees | What is guaranteed, what is not, the four escape hatches |
| Troubleshooting | What each stop message means and what to do about it |
| Message Codes | The stable message-code contract and how translations work |
| Roadmap | Where this is going: any SQL to any SQL |
The canonical deep-dive documents live in the repository under
docs/ — this wiki is the
guided tour, those are the reference.
No schema creation (bring your own schema), no live sync (it is a cutover tool), no data transformation (move faithfully, transform afterwards). The reasoning behind each is in Roadmap.
SQL Data Migrator — MIT licensed. The wiki mirrors the repo's docs/; when they disagree, docs/ wins.