Migrate from crmConnect to Twenty CRM

crmConnect Contact records map to Twenty CRM Person objects. We extract standard fields (name, email, phone, address, company association) from CSV export and map them to the corresponding Twenty Person field names. crmConnect does not expose a field schema endpoint, so we discover available custom contact properties during the export phase and map each one to a Twenty custom field before migration. Any crmConnect tag associations on contacts migrate as tag strings on the Person record.

crmConnect Company records map to Twenty CRM Organization. The company name, domain, industry, and address fields map directly. Organization is created in Twenty before Person import so that the Person-Organization relationship is satisfied at the moment of Person insert. crmConnect does not enforce a strict account-company split, so single-record accounts map to Organizations without a linked Person.

crmConnect Pipelines map to Twenty CRM Opportunities with stage names configured to match the source pipeline stage labels. Since crmConnect Professional limits to 1 active pipeline, the mapping is typically one pipeline to one set of Opportunity stages. We configure Twenty's pipeline stages with names, probabilities, and ordering matching the crmConnect pipeline definition before migration.

crmConnect Opportunities map to Twenty CRM Opportunities with amount, stage assignment, expected close date, and owner association preserved. The Opportunity is linked to the parent Organization and the responsible Person owner. Custom opportunity fields in crmConnect are discovered during export and mapped to Twenty custom fields before the import phase.

crmConnect Calendar records with event times, attendees, and linked contact associations map to Twenty CRM CalendarEvent. We preserve event title, start and end timestamps, attendee list, and the association to the linked Person record. Standard tier limits to 1 calendar; Professional supports unlimited calendars, and we migrate all calendar records found in the export.

crmConnect email engagement records migrate to Twenty CRM as combined activity entries. The email content and timestamp attach to the linked Person record's activity timeline. We use Twenty's API for activity inserts rather than CSV to preserve the chronological ordering against the correct Person record.

crmConnect call engagement records migrate to Twenty CRM Task with the call subtype and duration preserved. Call disposition and notes map to task body fields. Activity ordering is preserved by setting the task timestamp to the original crmConnect call timestamp.

crmConnect meeting engagements map to Twenty CRM Task with type meeting. Meeting title, attendees, location, and start time transfer. Attendee mapping links to Person records via the relationship resolution step.

crmConnect Notes migrate as Twenty CRM Comments attached to the relevant Person, Organization, or Opportunity record. We determine the target object by the note's association field in the source export. Rich text formatting is preserved where the export preserves it; plain text where it does not.

crmConnect automations have no documented export format, so they cannot migrate as functional code. We export available automation metadata (trigger type, conditions, and action descriptions) from screenshots and any accessible internal metadata, then deliver a written automation intent document listing each automation with its purpose, trigger, conditions, and recommended Twenty CRM equivalent. The customer's admin rebuilds automations in Twenty's workflow system post-migration.