Migrate from Results to Twenty CRM

Results Contact records map to Twenty People. The primary email address on the Contact becomes the People email field and serves as the dedupe key during import. Any first name, last name, phone, job title, or address fields map to their Twenty equivalents. We confirm the exact field inventory on the Results side during the scoping call because no public API schema is documented.

Results Company records map to Twenty Company. The domain or website on the Company becomes the Company domain field and is used for cross-referencing People records by domain. Company is created before any People import so that the relationship lookup is satisfied at the moment of People insert.

Results Deal records map to Twenty Opportunity. The deal stage maps to Twenty stage, and the pipeline assignment maps to a Twenty Record Type with a corresponding Sales Process configured before migration. Deal amount, close date, and probability migrate to their Twenty equivalents.

Each Results deal pipeline becomes a Twenty Record Type on Opportunity with its own Sales Process that defines the valid stage values and probabilities. Stage names and ordering are preserved from Results, with the customer choosing whether to include or exclude closed-lost or stale stages from the target configuration.

Results Owner references on Contact, Company, Deal, and Activity records map to Twenty Workspace Members resolved by email match. We require the customer to invite and confirm all Users in Twenty before record migration begins, per Twenty's documentation requirement that users must exist before Owner lookups can resolve. Owners without a matching Twenty User go to a reconciliation queue.

Results custom objects migrate to Twenty custom objects of matching name. We create the destination schema in Twenty via Settings → Data Model and the /metadata API before any custom object data is imported. All custom fields, field types, picklist values, and lookup relationships are pre-configured. Any lookup fields referencing standard objects (People, Company, Opportunity) are validated against the existing import of those objects.

Results call activities map to Twenty Task records with the call subtype flagged. Call duration, disposition, and any recording URL stored in Results migrate to custom Task fields in Twenty. The activity timestamp preserves the original Results timestamp for timeline ordering.

Results email activities map to Twenty Task records. The email subject and body migrate to the Task body, linked to the related People or Company record. If Results stores email as a separate activity object, we map it to Task with the email body preserved in the body field and the timestamp used for timeline ordering.

Results meeting activities map to Twenty Task records. Meeting title, attendees, start time, and location migrate to the corresponding Task fields. The task is linked to the relevant People, Company, or Opportunity record via the Twenty relationship model.

Results notes (standalone note records or note-type activities) map to Twenty Note records linked via ContentDocumentLink to the parent People, Company, or Opportunity record. Rich text formatting is preserved where the Results export format supports it.

Attachments associated with Contact, Company, or Deal records in Results migrate as Twenty Attachments linked to the corresponding People, Company, or Opportunity record. File names and original upload timestamps are preserved. Attachments exceeding 25 MB are flagged for manual handling or alternative delivery.