Migrate from Touchdown to Twenty CRM

Touchdown Contacts map directly to Twenty People records. Email address serves as the primary dedupe key. Standard fields (name, email, phone, address) migrate 1:1. Custom contact properties are discovered during API exploration and pre-created as fields in Twenty's Data Model before import. Owner assignment (Account Owner in Touchdown) maps to Twenty workspace Members resolved by email match.

Touchdown Company records map to Twenty Company records. Company name is the primary dedupe key. Industry, website, and address fields migrate directly. If Touchdown Company records are linked to Contacts, the relationship is preserved by importing Companies before People so the Twenty People record can reference the Company via the WorkGroup or linked relationship. Schema discovery confirms whether Company exists as a named object or as contact-level company fields during scoping.

Touchdown Deal records map to Twenty Opportunities. Deal stage maps to a Twenty pipeline stage. We configure the pipeline and stage values in Twenty Settings before migration. Closed-Won and Closed-Lost status from Touchdown migrate as Opportunity stage values. Deal amount and close date transfer to Opportunity amount and closeDate fields.

Touchdown pipelines become Twenty Pipelines. We create the Pipeline with named stages and probability percentages in Twenty Settings before Deals are imported. If Touchdown uses multiple pipelines for different product lines or business units, each becomes a separate Twenty Pipeline.

Touchdown campaign metadata (name, type, status, associated contacts, and audience segment definition) is exported as a written inventory document. Twenty does not have a native Campaign object with the same feature depth. We document campaign structure, audience criteria, and associated custom fields so the customer's admin recreates campaign logic using Twenty's views, filters, and any applicable workflow builder features.

Touchdown audience segments are discovered via API and exported as structured definition records (filter criteria, segment name, associated contacts). Twenty uses Filters and saved Views on People and Company objects as the equivalent. We provide a written segment recreation guide mapping each Touchdown segment definition to the equivalent Twenty filter configuration.

Touchdown email template content and merge fields are exported as a structured document. Twenty does not have a native email template library with merge token support as a standard feature. We export template HTML and associated tokens so the customer's admin recreates templates in their chosen email sending tool and documents the replacement workflow.

Touchdown custom field schema is undocumented. We discover all custom field names, types, and picklist values during API exploration and pre-create them in Twenty's Data Model (Settings → Data Model) before any Contact, Company, or Deal import. Fields must exist before import because CSV import creates records, not fields. This step is done in the staging environment before production migration.

Touchdown email engagement records migrate as Twenty Task records linked to the corresponding People record. Subject, body, direction (sent/received), and timestamp transfer to Task fields. ActivityDate is set to the original Touchdown timestamp to preserve timeline ordering.

Touchdown call engagement records migrate as Twenty Task records with call-specific fields where supported. Call disposition, duration, and notes transfer to custom Task fields. The task is linked to the corresponding People record. Timestamp ordering is preserved.

Touchdown meeting engagements migrate to Twenty Tasks with meeting-specific metadata (date, duration, location). If Twenty supports Event records at the migration time, meetings land as Event records; otherwise, they migrate as Task records. Linked attendees resolve to People records by email match.

Touchdown Owner IDs on Contact, Company, and Deal records are resolved by email match to Twenty workspace Members. We extract all distinct owner emails, match against the Twenty Members list, and flag any Touchdown owner without a corresponding Twenty Member in the reconciliation queue. The customer's admin provisions missing Members before record import resumes.