Migrate from Phreesia to Microsoft Dynamics 365 Sales

Phreesia patient records map directly to Dynamics 365 Contact entities. First name, last name, email, phone, address, and date of birth transfer as standard Contact fields. If a patient record includes an employer or organization link in Phreesia, that relationship routes to an Account record with the Contact linked via AccountId.

Phreesia patient records may include an employer or affiliated healthcare organization. When present, this organization maps to a Dynamics 365 Account record. The Account stores organization name, address, and domain. If no employer is stored, patients without organizations attach to a default 'Individual Patients' Account record.

Phreesia stores insurance carrier name, plan name, member ID, group number, subscriber name, and eligibility status. Dynamics 365 Sales has no native insurance structure. We create custom text fields on both Contact (Insurance_Member_ID__c, Insurance_Group__c) and Account (Insurance_Carrier__c, Insurance_Plan__c) to preserve the full insurance record.

Phreesia visit records include appointment timestamp, provider name, visit reason, and clinical notes. Dynamics 365 Sales has no native appointment entity for patient visits. We create a custom Dataverse table (Patient_Visit__c) with fields for visit date, provider, reason, and notes, linked to the Contact record via a lookup relationship.

Phreesia captures structured clinical screening responses (social determinants of health, risk assessments, patient-reported outcomes). These map to custom fields on Contact and a linked custom Screening entity in Dataverse. If the screening uses a pick-list or multi-select format in Phreesia, we apply value mapping to the Dynamics custom pick-list.

Phreesia digital consent records include consent type, signature timestamp, and the signed form document. We preserve the signed form as a Note attachment on the Contact record and create custom fields (Consent_Type__c, Consent_Completed_Date__c, Consent_Valid_Until__c) for structured tracking. The Note stores the actual PDF or image of the signed form.

Phreesia stores payment card type, last four digits, and billing address for card-on-file records. These map to custom encrypted text fields on Contact (Payment_Method_Type__c, Payment_Last_Four__c, Billing_Postal_Code__c). Full card numbers do not migrate due to PCI compliance—the last-four and type are sufficient for payment reconciliation in Dynamics.

Phreesia appointment reminder sequences (SMS, email, IVR reminders before a visit) have no direct equivalent in Dynamics 365 Sales. These automations must be rebuilt in Power Automate or Dynamics workflows using appointment date triggers from the Patient_Visit__c custom entity. We export the Phreesia workflow definitions as a configuration reference.

Phreesia's recall campaigns (follow-up reminders for preventive care, annual wellness visits, specialist referrals) do not migrate. Dynamics 365 Sales Playbooks or Power Automate flows can replicate this behavior using the Patient_Visit__c custom entity and Contact records as triggers. We provide a workflow export for your Power Platform team to rebuild.

Phreesia associates patients with their care team members (primary care provider, specialists, referring physicians). Dynamics 365 Sales stores person-to-person relationships using the native Contact relationships feature or a custom Patient_Provider_Junction__c entity. We map provider names to related Contact records and establish the relationship in Dynamics.

Phreesia tracks patient outstanding balances from time-of-service payments. This value migrates to a custom currency field (Outstanding_Balance__c) on the Contact record. Dynamics 365 Sales does not have a native patient billing object—your billing team reconciles this field against your PM or billing system post-migration.

Phreesia records how a patient was referred (self-referred, physician referral, insurance network, marketing campaign). We map this to a custom pick-list field (Referral_Source__c) on Contact. If the referral originates from a referring physician in your network, that physician becomes an Account or Contact record with a referral relationship established.

Phreesia runs real-time insurance eligibility verification and stores the result (active, inactive, coverage details). This migrates to custom fields on Contact (Eligibility_Status__c, Eligibility_Check_Date__c, Eligibility_Coverage_Details__c). The verification result is preserved for historical reference but does not affect Dynamics workflows. If your organization uses the eligibility data for reporting or segmentation, the fields can be included in Dynamics views and Power BI dashboards without additional configuration.

Phreesia tracks whether patients prefer SMS, email, or phone contact, and whether they've opted out of marketing communications. We map these preferences to custom fields on Contact (Preferred_Contact_Method__c, SMS_Opt_In__c, Marketing_Email_Opt_In__c) for compliance tracking in Dynamics. These fields enable your team to respect patient preferences during outreach and ensure that Dynamics marketing emails comply with opt‑out requests.