Each card shows the eight most load-bearing field mappings. Full guides carry every field, every transformer, and every edge case we've hit.
Sybase IQ export + nightly delta sync
SQL Server views + ODBC bridge
Lightspeed REST API bridge + replay
Gravity Forms + Contact Form 7 + CSV drop
These are non-negotiable. Every migration we've done that violated one of these ended up in a painful reconciliation six months later.
You don't need much. A start call, a status poll, a cancel hatch. Everything else is the mapping and validation you'd be doing anyway.
Start a migration. Body carries source, target, mapping, and validation rules. Returns a migration_id.
Poll status. Returns progress, records processed, errors, and checksum results per batch.
Cancel in-flight. Rolls back partial writes if the migration hasn't crossed its commit point.
The API is the easy part. The scheduling and the communication are what make a migration go calmly.
Tuesdays 1–3pm ET. Drop in with schema questions or dry-run results. No appointment needed.
90 minutes, two weeks out. Walk through mappings, validators, rollback. Nothing surprises us on the day.
Shared Slack channel. Daily 15-min standup. Engineer on call through cutover. Runbook in hand.