Before the first sync
Confirm primary keys (or a stable surrogate). Decide TIMESTAMP WITH TIME ZONE policy. Map numeric precision. List tables that must never full-refresh in prod.
Incremental requirements
You need a reliable updated_at or equivalent watermark, monotonic enough for your lag SLA. Soft deletes need a status column or you will resurrect rows.
Warehouse side
Role with CREATE SCHEMA / TABLE as needed. Warehouse size for initial load vs steady state. Separate landing schema from marts so drift does not hit BI directly.
First-week monitors
Row-count delta vs source, null-rate on keys, lag vs watermark, and schema diff after every deploy. Pack waitlist: https://91crew.com/etl-pack.html
Related: ETL Pack · Schema evolution · Failure recovery