Salesforce Data Cloud is becoming central to data management and Agentforce deployments. Essentials streamlines this by using the multiple Salesforce APIs to move Data Cloud assets across environments and version control. Teams can easily select, validate, and deploy components or commit them to CI/CD workflows, reducing errors and improving governance.
Before Deploying Data Cloud
Salesforce Permissions Required
To ensure Data Cloud components appear in Essentials, make sure the user authorizing the org connection has the Data Cloud Architect permission assigned in Salesforce.
Without this permission, Essentials will not be able to retrieve Data Model Objects or Data Lake Objects.
Map Data Lake Object (DLO) and Data Model Object (DMO)
The Salesforce API currently returns only mapped DMOs and DLOs. To have these appear in Essentials, please ensure the necessary mappings are completed first within Salesforce.
Deploying Data Cloud
Which Data Cloud metadata types are supported, and where can you find them?
The table below outlines the Data Cloud–related metadata types supported by Essentials. Please note that Data Model Object and Data Model Field appear in Essentials under Custom Object and Custom Field.
Essentials Component Type | Data cloud concept | API name |
Activation platform | Activation platform | |
Data Stream Template | Data kits | |
Data Source Bundle Definition | Data kits | |
Data Package Kit Definition | Data kits | |
Data Package Kit Object | Data kits | |
Streaming App Data Connector | Data connectors, Data streams | |
Mkt Data Tran Object | Data connectors, Data streams | |
External Data Source | Data connectors, Data streams | |
External Data Connector | Data connectors, Data streams | |
External Data Tran Object | Data connectors, Data streams | |
Data Stream Definition | Data connectors, Data streams | |
Data Stream Template | Data connectors, Data streams | |
Data Source Object | Data connectors, Data Lake Object | |
Data Source | Data connectors, Data Lake | |
Object Source Target Map | Relationships | |
Field Src Trgt Relationship | Relationships | |
Data Src Data Model Field Map | Relationships | |
Data Connector Ingest Api | Ingest API data stream | |
Calculated Insight Definition | Calculated insights | |
Data Calculated Insight Template | Calculated insights | |
Market Segment Definition | Segments | |
Data Connector S3 | S3 data stream | |
Internal Data Connector | Internal Use | |
Data Kit Object Template | Data Object | |
Data Kit Object Dependency | Data Object | |
Custom Object | Data Model Object | |
Custom Fields | Data Model Field | |
Customer Data Platform Settings | Settings |
To help users easily find Data Cloud–related components, we’ve added a new filter. Use this filter to quickly view all Data Cloud components in one place.
 Data cloud component filter. |
In addition, you can use a Data Kit to deploy a package kit definition from one org to another. A Data Kit allows you to bundle and deploy multiple types of components together in a single package, making it easier to manage configurations and maintain consistency across environments. You can learn more in this article Deploy Data Kit
Dependency Support
We have added dependency support for a number of Data Cloud components, making it easier to identify related items. For example, to view all dependencies for a Data Kit, simply expand the [+] icon next to it and select “Select all dependencies", like so.
 Data kit dependencies |
Dependency support is currently available for a limited set of Data Cloud components, with more to come. We’ll continue expanding coverage in upcoming releases to include the most commonly used components.