Migrate from Lifeline Suite to Microsoft Dynamics 365 Sales

Lifeline Suite patient records map to Dynamics 365 Contacts. The patient's primary organization (if any) becomes the Contact's AccountId lookup. Patient ID from Lifeline Suite is stored as a custom field (Original_Patient_ID__c) for traceability and delta-run de-duplication. During migration, we also preserve the original patient create date in a separate custom datetime field to maintain full historical context.

Lifeline Suite organizations map directly to Dynamics 365 Accounts. Facility address, phone, and type (hospital, clinic, lab) translate to Account fields. Multiple facilities can be created as separate Account records linked by a parent-account hierarchy if Lifeline Suite supports facility grouping.

If Lifeline Suite provider records include Active Directory-equivalent credentials, they may map to Dynamics 365 User records for owner assignment. Providers without system login map as Contacts with a custom Role field (Provider_Role__c) to distinguish them from patient contacts. This mapping ensures accurate ownership and audit trails.

Dynamics 365 Sales has no native clinical encounter object. We create a custom Encounter Dataverse table keyed by the patient Contact. Fields include Encounter_Date__c, Encounter_Type__c, Provider__c (lookup to Contact), Summary__c, and Diagnosis_Codes__c. Encounter records link back to the patient Contact via a lookup relationship. This custom table also supports future extensions such as attaching treatment notes or linking to external diagnostic reports via Power Automate.

Lifeline Suite appointments migrate as Dynamics 365 Appointments (activitypointer entity). Original scheduled time, provider, and location are preserved in appointment fields. Status mapping handles Cancelled vs Completed vs No-Show values from the source.

Billing records require a custom Dataverse table (Billing_Record__c) since Dynamics 365 Sales does not include billing as a native CRM object. The table includes Amount__c, Status__c, Payer_Name__c, Insurance_Plan__c, and Patient__c (lookup to Contact). Linked line items become child records or a multi-select text field depending on source complexity.

Insurance carrier data from Lifeline Suite merges into a custom Insurance_Carrier__c table with links to Account (the carrier) and Contact (the insured patient). Primary vs secondary coverage is stored as a custom pick-list field (Coverage_Tier__c) on the relationship. This structure allows reporting on payer mix and insurance utilization trends.

Any custom fields defined in Lifeline Suite for patient records (e.g., blood type, emergency contact, allergy flags) become Dataverse custom fields on the Contact entity. Type-aware mapping applies — date fields use datetime, pick-lists use option sets, and multi-select values use a custom multi-select option set.

Lifeline Suite custom encounter fields (e.g., vitals recorded, procedure codes, referral source) migrate to the custom Encounter Dataverse table as typed fields. ICD or CPT codes stored in encounter records map to a text field with the original code format preserved for reference.

Documents attached to patient records or encounters in Lifeline Suite re-upload to SharePoint (connected via Dynamics 365's native SharePoint integration) or as Note annotations on the relevant Contact or custom Encounter record. Original file names and timestamps are preserved. The migration process also maintains folder hierarchy where possible.

Lifeline Suite care plans have no direct Dynamics 365 equivalent. We create a custom Care_Plan__c Dataverse table linked to Contact (patient) and Encounter (associated visit). Plan goals, interventions, and status are stored as custom fields; automations must be rebuilt in Power Automate.

Referring physician data from Lifeline Suite becomes a Contact record with a custom Referral_Role__c pick-list (Referring Physician). The referral relationship is stored in a custom Referral__c table linking the referring Contact to the patient Contact, with referral date and reason fields.