Migrate a system
Replace a legacy system instead of bridging it: pick a template, dry-run it free on your own machine, then load and reconcile with a certificate.
- 1. Pick a templateFree or paid, written by anyone, forkable. See what it needs and what it maps before you start.
- 2. Dry-run it freeOn its sample data first, then against your own system read-only. It writes nothing to your target and calls nothing on TheProtocol; its report holds counts, field names and hashes, never a value.
- 3. Load and reconcileThe load runs exactly once and can resume; both sides are read back and compared; a migration certificate on the ledger carries every report's hash, checkable offline.
Write your own
A template is a folder: a manifest, a proxy spec with its mappings, a README and sample data. Publish it free or for a price; a fork names its parent and pays the parent's author a share of each sale.
tp-proxy migrate new my-migration --from sql --to sql tp-proxy migrate check my-migration tp-proxy migrate publish my-migration --visibility public