Get Started with Data Cloud One
Learning Objectives
After completing this unit, you’ll be able to:
- Identify different possible Data Cloud One org architectures.
- Understand the first steps to setting up Data Cloud One.
Plan Data Cloud Architecture Strategy
As you review Data Cloud One, start by walking through some considerations and scenarios. Depending on what your current org architecture is, you might have a different set up process. To reduce any downstream issues, first identify your home org and companion org before setting up Data Cloud One.
Here are three possible scenarios your company might be working with. All three cases assume that you don’t have data residency concerns to work around, or that all orgs are already provisioned in the same geographical region.
Scenario 1: Multiple Orgs Without Data Cloud
If your company doesn’t have Data Cloud on any org yet, you can choose whichever org you’d like to be the Data Cloud home org and whichever org(s) you’d like to be the companion org(s).
Scenario 2: Multiple Orgs but Only One Org with Data Cloud
If you have Data Cloud provisioned on one org, then that org can serve as the home org. Orgs without Data Cloud can be connected as companion orgs.
For example, Northern Trail Outfitter’s Sales org has Data Cloud, while its Marketing and Customer Service orgs don’t. NTO designates the Sales org with Data Cloud to be the home org and designates the orgs without Data Cloud to be companion orgs.
Scenario 3: Multiple Orgs with Data Cloud
If you have multiple orgs with Data Cloud, you can choose one org to become the home org, and designate the rest as companion orgs. You can keep Data Cloud on your designated home org, and convert the other orgs to companion orgs by deprovisioning Data Cloud.
For example, NTO’s Operations, Materials Research, and Sporting Goods Retail orgs all have Data Cloud on them, but NTO only wants one Data Cloud home org. NTO chooses one of its orgs, the Operations org, to be its Data Cloud home org. That org maintains its Data Cloud license. For the rest of its orgs, NTO can deprovision Data Cloud so that those orgs can become companion orgs.
Because deprovisioning requires the org data and metadata to be deleted, NTO moves the data into its Data Cloud home org and use a data kit to move the metadata as well. NTO also carefully evaluates any features that are dependent on that Data Cloud instance, and works to connect those features to its new home org instead.
Best Practices and Considerations
Keep these best practices in mind when considering Data Cloud One.
-
Data Residency: Consult your legal department before connecting orgs across different regions. All data in companion orgs becomes resident in the region of the home org, which could create data residency issues.
-
Growth: Confirm that your long-term growth objectives support the decision to implement a single Data Cloud instance.
-
Architecture: Assess whether all orgs require complete control over their data and Data Cloud configurations. If so, creating multiple Data Cloud orgs is advisable. However, if you want to centralize control across orgs and minimize data silos, connect multiple orgs to a single Data Cloud.
-
Companion Connections: Every home org has a maximum number of free companion-connected orgs it can have. If they reach the maximum, you might want to add Additional Connection licenses to the home org to extend their maximum.
-
Deprovisioning: Deprovisioning Data Cloud, or converting a Data Cloud home org to a companion org, can take months, and can lead to data loss or service disruption. Contact Salesforce Customer Support for timeline information. For more information, see Convert a Data Cloud Home Org to a Data Cloud One Companion Org in Salesforce Help.
Set Up Data Cloud One
Now that you thought about your Data Cloud architecture strategy and identified a home org and companion orgs, you’re ready to set up Data Cloud One.
Here are the steps the Northern Trail Outfitters admin performs to set up Data Cloud One.
- Add the free Data Cloud One Companion Org SKU to each of the companion orgs.
- Connect the companion orgs to the home org.
- From the home org, share data spaces to the companion orgs.
- In the companion org, grant users access to Data Cloud One based on data compliance and governance needs.
The Data Cloud One app appears in NTO’s companion orgs as soon as the companion connection is active and the initial metadata sync is completed. Users in companion orgs can now access data from the Data Cloud home org and build insights, segments, and prompts with ease.
How It All Works Together
Now, see how all these parts work together with NTO.
Before using Data Cloud One, NTO has one org with Data Cloud, its single source of truth. NTO connects its Data Cloud org to all of its other Salesforce orgs, including its Customer Service org and Sporting Goods Retail org, through standard Salesforce CRM connections.
When NTO decides to adopt Data Cloud One, NTO sets up companion connections from the Data Cloud home org to its other Salesforce orgs, which makes these orgs companion orgs. Admins on the Data Cloud home org can partition its data into data spaces and choose which data spaces to share with each of the companion orgs. Now, users of the companion orgs can use the Data Cloud One app to work in their own data spaces, creating their own segments, insights, and activations, and still access cross-org insights. All with only one Data Cloud.
Now that NTO’s users can access data from a shared source of truth, it’s so much easier to manage all of its different orgs. NTO’s salespeople can create insights and segments about their leads without messing with the data from Customer Service. And Marketing and Sporting Goods Retail can access cross-org analytics about the same unified customer profiles while creating their own data actions and agent prompts. NTO can even use Agentforce features like Audit Trail and Feedback Logging in its companion orgs.
Just like NTO, with Data Cloud One, you can save time, money, and headaches by optimizing performance and data usage across your orgs.