Migrate from Bp Premier to Microsoft Dynamics 365 Sales

BP Premier Patient is the primary record and maps to Dynamics 365 Account when the patient represents a household or organisation. The patient's full name splits into Account Name, and the BP Premier Patient ID is stored as a custom field (BP_Patient_ID__c) for traceability. Individual patients map to Contact records separately.

BP Premier Patient demographics (first name, last name, date of birth, gender, Medicare number, address) merge into a single Dynamics 365 Contact record. Medicare details and healthcare identifiers stored as custom fields since no native equivalent exists in Dynamics 365.

BP Premier practitioners (GPs, specialists, Allied Health providers) map to Dynamics 365 Contact records with a Provider_Type__c custom field identifying their role. Provider email addresses are used to match and resolve Dynamics 365 user records as owners for activities and accounts.

BP Premier appointment records have no direct Dynamics 365 equivalent — they map to a custom Activity entity (BP_Appointment__c) with fields for appointment start and end time (mapped from BP Premier's appt time and duration), status (mapped via value mapping from BP Premier status codes), and clinical reason (stored as a custom string field). The related patient resolves to the Account or Contact.

BP Premier billing transactions (bulk-bill claims, itemised invoices, Medicare transactions) map to Dynamics 365 Opportunity records — not an ideal fit since Opportunities represent sales pipelines rather than billing ledgers. Transaction amount and date map to Estimated Revenue and Close Date; the billing description becomes the Opportunity Name.

BP Premier clinical notes, reason for visit, and clinical findings have no equivalent in Dynamics 365 Sales. We migrate these as Dynamics 365 Note records attached to the Contact or Account, with the clinical date preserved in the Note's Created On timestamp. The original author (practitioner) resolves to a Dynamics 365 user.

BP Premier prescribing records store medication name, dosage, and instructions. Since Dynamics 365 Sales has no prescribing entity, medications are migrated as Note records with a custom BP_Medication__c text block containing the full prescription detail. Attachments such as prescribing PDFs are re-hosted as Dynamics 365 FileAttachments.

BP Premier file attachments on patient records (referral letters, imaging results, consent forms) are downloaded and re-uploaded to the Dynamics 365 SharePoint integration attached to the corresponding Account or Contact record. File size limits of 10MB per file apply. The original file names and folder structures are preserved where possible, and SharePoint permissions are mapped to Dynamics 365 security roles to maintain appropriate access controls across the organisation.

BP Premier practice-level settings and the practice organisation record map to a Dynamics 365 Account representing the clinic. Address, phone, and practice manager details migrate as standard Account fields. Additional practice metadata such as billing software configuration, operating hours, and clinic-specific flags are evaluated during discovery and stored as custom fields on the Account record where they add operational value for staff using the CRM.

Any custom properties configured by the practice on the BP Premier Patient record (such as insurance provider, health fund number, or custom clinical flags) are enumerated during discovery and created as Dynamics 365 custom fields on the Contact entity with the __c suffix. Value mapping applies where custom fields use pick-list values.

BP Premier appointment status codes (Booked, Confirmed, Attended, Did Not Attend, Cancelled, No Show, Rescheduled) are mapped value-by-value to custom status values on the BP_Appointment__c entity. The mapping table is delivered as part of the migration plan before the load runs, and any status codes that do not have a direct equivalent in the target pick-list are flagged for the practice administrator to confirm the appropriate target value before migration commences.

BP Premier recall and reminder功能 (patient recall for follow-up, health checks) has no direct Dynamics 365 Sales equivalent. We preserve recall records as custom fields on the Contact and export the recall schedule as a reference file; rebuilding the recall logic as Dynamics 365 workflows or Campaign members is a post-migration configuration step.