Migrate from MOGO to Twenty CRM

MOGO contacts migrate as Twenty People records. Email, name, phone, job title, and address fields map directly. MOGO contacts without a linked company land as standalone People records. Primary company assignment uses Twenty's companyId relation field on the People object.

MOGO companies map to Twenty Companies directly. Company name, domain, industry, employee count, and revenue fields translate to their Twenty equivalents. If MOGO supports parent-company hierarchies, the top-level company migrates first, then children reference it via the parentId relation in Twenty.

MOGO deals translate to Twenty Opportunities. Deal name, amount, close date, and stage all map to their Twenty counterparts. The MOGO deal stage name becomes a custom select field in Twenty since Twenty's pipeline model differs from MOGO's stage naming conventions.

Every MOGO custom field on contacts, companies, or deals requires a corresponding custom field in Twenty before migration. Field type mapping applies: MOGO text fields become Twenty text fields, pick-lists become select or multi-select, and numeric fields map to Twenty number fields. We create these in Twenty during the schema-setup step before data loads.

MOGO engagement records — calls, emails, and meetings — migrate as Twenty Tasks. The activity type (call, email, meeting) is stored in a custom select field on the Task. Original timestamps, owners, and linked contact/company references are preserved via Twenty's relation fields on the Task object.

MOGO notes migrate as Twenty Notes attached to the relevant People, Companies, or Opportunities record. Rich-text formatting in MOGO notes is preserved as-is in Twenty Notes. If MOGO notes include file attachments, those files must be re-uploaded manually or via Twenty's API since CSV imports do not carry binary attachments.

MOGO tasks and to-do items map directly to Twenty Tasks. Due date, assignee (resolved by email match to Twenty workspace member), completion status, and linked record references all transfer. Open and completed status is represented using Twenty's standard task completion field.

MOGO owner or user IDs resolve to Twenty workspace members by email address match. During migration, each MOGO owner email is checked against the Twenty workspace member list. Unmatched owners are flagged before migration commits — your team either creates the Twenty user first or assigns records to a fallback workspace member.

MOGO file attachments on contacts, companies, or deals do not transfer via CSV import or standard API export. We export the list of attachment names and the records they belong to as a rebuild reference. Files must be re-uploaded manually in Twenty or via Twenty's API upload endpoint after migration completes.

MOGO workflows, sequences, and automation rules do not migrate. They are application-level logic with no data representation. We export your MOGO workflow definitions as a structured reference document so your Twenty admin or implementation partner can rebuild equivalent logic in Twenty's workflow builder or via external automation tools.