Salesforce Health Cloud to Nexus CRM: 8-Week Migration Playbook

ICG has migrated 50+ Indian clinics from Salesforce Health Cloud (and Salesforce Sales Cloud + Service Cloud configured for healthcare) to Nexus CRM since 2022. Migration is the most-asked engagement after net-new Nexus implementations.

This article covers the data-tested 8-week migration playbook: data export, schema mapping, workflow re-implementation, DPDP audit-trail preservation, telecaller re-training, and the post-migration governance period.

Why clinics migrate from Salesforce Health Cloud to Nexus

The migration decision usually crystallises after one of these triggers:

1. Annual Salesforce renewal hits ₹2-8L/month. Most Indian clinics signed Salesforce 3-5 years ago when it was the only "enterprise-grade" CRM in healthcare. As usage scaled (more users, more storage, more integrations), the bill compounded. Renewal-time review surfaces the cost.

2. Integration backlog crosses 6 months. Every healthcare-specific change (new specialty workflow, new telecaller scorecard, new Meta CAPI integration) requires a Salesforce admin or integrator. Backlogs compound. Business velocity slows.

3. DPDP Act 2023 compliance gap appears. Salesforce Health Cloud requires custom configuration for DPDP — audit trails, consent versioning, right-to-erasure workflows. Most Indian clinics discovered the gap in 2024-25 when DPDP enforcement began.

4. Healthcare-specific data model frustration. Salesforce's generic Account + Opportunity model doesn't map well to "lead → consultation → treatment package → cycle". Workarounds work but they're brittle.

5. WhatsApp Business API integration limitations. Salesforce's WhatsApp connectors are not native, and the 60-second response architecture (Lead Conversion AI) requires significant custom build.

The 8-week migration playbook

Week 1: Discovery + Architecture

• Salesforce object inventory: every custom object, field, validation rule, workflow, process, flow, trigger, Apex class
• User audit: active users + their permissions + their actual usage patterns from Salesforce login history
• Integration audit: every connector (Meta CAPI, Google Ads, WhatsApp, IVR, EMR, billing, Phoenix)
• DPDP audit: where is patient data stored, who has accessed it, what consents exist
• Output: Migration Architecture Document. Signed off by clinic management before week 2.

Week 2: Data Export

• Salesforce Data Loader exports for every object: leads, contacts, accounts, opportunities, cases, custom objects, attachments, notes
• Audit trail export: every Salesforce field history record (this preserves DPDP-relevant access logs)
• Integration disconnection plan: maintain dual-write for safety until cutover
• Output: full Salesforce data dump (CSV + binary attachments), audit trail JSON file, DPDP compliance attestation

Week 3: Schema Mapping

• Map every Salesforce object → Nexus CRM specialty-templated object
• Field-by-field mapping (Salesforce custom fields → Nexus specialty-specific fields)
• Validation rule re-implementation in Nexus
• Workflow + process + flow → Nexus telecaller workflow + automation
• Output: Schema Mapping Document. Sample data round-trip test (export 100 records, import to Nexus, validate field integrity).

Week 4: Nexus Configuration

• Specialty templates activated (IVF / dental / derm / ortho / hospital OPD as relevant)
• Telecaller console configured with daily call-list + BI scorecards
• Meta CAPI + GCLID integration via Beacon
• WhatsApp Business API setup with 4-bot patient lifecycle
• DPDP compliance verified: AES-256, RBAC, audit trail, consent versioning, right-to-erasure
• Output: Nexus instance ready. Test users provisioned.

Week 5: Full Data Load + Validation

• Full data import to Nexus (all leads, contacts, accounts, treatment packages, audit history)
• Field-level validation: every record's data matches Salesforce source
• Audit trail preservation: every Salesforce field-history entry is preserved in Nexus audit log (DPDP requirement)
• Patient consent migration: all timestamped consent versions carried over
• Output: Data Validation Report. Sign-off by clinic management.

Week 6: Parallel Run

• Both Salesforce and Nexus operational. New leads write to BOTH systems.
• Telecaller team trains on Nexus while still using Salesforce for production work
• Daily comparison: Salesforce vs Nexus for new leads added that day
• Bug fixes + workflow refinements
• Output: Telecaller team confident on Nexus. Daily comparison showing parity.

Week 7: Cutover Preparation

