Migrate from Acumen to Twenty CRM

Acumen Contact records map directly to Twenty People. The People object stores name, email, phone, job title, and a companyId relation. For Acumen contacts without a primary company, a default placeholder company record gets created so the People record lands with a valid companyId reference.

Acumen Company maps to Twenty Companies. Companies store organization name, domain, industry, size, and location. The domain field in Acumen maps to the website field in Twenty's Companies object. Parent-company hierarchies resolve via a separate import step where the parentCompanyId maps to the Companies record's id field.

Acumen Deal maps to Twenty Opportunities. Opportunities track deal name, amount, stage, expected close date, and companyId plus personId relations. Acumen deal stage values map to Twenty Opportunity stage pick-list values — value-by-value mapping required when stage names differ between systems.

Acumen call activity records migrate as Twenty Tasks with Type set to 'Call'. The original call duration, outcome, and owner assignment transfer as custom fields or notes on the Task record. Owner resolves via email match against Twenty workspace members.

Acumen email activity records migrate as Twenty Tasks with Type set to 'Email'. The email subject, body, and timestamp preserve on the Task. Emails linked to specific People or Opportunities carry those relation IDs so the activity appears in the correct record's timeline.

Acumen meeting records map to Twenty Tasks with meeting-specific fields capturing start time, end time, location, and attendees. If Twenty's standard Event object is available in your tier, meetings use that instead to preserve full calendar integration with support for recurring meeting patterns and video conferencing link fields.

Acumen notes migrate as Twenty Notes attached to People, Companies, or Opportunities. Rich-text formatting in Acumen notes converts to Twenty's note body format. Notes without a parent record attach to the most recently related People record based on create date.

Acumen user and owner records map to Twenty Workspace Members. Resolution happens by email — each Acumen owner email matches against invited Twenty users. Unmatched owners get flagged before migration; their records can be assigned to a fallback member or held for manual reassignment.

Acumen custom objects map 1:1 to Twenty custom objects if your Twenty plan supports them (Organization tier and above). Custom object fields must pre-exist in Twenty's data model before migration. N:N relationships between custom objects require junction objects created in Twenty's Settings → Data Model.

Acumen file attachments on records re-upload to Twenty. Files store in Twenty's attachment system and link to the parent record (People, Companies, or Opportunities). Large files or inline images in rich-text notes download, rehost, and relink to maintain display in Twenty.

Acumen deal pipelines and stages map to Twenty Opportunity stages. Each stage name in Acumen requires a corresponding stage value in Twenty — custom stage names need value-mapping setup. Stage probability weights transfer as custom fields if you need them for reporting.

Acumen text custom fields require pre-creation in Twenty Settings → Data Model before migration. The field name, type, and any pick-list options must match the source configuration. FlitStack delivers a field-creation checklist so Twenty admins can provision fields before the import runs.

Acumen pick-list custom fields map to Twenty select custom fields. Each pick-list value requires explicit value mapping to the corresponding Twenty select option. Unused or inactive Acumen values get flagged for decision — include or exclude based on your data retention policy.

Acumen's internal record identifiers are preserved as a custom field on each migrated record called Source_System_ID__c. This custom field maintains traceability back to the original Acumen data for all subsequent migrations and data refreshes. It enables delta-run de-duplication by identifying which records have already been imported into Twenty, facilitates rollback identification if you need to revert changes, and provides a permanent cross-reference between Acumen exports and Twenty records.