LOOP LIFEDATA SUITE

Loop Life

Data Migration

Secure · Reliable · Flexible

Move data
forward.

Move and consolidate data across databases and environments. The column map, the rewritten SQL, and the run record stay on the computer that did the work.

Download Free TrialLearn More

Source

  • Database
  • Files
  • Cloud
  1. Map
  2. Validate
  3. Transfer

Destination

Database

Target engine

Migration

Illustration

Production PostgreSQL → Azure SQL

Migrating

78%

Tables
184 / 236
Rows
14.8M
Transferred
42.7 GB
Errors
0
  • Schema analyzed
  • Destination prepared
  • Data transfer running
  • Validation pending
  • Secure transfersConnection credentials stay on this computer.
  • Multi-platformSource and destination can be different engines.
  • Local processingTables are processed on the computer running the job.
  • Controlled workflowsStatus, rows, and errors stay with the run.
  • Windows and LinuxWindows, Ubuntu, Debian, and Arch.

Migration without the complexity.

Connect your source. Choose your destination. Control how your data moves.

From one engine to another, Loop Life Data Migration maps columns, rewrites scripts, and keeps a lineage record of the run.

Any source. Any destination.

  1. 1

    Connect

    Open the source and the destination. Connection credentials stay in the key vault on this computer.

  2. 2

    Discover

    The catalog is the tables, columns, and keys those connections returned.

  3. 3

    Map

    Rename columns and change types so the destination is ready to load.

  4. 4

    Migrate

    Move the tables you included. The job can create the target tables from the source catalog.

  5. 5

    Validate

    Lineage records status, rows, and errors. The logs from that run stay on the computer.

Map your data with confidence.

Schema mapping can rename a column and change its type. Data Lineage keeps the source column, the target column, and what changed. A widened type or a key that was not created shows up there.

email_address → email is a rename. The other fields can keep their names.

Source

Destination

  • customer_idcustomer_id
  • first_namefirst_name
  • last_namelast_name
  • email_addressemail
  • created_datecreated_at

Your migration. Your rules.

  • Table selection

    The run moves the tables you included. A skipped table does not look like a finished table.

  • Schema mapping

    Rename columns and change types on the way across.

  • Data mapping

    Source column, target column, and the schema around them stay with the run.

  • Dialect translation

    Scripts are rewritten between dialects such as T-SQL and PL/pgSQL. You read the SQL in the program.

  • Target tables

    The job reads the source catalog and creates the target tables with the types and keys.

  • Lineage

    When, source, target, status, SQL, rows, and errors. Export that record to JSON, XML, YAML, CSV, Excel, Parquet, or text.

  • Run files

    Logs, drift checkpoints, telemetry, and the reports are files from the run on that computer.

  • Connections

    The key vault holds connection credentials on this computer.

Connect the platforms your data depends on.

Move data between the database platforms and environments your organization already uses.

  • PostgreSQL
  • SQL Anywhere
  • Oracle
  • Redshift
  • Databricks
  • Azure SQL
  • MongoDB
  • ClickHouse
  • MariaDB
  • DuckDB
  • SQLite
  • MySQL
  • SQL Server
  • Snowflake
  • BigQuery
View all supported connectors →

Move data across environments.

  1. On-premise
  2. Cloud
  3. Hybrid

A job has a source and a destination. Those can be engines you run yourself, or cloud platforms such as Azure SQL, Snowflake, BigQuery, Redshift, and Databricks.

Databases, files, and cloud platforms.

  • Databases

    Move live tables between engines, or create empty tables on the destination.

  • Files

    CSV, Excel, JSON, Parquet, and related formats when the work is not already in a database.

  • Cloud platforms

    Azure SQL, Snowflake, BigQuery, Redshift, and Databricks.

Know what is happening to your data.

Lineage is the record of the run: when, source, target, status, SQL, rows, and errors. A run that skipped something does not look like a clean run.

Illustration of a run record
JobSourceDestinationStartedRowsStatus
customersPostgreSQLAzure SQL09:141.2MCompleted
ordersPostgreSQLAzure SQL09:22840KRunning
invoicesSQL ServerPostgreSQL——Pending

Your data. Your platform.

WindowsLinux

Ubuntu · Debian · Arch

Loop Life Data Migration supports Windows and Linux, on the computer where you installed it.

Work in your language.

Use Loop Life Data Migration in the language that works for you.

Explore language support →

One tool. Or the entire suite.

Loop Life Data Migration

$39.99

Lifetime license · one seat

One payment. Own your Data Migration license for life.

Start free trial

Want the complete Loop Life Data Suite?

Try Data Migration free.

Connect. Explore. Migrate. See what Loop Life Data Migration can do with your workflow.

Start free trial

14 days. No card. No purchase required.

Related

What is database migration? · SQL Anywhere to PostgreSQL · Oracle

Questions

Can Data Migration translate SQL between engines?

Application SQL rewrites the script for the engine you're moving to. T-SQL and PL/pgSQL are in that set. Read it before you run it.

Where is the record of a migration?

Data Lineage. Which column landed where, and a history. A widened type or a skipped key is a line in that history. The logs are on the computer that ran the job.

What does a Data Migration license cost?

$39.99 once, one seat. Or the suite: $19.99 a month, or 14 days with no card.

Move data forward.

Any source. Any destination. Your data. Your way.

Start free trial

People. Data. A brighter tomorrow.