Cross-cloud means multiple Salesforce clouds working together — Sales Cloud + Service Cloud + Marketing Cloud + others — providing a unified experience.
Common combinations:
- Sales + Service — same org. Shared Account/Contact; Opportunity for sales, Case for service. Most common combination.
- + Experience Cloud — adds external-facing portal for partners/customers.
- + Marketing Cloud Engagement — separate platform; integrated for B2C journeys.
- + Pardot/MCAE — same Salesforce platform; B2B marketing integrated.
- + CPQ/Revenue Cloud — quote-to-cash extensions of Sales.
- + Field Service — extends Service for mobile workforce.
- + Industries Cloud — pre-built vertical data model layered on top.
Architectural patterns:
1. Shared data model.
Account, Contact, Lead are shared across clouds — same record means same customer across Sales, Service, Marketing. Critical for unified customer view.
2. Cloud-specific objects.
Opportunity, Quote (Sales), Case, Knowledge (Service), Email Send (Marketing). Each cloud owns its specific objects.
3. Unified profile.
Each user has access to the clouds they need (multiple licenses or multi-cloud bundle license). Profile/permission set determines visibility.
4. Data flow:
- Marketing -> Sales: Lead handoff, MQL flagging, campaign attribution.
- Sales -> Service: closed-won customer information available for Service team.
- Service -> Sales: customer health, escalations affecting renewal.
- Sales -> Marketing: customer events triggering nurture.
- Service -> Marketing: post-resolution surveys, NPS triggering.
5. Reporting:
- Cross-cloud dashboards showing the full customer lifecycle.
- CRM Analytics unifies data from all clouds.
- Data Cloud for advanced cross-system unification.
Sharing model:
Different clouds may need different sharing. Service agents see all cases regardless of region; sales reps see only their region's opportunities. Configure per cloud.
Common pitfalls:
- Each cloud built in isolation — handoffs broken; users repeat work.
- Data model conflicts — Marketing wants one Lead structure; Sales wants another. Negotiate, don't fork.
- Performance — every additional cloud adds platform load. Tune progressively.
- Licensing complexity — figuring out the right mix of licenses for each user role.
- Adoption gaps — Marketing adopts heavily, Sales lightly; data flows asymmetrically.
Phasing strategy:
Sequential rollout typically:
- Phase 1: Sales Cloud — sales team operational.
- Phase 2: Service Cloud — service team operational.
- Phase 3: Marketing Cloud / Pardot — marketing automation live.
- Phase 4: Cross-cloud refinements — reporting, journey integration, AI.
Senior architect insight: the value of cross-cloud is the unified customer view. If each cloud is built without thinking about handoffs, you don't get that value.
Cross-cloud is more than the sum of individual clouds — it's a coherent customer experience strategy.