Migrate from Attio to Twenty CRM

Attio People records map 1:1 to Twenty Person records. We preserve all standard attributes (name fields, email, phone, job title, location) and custom attributes as Twenty custom fields. Attio's email sync history (Gmail/Outlook ingested) migrates as read-only Activity entries in Twenty. Note that Attio Person records linked to a Company via a Relationship Attribute carry a company_id that must be resolved to the corresponding Twenty Company record during import; we reconstruct this lookup chain via the Attio API before writing.

Attio Company records map 1:1 to Twenty Company records. Domain-based enrichment from Attio transfers as read-only fields. Companies are imported before People to satisfy the foreign-key dependency on the Person-to-Company relationship. We deduplicate on domain name during import.

Attio Deals map to Twenty Opportunities. Deal stage names map to Twenty pipeline stage values that we configure before migration. Amount, close date, probability, and owner assignment migrate directly. Deals linked to multiple People (Attio supports many-to-many via Relationship Attributes) map to a primary OpportunityContactRole in Twenty with secondary contacts recorded as custom multi-lookup fields.

Attio custom objects (gated 3 on Free, 5 on Plus, 12 on Pro, unlimited on Enterprise) migrate to Twenty custom objects of equivalent name. We pre-create the destination schema in Twenty before import, including all custom fields and lookup relationships to standard objects. A common migration blocker is Attio Plus plans using 5 custom objects that exceed what a simple Twenty configuration expects—validation during scoping flags this before any data moves. If the Attio workspace uses custom objects beyond the customer's target Twenty setup, we recommend consolidation or schema redesign during scoping.

Attio Lists are workflow-context collections of records with dynamic or static membership. Twenty does not have a Lists equivalent—saved Views with filter criteria provide the closest functional match. We extract every List definition, including its filter conditions (field, operator, value), and document it as a Twenty View configuration that the customer's admin recreates post-migration. List membership counts migrate as informational reference records attached to each Person and Company.

Attio Notes attach to records as threads and are first-class API objects. We migrate Notes with timestamp, author attribution, and record association preserved. In Twenty, Notes attach to the corresponding Person, Company, or Opportunity record as a comment-style entry. Rich text content migrates as plain text if the destination field type does not support rich text.

Attio Tasks migrate to Twenty Tasks with assignee, due date, status, and priority preserved. Owner assignment migrates by resolving Attio owner email to Twenty User records. Tasks attached to a specific record carry the parent lookup to the corresponding Twenty Person, Company, or Opportunity.

Attio's automatic email and calendar sync produces engagement records for People and Company records. These migrate as read-only Activity entries in Twenty's timeline, with the original timestamp preserved. Call duration and disposition from Attio migrate as custom Activity fields. Manual activity logs (logged calls, emails, meetings) migrate as equivalent Twenty Activity entries. Note that Attio's last_interaction attribute only updates via email sync and cannot be manually set—we flag this limitation in scoping so teams do not expect it to carry forward as a usable sorting signal.

Attio Workflows consume workspace credits and define automation logic with trigger conditions and action blocks. Twenty's workflow and automation capabilities are actively developing and do not have a feature-parity mapping to Attio's workflow model. We do not migrate Workflows as code. We document every active Attio Workflow with its trigger, conditions, action sequence, and credit consumption estimate, and deliver it as a written specification for the customer's admin to rebuild in Twenty when Twenty's workflow feature set matures to support the use case.

Attio Sequences (available on Pro and Enterprise plans) are sales engagement cadences with step timing and delay logic. Twenty does not have a native Sequences or sales cadence feature. We document each sequence's step structure (step type, delay, template content) as a written handoff for the customer's admin to implement via email sequences in a separate sales engagement tool or via Twenty's workflow framework when available.

Attio Users (team members who own records) map to Twenty User records via email match. Owner assignments on People, Companies, Deals, and Tasks resolve to Twenty User references at migration time. Any Attio User without a matching Twenty User goes to a reconciliation queue for the customer to provision before the final migration phase runs.

Attio Relationship Attributes define how records across objects link together (e.g., a Deal linked to a Company and multiple People). These are the highest-risk element of this migration because Attio's workspace CSV export produces flat files without join keys. We query Relationship Attributes via the Attio API before any import, reconstruct the parent-child chains, and write lookup resolution records to temporary staging. We then import in dependency order (Companies first, then People, then Deals) with the resolved foreign-key IDs so that relationships are established at insert time rather than patched afterward.