Migrate from Bp Premier to HubSpot

Bp Premier patient demographics including name, date of birth, address, phone number, Medicare card number, and Individual Healthcare Identifier (IHI) map directly to HubSpot contact properties. Clinical notes and prescription history do not have a native equivalent in HubSpot's contact model, so these fields migrate as custom long-text properties or engagement notes to preserve the clinical context within each contact record.

Bp Premier stores a referring practitioner linked to the patient record. In HubSpot, the referring practitioner becomes a contact record (or company if a practice entity) associated via a referral-type label. Referral letter metadata and expiry dates migrate as custom contact properties.

Bp Premier appointment records contain provider, start and end time, appointment type, status, and bulk-billing flag fields that map to HubSpot engagement records (meetings or calls). The bulk-billing flag and provider ID have no native equivalent in HubSpot engagements, so these values migrate as custom engagement properties to preserve billing context and owner assignment for each appointment record.

Bp Premier clinical notes are free-text with clinical author and timestamp. HubSpot has no clinical note equivalent — we migrate notes as HubSpot engagement notes or as a custom long-text property on the contact, with original author preserved as a property value. Practices should review whether clinical notes belong in a CRM at all given privacy requirements.

Bp Premier prescription data (medication name, dosage, prescriber, date) has no HubSpot native equivalent. We migrate prescriptions as a custom object in HubSpot Enterprise or as a structured custom property on the contact record. Prescribers link back to practitioner contact records by email match.

Bp Premier stores bulk-billing status, MBS item codes, and healthcare card details per encounter. HubSpot has no billing object. We migrate the most recent billing status as custom properties on the contact (Bulk_Billing_Status__c, Healthcare_Card__c, Last_MBS_Item__c). Historical MBS line items require a custom object.

Bp Premier records each patient's IHI — Australia's unique health identifier. HubSpot has no native healthcare identifier field. We migrate IHI as a custom contact property (IHI__c) and flag it as a sensitive field requiring restricted access in HubSpot's sharing settings.

Bp Premier Medicare card numbers including the Individual Reference Number (IRN) map to a custom HubSpot contact property called Medicare_Card_Number__c. Medicare card expiry dates migrate as a companion custom date property (Medicare_Card_Expiry__c) to support renewal tracking workflows in HubSpot, allowing practices to set up automated reminders for card renewals before they expire.

Bp Premier practitioner and staff records map to HubSpot users by email match. Practitioners who are not HubSpot users become contact records instead of owners. Unmatched practitioners are flagged before migration so the practice can create HubSpot user accounts or assign a fallback owner.

Bp Premier tracks My Health Record opt-in status per patient. This migrates as a custom pick-list property (My_Health_Record_Status__c) on the contact record. The My Health Record integration itself — connecting to the HI Service — must be reconfigured as a HubSpot-connected app or third-party integration post-migration.

Bp Premier file attachments (referral letters, pathology reports, consent forms) linked to patient records re-upload to HubSpot Files associated with the contact record. File size limits and HubSpot's storage quotas apply — large imaging files may require external storage with a link stored in HubSpot.

Bp Premier e-prescribing (eRx) and Medicare Easyclaim transaction records are extension-layer data with no HubSpot equivalent. We export the last transaction reference and current prescription channel as custom contact properties. The active e-prescribing integration must be rebuilt on the HubSpot side with the relevant provider.