Migrate from MOGO to Pipedrive

MOGO patient records map 1:1 to Pipedrive Person records. The patient's name, phone, email, address, and birth date migrate directly. MOGO patient IDs are preserved in Pipedrive as a custom field (MOGO_Patient_ID__c) for traceability and delta-run de-duplication. This custom field is created in Pipedrive before migration to ensure no duplicates during the delta pickup.

MOGO's primary provider assignment per patient becomes the Pipedrive Person owner. Provider email addresses are matched against Pipedrive users to resolve OwnerId. Unmatched providers are flagged before migration; your team can invite them to Pipedrive or assign records to a fallback owner.

MOGO insurance carrier records (Delta Dental, MetLife, etc.) migrate to Pipedrive Organizations. The insurance carrier name becomes the Organization name. Patient-to-insurance assignments migrate as Person-to-Organization relationships in Pipedrive. Insurance group numbers and subscriber IDs are stored as custom fields on the Organization and Person records respectively, preserving billing context for each patient.

MOGO appointments become Pipedrive Activity records. The appointment date and time become the Activity due date; the appointment type (exam, cleaning, procedure) becomes the Activity subject. Provider assignment resolves to the Activity owner. Operatory and procedure codes are stored in custom fields on the Activity.

Completed treatment records in MOGO (filling, crown, root canal) map to Pipedrive Deals. The treatment fee becomes the Deal value. Treatment date becomes the Deal close date. Procedure codes and tooth numbers migrate as custom fields on the Deal. Active treatment plans map to open Deals; completed treatments map to Won Deals.

MOGO procedure codes (D0140, D2750, etc.) map to Pipedrive Products. Each procedure has a name, ADA code, and fee — these become the Product name, code, and standard price. Deal-Product associations in Pipedrive replicate which procedures were part of which treatment case.

MOGO multi-phase treatment plans (Phase 1: periodontal, Phase 2: restorative) map to a single Pipedrive Deal with all phases documented in the Deal notes and custom fields. Each phase can alternatively map to separate Deals linked by a custom text field, depending on your reporting needs.

MOGO billing records (amount billed, amount paid, insurance portion, patient portion, balance) translate into Pipedrive Deal fields. The total fee becomes Deal amount; payments received are tracked as Deal updates. Outstanding balances require a custom field on the Deal since Pipedrive has no native accounts-receivable tracking.

MOGO insurance claims with submission date, status, and payer response have no Pipedrive native equivalent. Claims are migrated as Activity records with type=InsuranceClaim, date submitted as due date, and claim status stored in a custom field. Your team rebuilds claims tracking in Pipedrive using Activities and custom fields.

MOGO referral sources (other practices, corporate accounts, marketing campaigns) migrate to Pipedrive Organizations. The referring entity name becomes Organization name; referral-specific fields migrate as custom fields. Pipeline reports in Pipedrive can then segment revenue by referral source. This allows your team to track which referral channels drive the most treatment cases and adjust marketing spend accordingly.

Any MOGO custom field on patient records (clinical notes, medical history flags, HIPAA consent flags) requires a corresponding Pipedrive custom field on Person. We create these fields in Pipedrive before the migration run and map values field-by-field. Multi-select fields in MOGO are mapped to Pipedrive multiselect fields to maintain data integrity.

MOGO custom fields on treatment records (anesthesia type, material used, tooth numbers) migrate to Pipedrive Deal custom fields. Multi-select values in MOGO require Pipedrive multiselect custom fields; we create the field types to match the source data. This ensures that treatment-specific details such as anesthesia type and tooth numbers are preserved in Pipedrive for clinical reference.

MOGO recall intervals (6-month cleaning, annual exam) have no direct Pipedrive equivalent. Recalls are migrated as Activity records with the next recall date as the due date and a subject like Recall: Cleaning. Pipedrive's automation rules can be configured to create follow-up Activities based on these dates after migration.

MOGO attachments per patient or treatment record are downloaded and re-uploaded as Pipedrive Activity attachments. File size limits per Pipedrive's storage allocation apply. We preserve the original file name and uploaded date for reference. Attachments over Pipedrive's size limit are noted in the migration report for manual handling if needed.

MOGO's practice or office location data can be merged into a top-level Organization representing the practice itself, or mapped as a custom field on all Patient and Deal records for filtering. Multi-location setups use Organization hierarchies in Pipedrive. This structure enables location-specific pipeline reports and revenue tracking per office in Pipedrive.