Migrate from Bp Premier to Salesforce Sales Cloud

Patient demographics (name, DOB, gender, contact details) map directly to Contact fields. The Bp Premier patient ID is stored as Source_Patient_ID__c on the Contact for traceability. Address fields map to MailingStreet, MailingCity, MailingState, MailingPostalCode, MailingCountry. Patients without a linked provider in Bp Premier land as Contacts without an Account association — your admin assigns a default Account or creates a 'Unassigned Patients' Account record.

Bp Premier providers (doctors, specialists, allied health) map to a combination of a Contact record (for practitioner name and AHPRA registration details) and a custom Provider__c object that stores provider type, specialty, provider number, and scheduling availability. This separates practitioner identity from patient-contact records and allows provider-level reporting in Salesforce.

Bp Premier appointments contain provider ID, patient ID, date/time, duration, service type, and status. These map to Salesforce Events with custom fields: Appointment_Status__c (custom pick-list matching Bp Premier statuses), Service_Type__c (custom text or pick-list), Provider_ID__c (lookup to Provider__c), and Duration_In_Minutes__c. The Event's WhoId links to the patient Contact record; the WhatId links to the patient's Account if a primary organization is defined.

Clinical notes (SOAP notes, consultation summaries, clinical observations) map to Salesforce ContentNote (Notes object) linked to the patient Contact via ContentDocumentLink. A custom Clinical_Note_Metadata__c field on the ContentNote stores visit type, SOAP format flag, and provider attribution. Bp Premier structured fields (BP reading, prescription list, lab results) are extracted as separate custom fields on the Contact rather than embedded in note text, preserving searchability and reporting on structured data.

Bp Premier records structured clinical observations (blood pressure, pulse, weight) as typed fields on the patient record. Salesforce has no native clinical observation object. FlitStack creates a custom Clinical_Observation__c object with fields: Patient__c (lookup to Contact), Observation_Type__c (custom pick-list), Observation_Value__c (text), Observation_Date__c (date), and Provider__c (lookup). Each BP reading becomes one record, enabling trend charting via Salesforce reporting.

Prescription records in Bp Premier (medication name, dosage, frequency, prescribing provider, date) have no Salesforce standard equivalent. FlitStack creates a Prescription__c custom object with fields mapped directly: Medication_Name__c, Dosage__c, Frequency__c, Prescribing_Provider__c (lookup to Provider__c), Prescription_Date__c, and Patient__c (lookup to Contact). Active vs. historical status preserved as Prescription_Status__c pick-list.

Lab results in Bp Premier include test name, result value, reference range, units, ordering provider, and date. Salesforce has no standard lab result object. FlitStack creates Lab_Result__c with fields: Test_Name__c, Result_Value__c, Reference_Range__c, Units__c, Ordering_Provider__c (lookup), Result_Date__c, and Patient__c (lookup to Contact). This structure supports Salesforce reporting on lab result trends per patient.

Bp Premier documents (referral letters, imaging files, consent forms) attached to patient records re-upload as Salesforce Files (ContentVersion + ContentDocumentLink). The ContentDocument's Title carries the original filename; a custom Original_File_Path__c field stores the Bp Premier storage location for reference. File size limits apply — Salesforce Files cap at 25MB per file by default. Files larger than 25MB are chunked or flagged for manual handling.

Bp Premier stores health fund name, membership number, and coverage details against the patient record. Salesforce has no standard health fund or insurance object. FlitStack creates a Health_Fund__c custom object with fields: Fund_Name__c, Membership_Number__c, Coverage_Type__c, and Patient__c (lookup to Contact). This supports reporting on insurance coverage distribution across the patient base in Salesforce.

Bp Premier's eHealth integrations — My Health Record access, NASH PKI certificate configuration, eRx Script Exchange — are platform-level connections with no Salesforce CRM equivalent. These must be re-established via third-party middleware or healthcare integration platforms (e.g., Mirth Connect, Telstra Health) after migration. FlitStack documents the current eHealth configuration as a rebuild reference for your IT or compliance team.