Snapshot
Create a source-to-target baseline for the selected scope.
Plans / Your reusable definitions
MySQL replication.
Reuse the plan.
A plan brings your source and target together with the table and column mappings between them. Snapshots, CDC, comparisons, and reconciliation can reuse those rules.
Example saved plan
Commerce replica
commerce_prod → commerce_replica
- Endpoints
- Production / Replica
- Table pairs
- customers, orders, inventory
- Column rules
- Keys, casts, expressions
- Source filter
- orders: status = 'paid'
Change capture
Follow changes with a supported capture method.
Compare
Check the mapped tables and inspect row differences.
Reconcile
Review the proposed repair scope before applying changes.
A saved definition, a separate run
The plan describes it.
You decide when it runs.
Saving a plan does not copy data. Inspect the endpoints and schema before launching an operation from the app.
Start in Plans
Create a new mapping or open an existing plan. Choose the source and target databases, then review the table pairs discovered from their schemas.
Refine the mapping
Inspect each table’s columns, keys, casts, expressions, and filters. Check schemas and review DDL differences before saving changes.
Keep the scope consistent
Reuse the saved plan when you set up supported operations. Recheck it when either schema changes, and review the result of every run.
Start with the right mapping.
Explore the current macOS editor, from endpoints to columns.