Migrate from MARS to Twenty CRM

MARS Contact records map to Twenty People. The mapping requires that every MARS contact field has a corresponding Twenty field created in Settings → Data Model before CSV import. If MARS stores multiple phone numbers or email addresses per contact, these map to the primary Phone and Email fields; additional contact details may require custom fields in Twenty since GitHub issue #13953 notes that Twenty's standard Person fields are intentionally minimal. Owner references on People require that the corresponding Twenty User exists before import.

MARS Company records map directly to Twenty Company. Twenty's Company object uses the same object name, which simplifies the mapping. The MARS company domain or website becomes the Company Website field. Companies are imported first because People records typically reference a Company via a lookup field. Custom fields on MARS Company require pre-creation in Twenty Settings → Data Model before import.

MARS Deal records map to Twenty Opportunity. The MARS deal stage maps to Twenty's Opportunity stage values, which the customer configures in Settings before migration. Closed-Lost and Closed-Won reasons from MARS custom fields migrate as custom Opportunity fields in Twenty. The Opportunity amount and close date map directly to the corresponding Twenty Opportunity fields.

Each MARS pipeline stage becomes a Twenty Opportunity stage value. The customer configures the ordered stage list in Settings before migration. Probability percentages from MARS can be stored as custom Opportunity fields in Twenty since Twenty's standard Opportunity model does not include automatic stage probability. The stage mapping document created during scoping is referenced during CSV import.

MARS Activity records map to Twenty Task or Note depending on the activity type. Calls and tasks map to Twenty Task. Meeting records map to Twenty Task with a meeting flag or to Note depending on the activity content. Email records without a call or meeting classification typically map to Note in Twenty's standard model since Twenty does not have a native email logging object equivalent to Salesforce's EmailMessage. Activity timestamps preserve the original MARS date for timeline ordering.

MARS Owner records map to Twenty User. Owner resolution happens by email match. Critical requirement from Twenty's documentation: users must be invited and must accept the invitation in Twenty Settings → Members before importing any records that reference an owner or assignee. Owners without a matching Twenty User are held in a reconciliation queue for the customer's admin to provision before record import proceeds.

MARS custom objects migrate to Twenty Custom Objects with equivalent API names. Each custom object requires pre-creation in Twenty Settings → Data Model before data import. Custom fields on custom objects, lookup relationships to standard objects (People, Company, Opportunity), and any validation settings must be configured before the CSV import runs. The import order for custom objects is last in the dependency sequence because they often have foreign keys to standard objects imported earlier.

If MARS stores product or service records linked to Deals, these migrate as Twenty Custom Objects since Twenty's standard model does not include a built-in Product2 equivalent. Product name, SKU, unit price, and description map to custom fields on the Products custom object. Price book and pricing configuration from MARS requires manual setup in Twenty or a custom field structure.

MARS tags and labels stored as multi-select properties on Contact, Company, or Deal migrate to Twenty custom multi-select fields. If MARS tags are used for content classification rather than CRM segmentation, they may map to Note tags or a custom classification field. The customer chooses the tag strategy during scoping based on how tags are used in reporting and segmentation.

MARS notes migrate to Twenty Note records linked to the parent People, Company, or Opportunity record. Attachments associated with MARS notes migrate as file references in Twenty if the attachment storage path is preserved in the export, or as Note records with a content summary. Rich text formatting in MARS notes preserves as plain text or basic HTML in Twenty Note.