Migration
What is database migration?
Database migration moves schema and rows from one engine to another. Loop Life Data Migration translates SQL and keeps a lineage of what changed. Read the script before you run it.
Moving a database is more than a copy
A migration takes tables from a source engine and lands them on a destination engine. Types, keys, and SQL dialects do not match one-for-one. A script that ran on SQL Server will not be the same script on PostgreSQL.
Loop Life Data Migration is the suite application for that job. It is not the synthetic-data generator and it is not the SQL IDE.
Read the SQL before you trust it
Application SQL rewrites the script for the engine you are moving to. T-SQL and PL/pgSQL are in that set. The rewritten statement is something you read before you run it. A finished cutover, an uninterrupted move, and a perfect rollback are not guarantees of the program.
Data Lineage records which column landed where. A widened type or a skipped key is a line in that history. The logs stay on the computer that ran the job.
Transactional integrity, stated carefully
ACID is the usual description of a reliable transaction: atomicity, consistency, isolation, and durability. Those words belong to the database engine that commits the work. Loop Life does not replace the engine's transaction manager and does not certify that a migration is ACID.
What the program does give you is the rewritten SQL, the column map, and the run record, so you can see what changed before you depend on it.