What 2 scenarios would you recommend when provisioning Data Cloud in an existing CRM Data org?

• A. Existing CRM Data Org has been highly customized
• B. Customer data is housed in a single Salesforce Org
• C. Customer is using Loyalty Management and Promotions
• D. Customer has a need to connect multiple CRM Orgs

Answer: (B)

Starting with a single Salesforce Org containing all customer data makes provisioning Data Cloud straightforward and fastest to value. When all data sits in one source, you can map the standard CRM objects cleanly, apply identity resolution once, and build a unified customer profile without wrestling with cross-org reconciliation. Governance, security, and data quality processes are easier to implement because there’s one set of rules and one data model to enforce. This setup avoids the extra complexity of harmonizing custom fields, objects, and data quality across multiple sources, and it keeps the initial sweep of data integration predictable.

If the CRM is highly customized, onboarding becomes more intricate due to bespoke objects and fields needing careful mapping and transformation. If there’s a need to connect multiple CRM Orgs, you’ll face cross-org data orchestration, more complex identity matching, and broader governance considerations, which slows time to value. Loyalty Management or Promotions data is valuable, but it doesn’t address provisioning challenges by itself—the simplest, most reliable starting point is a single, unified Salesforce Org.