Migrate from coreplus to Salesforce Sales Cloud

CorePlus clients map directly to Salesforce Accounts. Client name becomes Account Name; the client's primary address maps to the Account billing address fields. Clients linked to multiple practitioners preserve those relationships as Account Contact Relations or a custom junction object.

Each CorePlus client record that has an individual contact (not a company entity) also creates a Salesforce Contact linked via AccountId. The primary contact per client gets the primary AccountId; additional contacts use Account Contact Relationships for N:N parity. If a client has multiple practitioners associated, we map each practitioner relationship as an Account Contact Relation entry, preserving referral and care-team links within Salesforce.

CorePlus practitioners have no native Salesforce equivalent. We map them to Contacts with a custom Practitioner_Role__c pick-list field set to 'Practitioner'. If your org needs to distinguish practitioner schedule data from standard contacts, a custom Practitioner__c object with a lookup to Contact is the cleaner schema.

When practitioner-specific fields (specialty, provider number, availability slots) are extensive, we recommend a custom Practitioner__c object. We migrate the practitioner record, create the custom object metadata, and link each Practitioner__c to its primary Contact record via a lookup field. The custom object also stores schedule templates, service types offered, and any certification or affiliation data, enabling downstream reporting on practitioner utilization.

CorePlus appointments map to Salesforce Tasks. The task Subject carries the appointment type; Start DateTime and End DateTime map to Task ActivityDate and custom datetime fields since Tasks store only a date, not a time range. Custom fields capture service type, practitioner link, and client link.

Appointments with a scheduled time-of-day are better modeled as Salesforce Events so start and end times are preserved. We map to Event with Subject = appointment type, StartDateTime and EndDateTime preserved, and custom WhoId (Contact) linking to the client contact record.

CorePlus invoices have no Salesforce standard object equivalent. We create a custom Invoice__c object with fields for invoice number, date, amount, status, and a lookup to the client Account. Line items map to a related Invoice_Line_Item__c custom object with product, quantity, and price fields.

CorePlus referrers are referral source entities — individual doctors or organizations who refer clients. We map referrers to Salesforce Accounts (marked with a custom Referrer_Type__c field) and create a custom Referrer_Client_Link__c junction object to preserve the many-to-many relationship between referrers and clients.

CorePlus service types define what services are offered, with associated fees and stock levels. These map to a custom Service_Type__c object with Name, Fee__c, and active/inactive status. The service type links to appointments via a lookup field on the Task or Event custom fields.

CorePlus practitioner availability slots have no Salesforce standard equivalent. We create a custom Availability_Slot__c object linked to the Practitioner Contact or Practitioner__c record, with start/end datetime, day-of-week, and active status fields. Note that Salesforce-calendar integration requires separate Flow or third-party tooling.

CorePlus draft notes attached to client records map to Salesforce Notes. The note title, body, and parent record link (client-to-Account lookup) are preserved. Notes created by practitioners carry the owner ID resolved by email match to the Salesforce user. If a note references an attachment, we migrate the attachment to Salesforce Files and link it to the parent Account or Contact record for complete context.

CorePlus users who created or own records are resolved by email address against Salesforce users. Unmatched owners are flagged before migration — either the Salesforce user is provisioned first or records are assigned to a designated fallback owner. No record lands without a valid OwnerId.