Migrate from Bp Premier to HighLevel

Bp Premier patient demographics (name, date of birth, gender, Medicare/DVA number, address, phone, email) map directly to HighLevel contact fields. Original Medicare/DVA numbers store as custom fields since HighLevel has no native health-insurance identifier field. Create dates and last-modified timestamps preserved as custom datetime fields.

Bp Premier practice and clinic records (clinic name, address, phone, fax, provider list) map to HighLevel companies. Multi-location practices create multiple company records linked to the primary contact. Practice management details (operating hours, referral preferences) store as custom fields in HighLevel.

Bp Premier provider records (doctor name, AHPRA registration, specialty, provider number) merge into HighLevel contacts with a custom role designation. Providers who are also billable clients get merged into the same contact record; non-client providers store with a 'Staff' tag in HighLevel. AHPRA registration numbers preserved as custom fields.

Bp Premier appointment records (date, time, duration, appointment type, provider, status) map to HighLevel tasks with original timestamps preserved. Appointment type (standard, long, procedure) stores as a task custom field. Status (booked, attended, missed, cancelled) maps to HighLevel task status values with a value-mapping table applied.

Bp Premier encounter records (date, provider, chief complaint, clinical notes, observations) require a HighLevel custom object named 'Clinical Encounter'. Each encounter links to the patient contact and provider contact via lookup relationships. Clinical note content stores as a long-text field in the custom object.

Bp Premier prescription records (drug name, dosage, frequency, prescriber, date) map to a HighLevel custom object linked to the patient contact. Drug name and dosage store as custom text fields. Bp Premier's PBS/RPBS coding requires custom field mapping since HighLevel has no pharmaceutical classification field.

Bp Premier pathology results (ordered test, result values, reference range, status, ordering provider) map to a HighLevel custom object. Result values store as custom text or number fields per test type. Critical/abnormal flags stored as custom pick-list values. No HighLevel native equivalent exists for pathology interpretation logic.

Bp Premier referral records (referring doctor, specialist, reason, date, status) map to HighLevel contact notes plus a referral-type custom field on the patient contact. Outgoing vs incoming referral distinction stored as a pick-list value. External specialist contact details stored as a secondary contact lookup.

Bp Premier recall records (recall type, due date, provider, status) map to HighLevel tasks with a due-date field and a custom 'Recall Type' field. Clinical recall reasons (cervical screen, diabetic review, etc.) stored as pick-list values. Recalls that were completed in Bp Premier marked as completed tasks in HighLevel.

Bp Premier invoice and billing records (amount, item codes, Medicare/DVA fee, patient payment, date) map to HighLevel opportunities. Invoice total maps to opportunity amount. Item-code descriptions stored as opportunity custom fields. Bp Premier's bulk-billing vs private-billing distinction maps to opportunity stage values via value mapping.

Bp Premier family and social history fields (smoking status, alcohol use, next of kin, emergency contact) map to custom fields on the HighLevel patient contact. These do not have native equivalents in HighLevel's standard contact schema and must be created as custom fields before migration.

Bp Premier immunisation records (vaccine type, date given, batch number, site, adverse reaction flag) map to a HighLevel custom object linked to the patient contact. Vaccine name stored as a custom pick-list. Adverse reaction flag stored as a custom boolean field. National Immunisation Register (NIR) status stored as a custom field.