Zero-copy or full ingestion? A decision framework for Data Cloud
When to federate with Snowflake, Databricks or BigQuery, when to ingest, and how to model the FinOps consequences.
- Zero-copy is not free — you pay for query egress and warehouse compute per activation.
- Full ingestion is not evil — it wins when activation latency and downstream write-back matter.
- Most enterprises land on a hybrid: ingest identity + engagement, federate analytics + finance.
The three real options
1) Full ingestion into Data Cloud storage. 2) Zero-copy federation via Snowflake / Databricks / BigQuery / Redshift shares. 3) Hybrid — ingest hot, federate cold.
Each has a distinct cost curve. Ingestion is priced on storage + credits consumed on transform. Zero-copy shifts cost to your warehouse bill via cross-platform query compute.
The decision axes
Activation latency (Marketing Cloud / Agentforce need sub-second lookups), write-back requirements, data gravity (where is the source of truth?), and regulatory residency. Score each workload on these four and the answer usually falls out.
The FinOps mistake we see most often
Teams pick zero-copy for 'cost savings' then activate a 20M-row segment nightly against a federated table — and blow the Snowflake bill. If the segment is activated more than daily, ingest it.
How to make this specific, measurable and shipped.
A concrete goal shape for turning this insight into a board-defensible programme.
Build a per-workload federation-vs-ingestion decision tree for the top 20 data sources feeding Data Cloud.
Data Cloud credit spend, warehouse compute $, activation latency P95, model refresh SLA.
Baseline current spend in weeks 1–2, model 3 scenarios in weeks 3–4, migrate in a phased 90-day plan.
Directly reduces cloud spend variance — a top-3 CFO concern in every 2026 IT review.
Decision framework signed off in 4 weeks; first optimisation wave live in 12 weeks.
Put numbers on it.
An interactive model calibrated to the shape of programmes we run. Tune the inputs to your reality — the outputs recompute instantly.
Data Cloud zero-copy vs ingestion TCO
Compare 12-month cost of federating vs ingesting a workload into Data Cloud.
- 1M rows ≈ 1GB after Data Cloud compression (varies with column count).
- Warehouse cost per query is an average across activation shapes.
- Excludes engineering FTE cost — typically favours ingestion at scale.
- 01Zero-copy is a pricing model, not a free lunch.
- 02Activation frequency is the single strongest predictor of the right choice.
- 03Model FinOps before architecture — not after go-live.
Pressure-test this against your org.
A Principal Architect will validate the assumptions, pull in your baselines and turn this into a defensible business case.
Book a working sessionAgentforce vs Copilots: what enterprises actually need in 2026
Copilots suggest; agents act. A field guide to picking reasoning-first agents for service, sales and RevOps — and where copilots still win.
Read →CPQ+ to Revenue Lifecycle Management: a pragmatic migration path
The legacy CPQ+ and Billing footprint isn't going away tomorrow — here's how to phase RLM without breaking quote-to-cash.
Read →Should you move from MC Engagement to Marketing Cloud Growth?
Data Cloud-native Marketing Cloud is the future — but only some orgs are ready today. A checklist for the migration decision.
Read →