Migrate from MOGO to Zoho CRM

MOGO patients must be assigned to either Zoho Lead or Contact based on patient status or record type. Active patients with open treatment plans land as Zoho Contacts; inactive or prospect records route to Lead. This split is necessary because Zoho does not have a unified patient record equivalent to MOGO's structure.

Active MOGO patient records with clinical history and open appointments map directly to Zoho Contact. The patient's primary address, phone, email, and insurance fields translate to Zoho Contact standard and custom fields. The original MOGO patient create date is preserved as a custom datetime field for continuity in reporting.

MOGO's practice or facility entity maps to Zoho Account. Practice name becomes Account Name, address fields map to the standard Zoho Account address compound, and practice phone maps to Account Phone. If MOGO stores multiple locations under one practice, each location becomes a separate Zoho Account with the parent-practice as a parent AccountId lookup.

MOGO appointments translate to Zoho Tasks. The appointment date and time map to Zoho Task Due Date and Reminder fields. Treatment codes, procedure names, and cost data map to custom fields on the Task because Zoho standard Task does not have native procedure-name or cost fields. The Task subject uses the appointment type or procedure name from MOGO.

MOGO procedures with associated costs map to Zoho Deals. The procedure name becomes the Deal Name, the cost maps to Deal Amount, and the treatment status maps to the Deal Stage pick-list via value mapping. If MOGO tracks multiple procedures per patient visit, each procedure generates a separate Zoho Deal linked to the Contact.

MOGO files attached to appointments — clinical forms, imaging references, or signed documents — migrate as Zoho Attachments linked to the corresponding Task record. The original filename is preserved. Inline images or embedded references in MOGO notes are extracted and reattached as separate files if the export format supports it.

MOGO insurance carrier, group number, subscriber ID, and account balance do not have Zoho standard equivalents. These migrate as custom fields on the Zoho Contact record: Insurance_Carrier__c, Insurance_Group_Number__c, Insurance_Subscriber_ID__c, and Account_Balance__c. The field data types match the source values (text or currency).

MOGO clinical notes and patient history text fields migrate to a combination of Zoho Contact Notes and a custom Treatment_History__c multi-line text field. Long-form clinical notes that exceed Zoho's standard Note body length are stored in the custom field to preserve all content without truncation.

MOGO provider and staff user records are matched to Zoho Users by email address. MOGO does not expose a user export in standard CSV templates, so FlitStack requests admin-level export access or uses an authenticated API session. Unmatched users are flagged before migration so the Zoho admin can pre-create accounts or assign records to a fallback owner.

MOGO custom fields added to the patient record — such as referral source, preferred contact method, or recall date — are created as Zoho Contact custom fields using the same data type. Multi-select pick-list fields in MOGO become Zoho multi-select pick-list custom fields with values preserved exactly as they appear in MOGO.

MOGO custom fields on appointments — such as recall type, provider notes, or chair time — migrate as Zoho Task custom fields. Each custom field is created on the Task module with matching data type before the migration run so the fields are available for mapping without post-migration remediation.

MOGO workflows and automated sequences do not have a direct equivalent in Zoho CRM and cannot be migrated programmatically. We export your MOGO workflow definitions as a reference document and recommend rebuilding priority workflows in Zoho Blueprint or Zoho Workflow Rules post-migration using the exported definitions as a guide.