Migrate from Bp Premier to Mailchimp

BP Premier patient records are the source of truth for contact data. Each patient with a valid email address maps to one Mailchimp contact. Patients without email addresses are flagged for manual review — Mailchimp requires a valid email per contact record.

Patient first name maps to Mailchimp FNAME, last name to LNAME, phone number to PHONE, and full address to the ADDRESS merge field. BP Premier stores addresses in structured fields (street, suburb, state, postcode) which flatten into Mailchimp's single ADDRESS merge field format.

The patient's email address in BP Premier maps directly to Mailchimp's required EMAIL field. This is the unique identifier per contact. BP Premier does not require email for all patients — contacts without email are excluded from the Mailchimp migration and surfaced in a separate report.

BP Premier patient groups (e.g., 'Diabetes Management', 'Allied Health', 'Pediatric') are not native Mailchimp audience fields — they convert to flat tags applied per contact. Multiple groups per patient result in multiple tags. Tags are the closest Mailchimp equivalent to BP Premier's patient grouping system.

BP Premier recall flags and alert codes (e.g., 'Recalls: 3-month', 'Alert: Immunisation due') need Mailchimp merge fields created to store the recall type and interval. We create a RECALL_TYPE__c and RECALL_DATE__c merge field per audience. Active recall flags also apply a 'Recall-Active' tag for segmentation.

BP Premier referral source codes (e.g., 'GP Referral', 'Self-Pay', 'NDIS') have no direct Mailchimp equivalent. We create a REFERRAL_SOURCE__c text merge field on the Mailchimp audience and populate it per contact where the source code is recorded in BP Premier.

BP Premier stores patient date of birth as a date field. Mailchimp has a native BIRTHDAY merge field (MM/DD format) — if BP Premier DOB is stored in this format it maps directly, otherwise we create DOB__c as a custom date merge field to preserve full date precision.

The BP Premier internal patient identifier (Record ID) is preserved as a custom merge field (SOURCE_PATIENT_ID__c) on each Mailchimp contact. This enables traceability between the source system and destination, and supports delta-run de-duplication for future contact updates.

BP Premier appointment history — dates, provider, appointment type — has no equivalent in Mailchimp's contact model. Appointment data remains in BP Premier. We do not migrate appointment history to Mailchimp as it is clinical scheduling data with no marketing use case in an email platform.

BP Premier clinical notes, prescription records, and clinical findings are excluded from the Mailchimp migration entirely. These contain sensitive health information that should not be stored in an email marketing platform. Only demographic and contact-adjacent properties migrate.

BP Premier records when a patient was first created in the system. Mailchimp's built-in timestamp reflects when the contact was added to Mailchimp, not when the patient record originated in BP Premier. We preserve the original BP Premier create date as a custom merge field for reporting continuity.