Tech Talk

Data Cloud provisioning strategy is one of the key aspects of the Data Cloud project which can make the project implementation super easy or just opposite.

There are two ways a Data Cloud can be provisioned

1. Data Cloud as a part of the existing Salesforce Org.
2. Data Cloud is in the completely separate box, dedicated only for Data Cloud.

What is Existing Core Data Org?

• Data Cloud is a part of the existing sandbox (Sales, Service etc.) and it is added as an app in the Org.
• Data Cloud Admin Requires System Admin profile.
• Data Cloud Admin gains access to Data Cloud using permission set.

Why Use this Data Cloud provisioning strategy?

1. Customer has single line of business.
2. All customer data (Except data inside DLO) is housed in a single Org.
3. Need custom development (LWC, APEX) to create Dashboard and other components.
4. Sales, Service or other traditional clouds need data from Data Cloud.

Consider Below facts before proceeding to the provisioning in the Same org

1. Data Cloud can be only provisioned in the Production Org. Although other Clouds can be migrated through separate sandboxes during different lifecycle of the project, Data Cloud will be only be in the Production. So, separate connection is required between Data Cloud production and UAT, QAT sandboxes.  
2. Identity resolution jobs will produce test data and Production data and they will reside along side in the Identifier DMO. Either Data Space or an attribute can be leveraged to distinguish between Test and Production Data.
3. Code Migration is easy as all are in the same sandbox however Prod and Non-Prod data needs to be separated via Data Space or attributes. 

New Data Cloud Org Provisioning Strategy

• Data Cloud is provisioned to Separate Org Entirely.  Sometimes it is called as “Home Org”.
• Most of the customer is currently using this method.

Why Use this Data Cloud Implementation strategy

1. Multiple Business Units.
2. Highly Complex enterprise architecture exists.
3. Regulated industry which requires certain Data security.
4. Data residency is in Question.
5. There are already a lot of customizations in the current Org.
6. Data Cloud Admin and System Admin should not able to access each other app.

Consider Below facts before proceeding to the provisioning in the separate org

1. Data Kits can be leveraged to migrate some of the components.
2. As of now No Data Cloud Sand Box exist. Although it’s in the near future roadmap and coming soon.

Conclusion

Both of the strategies have advantages and disadvantages however, with new Data Cloud sandbox Salesforce is moving towards different sandbox strategy. So, going forward we can see a lot of new features in that area.