FIG. 02 What actually moves

Every platform in the building quotes a data programme before a single agent does real work. Here is the same table under both approaches, and the thing each one needs to take away from it.

the sourcecrm.accounts4.1M rowson-prem

columntypesamplenote
account_idvarcharACC-8841 
legal_namevarcharMeridian Foods Pvt Ltdcustomer data
tiervarcharT1 
owner_emailvarcharr.iyer@meridian.inpersonal data

+ 34 more columns

the usual precondition

Move it first

Warehouse, lakehouse or a vendor tenancy. The agents come after.

what has to travel

rows 4,100,000
columns 38 of 38
incl. every name, email and contract value
a programme
not a sprint
their tenancy
your operational data, on their side of the line

SynOS

Profile it where it sits

Installed inside your own infrastructure. Rows are queried live at answer time.

what has to travel

rows 0
held null rate · distinct counts · length bounds · value samples
column roles and metric bindings, not contents
first workflow
in weeks
your own infrastructure
nothing migrated, nothing replaced, nothing left the building

Data residency, cost and freshness are the same design decision, taken once. The legacy estate stops being the blocker.