ingestr Step 3 of 3

Data migration with ingestr

Freeze the plan and back up the systems

Before the production run, freeze the table map, connection names, target schema, strategy, key definitions, and validation queries. Record the exact version of ingestr and Bruin that you tested.

Then:

  • take a source backup or confirm the latest restorable point;
  • take a target backup before the final promotion if the target already contains data;
  • confirm that source logs will be retained for the full migration and rollback window;
  • confirm who can pause writes, change application routing, and approve rollback;
  • verify that monitoring and alerting are open before the load starts.

Do not treat a migration tool as your backup system. A copy in the destination is not a recovery plan until you know how to restore it.

Sign up to our newsletter

Practical updates on open-source data pipelines, AI analysts, governance, and what we are shipping at Bruin.

The signup form is hosted by Brevo. Allow marketing cookies to load it.