SYS.06 · Systems & Data
CRM → Supabase Mirror
A data-mirroring toolkit that caught a migration about to orphan production.
- Client
- Tilt Media
- Year
- 2026
- Role
- Architect & engineer
- Category
- Systems & Data · SYS.06
The numbers
1
production incident prevented
5,000
record backfill cap
2
abort guards
The engineering
Caught and reverted a genuinely dangerous migration. The prior script would have renamed the live projections table aside and replaced it with an incompatible one — making every existing projection invisible to the CRM while new writes went somewhere else. The runbook proves the rename had already run once, harmlessly, while the table was still empty.
Diagnosed that two supposedly-parallel modules use incompatible data models — one monthly-amount × duration with currency-converted columns, the other a flat amount — and documented that the shared bot must never reuse one CRM’s SQL against the other.
Migrations written defensively throughout: non-destructive column relaxation, two abort guards for detected damage, insert/update-only syncers that never delete, and full idempotency.
Stack
- PostgreSQL
- SQL DDL + RPCs
- Deno
- Base44