Migrate from matrix to Twenty CRM

Matrix contacts map to Twenty People records. The People object in Twenty stores name, email, phone, job title, and a relation to the parent Company. Owner assignment resolves by email match against Twenty workspace members. If a Matrix contact has no associated company, it lands in Twenty as a People record without a companyId link.

Matrix company records map to Twenty Companies. The Companies object holds name, domain/website, industry, employee count, and annual revenue fields. Company hierarchies (parent/child) in Matrix translate to Twenty's company relation field if your setup uses that pattern. Multi-company associations on contacts collapse to one primary companyId plus relationship records in Twenty.

Matrix deals map to Twenty Opportunities. The Opportunities object tracks deal name, amount, stage, close date, and links to a Company and one or more People records. Pipeline stage names in Matrix map to Opportunity stage values in Twenty via value-by-value mapping—stages with no direct match get assigned to a default 'Open' or 'New' stage pending your review.

Matrix tasks and activities become Twenty Tasks. Completed tasks, call logs, and email records from Matrix migrate as Tasks with Type set to 'Call', 'Email', or 'General' and original timestamps preserved. Notes in Matrix become Twenty Notes attached to the parent record (Person, Company, or Opportunity). Rich-text formatting in Matrix notes is preserved in Twenty's Note body field.

Matrix pipeline stages map to Twenty Opportunity stage values. Each Matrix deal stage (e.g., 'Qualification', 'Proposal', 'Closed Won') maps to a corresponding Twenty stage option. We preserve the original stage-entered timestamp as a custom datetime field on the Opportunity so reporting continuity is maintained. Stages with no match get flagged for your review before the full migration runs.

Matrix owner IDs resolve to Twenty workspace members by email address. If a Matrix owner email matches an existing Twenty workspace member, their Twenty user ID becomes the record owner. Unmatched owners are flagged in the migration plan—you must either invite those users to Twenty first or designate a fallback owner who receives those records. No record lands in Twenty without a resolved owner.

Matrix custom objects map 1:1 to Twenty custom objects. Before migration, we create the equivalent custom objects in Twenty via Settings → Data Model, then map custom fields to their Twenty counterparts. Custom-object relationships (one-to-many or many-to-many) translate to Twenty relation fields—if Matrix uses N:N associations, we build junction objects in Twenty.

File attachments from Matrix records re-upload to Twenty as file attachments on the corresponding Notes or Task records. File size limits apply—Twenty's import process handles re-upload of files up to the configured storage limit. Inline images in rich-text notes are extracted and re-hosted as Twenty attachments.

Matrix workflows, sequences, and automation triggers do not have a migration path to Twenty. We export your workflow definitions as JSON configuration files and note every trigger, condition, and action so your Twenty admin has a rebuild reference. This is disclosed upfront—no surprises at cutover.

Matrix tags and label assignments on contacts or deals migrate to a custom multiple-select field in Twenty (e.g., Tags__c on People). If Twenty's tag model matures, the field can be re-mapped. We create the field in Twenty before import and populate it with the tag values from Matrix.

Matrix internal record IDs are stored as a custom text field on each Twenty record (e.g., Source_ID__c). This enables delta-run de-duplication on future synchronizations and provides traceability back to the original Matrix record if reconciliation is needed. The field remains editable, allowing you to append additional identifiers or override values as your integration evolves.