Migrate from coreplus to Microsoft Dynamics 365 Sales

CorePlus clients map directly to Dynamics 365 Sales Contact records. Each CorePlus client is assigned a primary Account lookup in Dynamics 365 based on the client's associated organization name. Client create dates migrate as a custom datetime field since Dynamics CreatedDate reflects the migration run date.

CorePlus client organization names that represent businesses (rather than individuals) merge into Dynamics 365 Sales Account records. If a client has no organization name, they land only as a Contact without an Account lookup. FlitStack splits individual vs. organizational records during the mapping phase.

CorePlus practitioners who will use Dynamics 365 as CRM users are resolved by email match against Dynamics SystemUser records. Practitioners without a matching email are flagged before migration — your team either creates the Dynamics user first or assigns those practitioners as Contacts with a custom Practitioner_Role__c field.

CorePlus practitioners who are also referring providers and do not need Dynamics CRM user access map to Contact records with a custom Practitioner_Specialty__c field to preserve their professional designation. This prevents them from being treated as regular client contacts within the CRM.

CorePlus appointments map to the Dynamics 365 Sales Appointment entity with the original start time, end time, and subject preserved. The Appointment's Regarding lookup attaches to the client Contact record. Status reason maps from CorePlus appointment status to the corresponding Dynamics AppointmentStatus option-set value.

CorePlus appointment types flagged as 'Phone Call' or 'Telehealth' in the service-type configuration map to the Dynamics PhoneCall entity instead of Appointment. The phone call duration, direction (inbound/outbound), and subject are preserved from the CorePlus appointment record. For accurate reporting in the target system.

CorePlus invoices have no native equivalent in Dynamics 365 Sales — Dynamics handles billing through Business Central, not the Sales CRM. FlitStack creates a custom Invoice entity on the Dataverse to store CorePlus invoice number, total amount, status, issue date, and client lookup. Your team maps this to a Business Central invoice workflow post-migration.

CorePlus invoice line items (service descriptions, quantities, fees) migrate as rows in the custom Invoice Line Item entity, linked to the custom Invoice record via a lookup. Each line item includes the service type reference, unit price, and total from CorePlus.

CorePlus referrer records — typically referring physicians or provider organizations — map to Dynamics 365 Sales Account records with a custom Referrer_Type__c pick-list field set to 'Physician' or 'Organization'. The referral relationship to clients is preserved via a custom Client_Referrer_Junction__c entity connecting Contact to Account.

CorePlus service types with associated fees and stock levels migrate as a custom Service_Type__c entity on the Dataverse. Dynamics 365 Sales has no native service-type concept — this custom entity allows appointment-type reporting and invoice line-item population in the custom Invoice entity post-migration.

CorePlus client groups (used for report filtering and batch operations) migrate as a custom Client_Group__c entity. Each client Contact receives a lookup to its Client_Group__c record. This preserves segmentation logic that would otherwise require manual reassignment in Dynamics in your environment.

CorePlus draft notes attached to client records migrate as Dynamics Annotation records linked to the corresponding Contact. The annotation body and subject are preserved. Draft status is stored as a custom Draft_Note_Flag__c boolean since Dynamics does not have a draft concept for notes.