Reconciliation before cutover
Cutover is a decision, and a decision needs evidence. Reconciliation produces the evidence.
This is a generalised method, not a client case study. No client names, schemas, data, or outcomes are published here, and no results are claimed on a client's behalf.
What is reconciling Airtable data before cutover?
Cutover is a decision, and a decision needs evidence. Reconciliation produces the evidence.
Method
- Compare row counts per table, and per relation for join tables.
- Checksum a normalised projection of each row, so formatting differences do not create false mismatches.
- Verify referential integrity: no orphan children, no dangling join rows.
- Sample high-value records and compare field by field, including attachments and long text.
- Re-run the whole reconciliation immediately before cutover, not once a week earlier.
select md5(string_agg(row_key, '|' order by row_key)) as table_digest
from (
select id::text || ':' ||
coalesce(name, '') || ':' ||
coalesce(to_char(amount, 'FM999999990.00'), '') as row_key
from invoices
) s;Failure modes
- Comparing raw strings where the two systems format numbers or dates differently.
- Ignoring attachments because they are stored elsewhere.
- Reconciling a stale snapshot while the base keeps changing.
How it is verified
- All digests match on a frozen source snapshot.
- Zero orphan rows across every relation.
Questions this pattern answers
What is reconciling Airtable data before cutover?
Cutover is a decision, and a decision needs evidence. Reconciliation produces the evidence.
How do you implement reconciliation before cutover?
Compare row counts per table, and per relation for join tables. Checksum a normalised projection of each row, so formatting differences do not create false mismatches. Verify referential integrity: no orphan children, no dangling join rows. Sample high-value records and compare field by field, including attachments and long text. Re-run the whole reconciliation immediately before cutover, not once a week earlier.
How is reconciliation before cutover verified?
All digests match on a frozen source snapshot. Zero orphan rows across every relation.
What usually goes wrong with reconciliation before cutover?
Comparing raw strings where the two systems format numbers or dates differently. Ignoring attachments because they are stored elsewhere. Reconciling a stale snapshot while the base keeps changing.
Related patterns
Projects in this track
This page documents the method. Engagement scope and pricing live on TechTide AI.
Airtable Exit and Rescue at TechTide AI→© 2026 Alex Cinovoj · TechTide AI · Columbus, OH