Migrate from MOGO to HighLevel

MOGO patient records map 1:1 to HighLevel contacts. All demographic fields including name, date of birth, address, phone numbers, and email address migrate as direct field maps. MOGO's original patient ID is preserved as a custom field (Source_Patient_ID__c) on the contact record for traceability, deduplication during delta runs, and reconciliation against the source system.

MOGO stores insurance carrier name, policy number, group number, and subscriber relationship as standard patient sub-fields. These have no native HighLevel equivalent and are migrated as custom fields on the contact record — specifically Insurance_Carrier__c, Policy_Number__c, Group_Number__c, and Subscriber_Relation__c. This preserves all insurance attribution data within each contact record for eligibility checks and workflow segmentation.

MOGO appointments (date, provider, operatory, procedure code, status) become HighLevel tasks with Type='Appointment'. Original appointment date, provider name, and procedure code are stored as custom fields on the task since HighLevel tasks do not natively capture provider or procedure metadata. Multiple appointments for the same patient generate separate tasks.

MOGO treatment plans with procedure codes, tooth numbers, and plan status migrate as HighLevel tasks with a custom Treatment_Plan__c field containing the plan summary. Each plan line item becomes a sub-task linked to the parent contact so the treatment roadmap is visible within the contact timeline.

MOGO clinical notes and per-visit SOAP notes do not have a HighLevel equivalent. We migrate the latest clinical note as a long-text custom field (Clinical_Notes__c) on the contact record. Historical notes are stored as task descriptions linked to the contact for chronological access. X-ray file links are not preserved in HighLevel — flagged for manual reference.

MOGO prescription records containing medication name, dosage, frequency, and prescribing provider are migrated as a text-based custom field (Prescription_History__c) on the contact. This summary approach is required because HighLevel has no native prescription object or structured medication management capability. The text field preserves the prescription record within the contact for reference without forcing an unnatural data structure.

MOGO recall intervals (e.g., 6-month cleaning, annual exam) drive automated patient re-engagement. HighLevel has no recall object — these intervals are exported as a reference dataset and rebuilt as HighLevel workflow automations using date-based triggers and contact tags (Recall_6_Month, Recall_Annual).

MOGO treatment ledger entries (procedure, fee, insurance portion, patient portion, payment status) do not map to a HighLevel object. We migrate the current outstanding balance and last payment date as custom fields (Outstanding_Balance__c, Last_Payment_Date__c). Full ledger history is exported as a CSV reference file for billing reconciliation.

MOGO providers and staff members are matched to HighLevel users by email address. Unmatched staff are flagged before migration — the practice either creates the HighLevel user account first or assigns the records to an existing user. Provider specialty is stored as a custom field (Provider_Specialty__c) on the contact.

MOGO referral source tracking data — including referring dentist names, marketing channel attribution, and word-of-mouth referral categories — migrates as a custom pick-list field (Referral_Source__c) on the contact record. This preserves all historical referral attribution data and enables future workflow segmentation based on how each patient was originally acquired.