How to Integrate Salesforce Data Cloud With Snowflake in 5 Minutes (Zero-Copy Guide)
Need Snowflake data available in Salesforce without copying it into another repository? Zero-copy data federation lets Salesforce Data Cloud, now called Data 360 in current Salesforce documentation, query data in Snowflake on demand.
This guide walks through the Snowflake → Data Cloud direction: connect Snowflake, create a federated data stream, and keep acceleration off for zero-copy access. The five-minute setup is realistic only when your credentials, permissions, network access, and target data are ready beforehand. Production preparation can take longer.
Important: This is not the same as sharing Salesforce data out to Snowflake. If you want Snowflake to access Data Cloud data products, that’s a different setup. See Salesforce’s Snowflake data federation guide for this walkthrough’s direction.
What zero-copy federation does, and doesn’t do
With acceleration disabled, Data Cloud queries the selected Snowflake data when a supported Data Cloud feature requests it. The records remain in Snowflake rather than being persistently ingested into Data Cloud. This can reduce duplication and keep access close to the source.
Zero-copy does not mean zero cost or zero planning. Salesforce notes that federation usage is based on rows accessed by external queries. Query frequency, data volume, and the way you use the federated data all matter. Review Salesforce’s credit consumption guidance before rolling out a high-volume use case.
Before the five-minute setup: prepare access
Ask your Salesforce and Snowflake administrators to confirm these items first:
- Salesforce access: A System Administrator or Data Cloud Architect can create the connection; a Data Cloud Architect can create the data stream.
- Snowflake access: A dedicated service identity and role have the necessary usage and read permissions for the chosen warehouse, database, schema, and tables.
- Network access: Snowflake’s network policy allows the relevant Data Cloud IP addresses. Check Salesforce’s IP allowlist guidance.
- Authentication: Your team has chosen private-key authentication or Salesforce IDP authentication (OIDC), and the required credentials are ready.
- A focused first use case: Identify the tables and fields needed for one workflow, not the whole warehouse.
Use a dedicated identity and least-privilege access. Don’t reuse a human’s account or grant broad access simply to get through setup faster. Salesforce’s connection instructions describe authentication options and the access requirements.
Connect Salesforce Data Cloud to Snowflake in five steps
The exact labels can vary by org version and configuration. Use the current Salesforce setup guide if your screen differs.
1. Create the Snowflake connection
In Salesforce, open Data Cloud Setup and select Snowflake under External Integrations. Click New, then enter a connection name and API name.
Choose your approved authentication method. For private-key authentication, supply the Snowflake credentials and key as prompted; follow Salesforce’s instructions about key formatting and passphrases. For Salesforce IDP authentication, enable the option and copy the generated external ID. Keep the connection window open while your Snowflake administrator configures the corresponding OIDC service identity: the external ID is unique to the connection.
Enter your Snowflake account URL, continue, select an authorized warehouse, and save. Verify the connection is active before moving on.
2. Start a Snowflake data stream
Open Data Streams in Data Cloud and click New. Choose Snowflake as the source, then select the connection you just created.
3. Choose the source data
Select the Snowflake database and the specific table or tables needed for your use case. Choose the appropriate data category and select a unique primary key for each object. You can also select a record-modified field if your configuration requires it.
Select only the necessary fields. Check that the field types are supported, and assign the stream to the appropriate Data Space.
4. Keep acceleration disabled
At the acceleration step, clear “Enable acceleration.” This setting is essential: Salesforce documents that enabling acceleration caches data by batch-ingesting it into a Data Lake Object on a schedule. Leaving acceleration disabled keeps the stream federated, with queries made against Snowflake when needed.
5. Deploy and validate
Click Deploy, then validate access using a suitable Data Cloud feature, such as Data Explorer or another supported query experience. Confirm that the expected fields are available and that the intended use case behaves correctly. If you need to use the data in segments or calculated insights, follow the relevant data-model mapping steps for your use case.
For Salesforce’s detailed screens and field-by-field sequence, see Create a Snowflake Data Stream.
Production checks before expanding access
A successful connection is the start, not the finish. Confirm the following before making the integration a dependency for business-critical workflows:
- Data quality: Are the selected fields complete, consistent, and understood by the Salesforce users who will rely on them?
- Access boundaries: Does the service identity see only the intended Snowflake objects? Are Data Cloud permissions aligned with your data policies?
- Cost and query behavior: Which processes will query the federated data, how often will they run, and how will your team monitor rows accessed?
- Performance expectations: Does the live query pattern meet your users’ needs? If you need reduced latency and accept scheduled caching, evaluate acceleration deliberately: it changes the data-access model.
- Operational ownership: Who handles credential rotation, permission changes, troubleshooting, and future schema updates?
Common setup snags
The connection can’t see the warehouse. Ask your Snowflake administrator to verify that the service role has access to the selected warehouse, database, schema, and tables.
Authentication fails. Recheck the account URL and the authentication configuration. For Salesforce IDP authentication, confirm that the OIDC service identity uses the external ID generated by the connection you’re configuring. Don’t close the Salesforce setup window before the Snowflake-side configuration is complete.
The data stream is slower than expected. Review the query pattern, source data volume, permissions, and warehouse configuration. Consider whether live federation fits the use case or whether an explicitly configured cache is more appropriate.
The data appears copied. Check the data stream settings. If acceleration is enabled, Salesforce describes that behavior as caching through batch ingestion, not zero-copy federation.
Make the integration useful, not just connected
Zero-copy can help growing businesses make Snowflake data available in Salesforce without building a second persistent copy in Data Cloud. But business value depends on the foundation: clean fields, clear ownership, sound access controls, and an integration designed for the workflows that matter.
NextEd Consulting helps Salesforce-dependent businesses strengthen those foundations through data management and analytics, Salesforce implementation, and ongoing technical support. When the integration is complex or your internal team needs extra capacity, our staff augmentation services can connect you with pre-screened Salesforce specialists.
👉 Need expert support to scope or deliver a Snowflake integration? Explore our Salesforce consulting services or get in touch with NextEd Consulting to discuss the right next step.