• Final data sync (incremental — only changes since week 5 full load)
• All telecaller workflows switched to Nexus-only
• Salesforce moved to read-only mode (no new data, view-only for compliance)
• Marketing campaigns + WhatsApp lifecycle live on Nexus + Beacon
• Output: Salesforce read-only. Nexus production-live.

Week 8: Go-Live + Stabilisation

• All new leads + telecaller workflow + reporting on Nexus
• Beacon attribution, Hawk CRM intelligence, Phoenix revenue intelligence wired up
• Final compliance audit: DPDP attestation, data localisation, breach notification setup
• Salesforce shutdown plan: 6-month read-only retention for compliance, then archive
• Output: Migration complete. CAP training plan active for next 90 days.

What the migration delivers

Median outcomes from ICG's 50+ Salesforce → Nexus migrations:

angryturtle/18-change-history.png" alt="Angryturtle Change History — timestamped audit trail of every edit made to the listing, by whom, and prior value" loading="lazy" decoding="async" style="width:100%;height:auto;display:block;">

• Total cost of ownership reduction: 40-60% (from ₹3-8L/month Salesforce + integrator to ₹1-3L/month Nexus + ICG)
• Implementation velocity: 4-8 weeks (Nexus) vs 4-9 months (Salesforce custom build for any new specialty workflow)
• CPQL improvement: 38-58% in first 90 days post-migration (driven by Beacon CAPI, specialty templates, Hawk intelligence)
• DPDP compliance: automatic by architecture (no separate compliance officer needed)
• Telecaller productivity: 40-80% improvement (driven by Nexus daily call-list + BI scorecards + CAP training)

The Salesforce vs Nexus decision matrix

Choose Salesforce Health Cloud (over Nexus) when:

• Hospital network with global presence needing tight integration with non-Indian systems
• Have ₹35-50L + 4-9 months for customisation
• 5+ Salesforce administrators in-house
• Priority is corporate-wide single-customer-view across non-healthcare lines

Choose Nexus CRM (over Salesforce) when:

• Speed-to-value matters (4-8 weeks vs 9 months)
• DPDP compliance must be automatic, not custom
• Healthcare-specific workflows are needed (treatment packages, telecaller cadences, qualification gates)
• Budget is ₹50K-3L/month rather than ₹3L+/month for Salesforce + integrator
• WhatsApp Business API + Meta CAPI native is non-negotiable

Related reads

• Healthcare CRM Agency India — full migration + implementation engagement
• Nexus CRM — destination platform
• Best Healthcare CRM India 2026 — 12-platform comparison

Seven mistakes that stall a Salesforce Health Cloud to Nexus migration

Across 50+ Indian clinic migrations, the same avoidable errors surface. Fix these before Week 1 and you cut cutover risk by roughly two-thirds.

1. Treating it as an IT project, not an operations project. The front-desk, tele-callers, and clinical coordinators use the CRM 100+ times a day. If they aren't in the mapping workshop, adoption collapses in Week 3.
2. Exporting objects instead of journeys. Teams dump Accounts, Contacts, and Leads as flat CSVs and lose the appointment-to-consult-to-package journey that Nexus rebuilds automatically.
3. Skipping the DPDP audit before migration. The 2023 Digital Personal Data Protection Act now applies to every Indian clinic. Migrating without a consent-artifact map means importing non-compliant records into a new system.
4. No parallel-run window. Cutting over on a Friday night with no dual-write period is how clinics lose two weeks of appointments. A 5-7 day parallel run is non-negotiable.
5. Ignoring WhatsApp and IVR integrations. Most Salesforce Health Cloud deployments in India bolted WhatsApp Business API and cloud-telephony on top. These break silently at cutover if the number-mapping isn't rebuilt.
6. Under-scoping training. Two hours of Zoom training does not replace muscle memory. Budget 8-12 hours of role-specific hands-on per user across two weeks.
7. No rollback plan. If something breaks in Week 9, you need a documented 24-hour rollback path back to Salesforce. Most teams don't write one.

The correction pattern is the same one we use across our Client Elevation Programme engagements: sequence the migration by revenue-critical journey (new-lead intake first, follow-up second, package renewals third), and give the marketing stack (Meta Catalyst IQ, Prism Pulse) read-access on Day 1 so attribution never breaks. For groups running paid-media alongside migration, Prism Spy keeps competitor-intel flowing while your team focuses on cutover.

If you're weighing a migration in the next two quarters, WhatsApp Rohit for a 30-minute audit against this seven-point checklist before you sign anything.