Every extract, staging table and sandbox in a healthcare migration holds regulated data, so safeguards start before the first file leaves the old system.
Healthcare and life sciences migrations split into two broad patterns. Provider organizations move patient engagement, referral and contact center data out of older CRMs and spreadsheets while the EHR stays the clinical record. Life sciences companies move healthcare professional, account and field interaction data, often from a legacy commercial CRM, while keeping medical and safety systems separate. In both cases we decide field by field what protected or regulated information needs to be in Salesforce, confirm the agreements and controls that permit it, and load through encrypted, access-limited channels with every step documented.
The difference in healthcare is that the migration itself is a handling event for protected health information. Extract files, staging databases and test sandboxes all hold regulated data, so they need the same safeguards as production, and the business associate agreement has to be in place before the first extract. Minimum necessary rules push back on the habit of copying everything. Life sciences adds its own constraints: interactions with healthcare professionals, samples and medical inquiries may be subject to transparency reporting and pharmacovigilance procedures. Identity is also messy, with the same physician listed under several practice locations and the same patient under several medical record numbers across facilities.
Referral sources, intake requests and scheduling outcomes from legacy tools are loaded as records linked to patients and referring providers. Access teams see prior requests and outcomes after cutover, and outreach staff see which referral relationships generate volume, all without clinical notes being copied out of the EHR into a second system. Referral status codes are standardized so reports compare sources on the same terms.
Physicians and other practitioners appear with different spellings, specialties and addresses across source systems. We match on national provider identifiers where available, consolidate practice locations and affiliations, and keep a crosswalk of old IDs so historical interactions attach to the correct professional instead of splitting across duplicates. Deceased or retired practitioners are flagged so outreach and territory plans leave them out, and affiliations with health systems and group practices are carried as relationships rather than overwritten fields.
For life sciences teams, calls, meetings, sample drops and approved content usage come across from the legacy commercial CRM with dates and representatives retained. We check that transparency-relevant fields survive the mapping intact, since reports built later depend on them, and we exclude anything that belongs in the safety or medical information systems instead. Territory and alignment history is kept so incentive calculations can be checked.
Open and recent patient or customer service cases move with status, category and audit history, so representatives do not restart conversations. Older closed cases can be summarized or archived depending on retention policy, and any attachment containing clinical detail is reviewed by the privacy team before it is included in a load. Queue and ownership mappings are tested so reopened cases route correctly.
We start with privacy and compliance leads alongside the business owner, before any data leaves a source system. Together we classify fields, confirm agreements and set where extracts may live. Test loads use masked or synthetic records wherever a sandbox lacks production-grade controls. Identity matching for patients or professionals is reviewed by the team that owns the master record. Loads run in stages, with open work first, and each stage is reconciled and signed off. Temporary files are destroyed on a documented schedule, and the legacy system is retired only after retention obligations are met.
Patient identifiers and appointment context are referenced, not duplicated. We migrate only the demographic and engagement fields approved for Salesforce and leave clinical documentation in the EHR.
Practitioner identifiers, specialties and affiliations from the directory drive matching, so migrated interactions and referrals attach to one clean professional record.
Adverse event reports and medical inquiries found in legacy CRM data are routed to the proper system and procedure rather than loaded as ordinary Salesforce activity.
Encryption, access logging, sandbox policies and agreements need to be ready before data moves, not after go-live. Salesforce Shield and related options can support that design, but your compliance team should confirm the approach meets HIPAA obligations for your organization.
Resist copying every column because it exists. Each regulated field should have a named business use in Salesforce. Fewer protected fields mean simpler access rules, smaller breach exposure and a quicker review by privacy staff before each phase goes live.
Old CRMs holding health data cannot simply be switched off. Retention requirements, legal holds and audit needs may call for a read-only archive for some time. Decide who owns that archive, how it is secured, and when its records are eventually destroyed.
Client names are anonymized.
Only if that sandbox has controls equal to production and your agreements cover it. Many organizations prefer masked or synthetic data for early test loads and a tightly controlled full copy for final validation. We plan that with your privacy officer, because the test environment is often where migration projects accidentally widen access to protected information.
Healthcare professional and account records, affiliations, call and meeting history, sample transactions and territory alignments usually move. We review which history supports future planning or reporting obligations, archive the rest, and confirm that consent and communication preferences from the old platform are honored in Salesforce from the first day reps log in. Call plans and target lists are rebuilt once alignments are confirmed.
Carefully, and with the organization's master patient index as the authority. Salesforce should not become a second place where patient identities are decided. We match to the enterprise identifier, flag conflicts for the health information management team, and avoid merges that the source systems themselves would not recognize or be able to reverse. The review list is worked jointly before each load.
No partner can certify compliance for you. We design and run the migration with safeguards that support your HIPAA program: encrypted transfers, least-privilege access, and documented handling of files and reconciliation records. Your compliance and legal teams decide whether the approach meets your obligations, and we give them the documentation they need to make that call.
One onshore team with 150 Salesforce certifications, a Salesforce Consulting Partner since 2017.
A monthly brief for the people who own Salesforce, AI and revenue technology
What changed in Salesforce and AI this month, and what to do about it.
One email a month. Written by the consultants who deliver the work, not by a marketing team, for the leaders who make the technology decisions.
Consultant analysis, not vendor recaps. One click to leave.