Migrate from EXACT to Twenty CRM

EXACT contacts map directly to Twenty People. The primary company link on the EXACT contact resolves to the Twenty People.companyId relation field. Phone, email, job title, and address fields map field-by-field. If the EXACT contact has no primary company, it lands in Twenty People without a company relation.

EXACT companies map to Twenty Companies with company name, industry, phone, website, and address fields transferred directly. Parent-child company hierarchies in EXACT map to Twenty's Companies.parentId relation. Multi-company associations that EXACT supports as separate records become individual Companies in Twenty.

EXACT sales or opportunities map to Twenty Opportunities with deal name, amount, expected close date, and stage transferred. The EXACT sales status (open, won, lost) maps to Twenty's opportunity stage field with value mapping applied per your configured stages. If EXACT stores probability percentages, we transfer those as a custom field on the Twenty Opportunity, preserving historical forecasting data for reporting.

EXACT logged activities (calls, emails, meetings) transfer as Twenty Tasks with subject, description, due date, and assignee fields. Meeting activities with duration preserve start and end timestamps. Email bodies store as Note content linked to the related People or Companies record.

EXACT documents attached to contacts, companies, or sales become Twenty Notes with the file name and a reference to where the file was stored. If EXACT stored files in its document management system, we re-upload them to Twenty's storage and link them to the relevant record.

EXACT custom fields on contacts require Twenty custom fields created before import. We create matching field types in Settings → Data Model and then map the values during the CSV import. Multi-select custom fields in EXACT map to Twenty's multi-select field type.

EXACT custom fields on companies migrate to Twenty custom fields on the Companies object. The field must exist in Twenty's data model before the import run. We generate the setup plan showing which custom fields need creation and their types.

EXACT projects do not have a direct Twenty equivalent. We create a Project custom object in Twenty with fields for project name, status, start date, end date, and linked company. The EXACT project-task relationship maps to Tasks linked to the custom Project record.

EXACT users resolve to Twenty Workspace Members by email match. We invite all EXACT users to Twenty before migration so their IDs are available for assignment. Unmatched EXACT owners flag for manual resolution — their records can be assigned to a fallback owner or the inviting admin.

EXACT's internal record IDs map to Twenty's id field or stored as a custom Source_ID__c field for traceability and deduplication. This enables delta-run identification of records that were modified between the initial migration and the cutover window. By preserving the original EXACT identifiers, you can cross‑reference data in both systems during the validation phase and avoid duplicate entries when importing updated records.

EXACT's sales pipeline stages map to Twenty Opportunity stage values via a value map. If EXACT has multiple pipelines, each becomes a distinct set of stage values in Twenty. We preserve stage-entry timestamps as custom datetime fields for historical reporting.

EXACT workflows, approval chains, and automation rules do not migrate. They must be rebuilt in Twenty's Workflow builder or via API integrations. We export EXACT workflow definitions as documentation so your team can reference them when rebuilding in Twenty. The exported definition includes trigger conditions, action steps, and any conditional logic, providing a blueprint that maps directly to Twenty's automation primitives.