Migrate from Data Team DDS to Twenty CRM

Direct map. Twenty's People object stores individuals with name, email, phone, job title, and a relation to Companies. If Data Team DDS stores contacts without a linked company, they land in Twenty as standalone People records. All standard fields map directly; custom contact properties must be pre-created in Twenty Settings before import.

Direct map. Data Team DDS company records map to Twenty's Companies object. Parent-company hierarchies in Data Team DDS map to the ParentId relation in Twenty's Companies if that structure exists in the source export. Industry and employee count fields migrate as custom selects or numbers if they are present in the source data.

Direct map. Twenty's Opportunities object tracks deal name, amount, stage, close date, and linked company and people. Each Opportunity is a single deal row — Data Team DDS deal rows with line items become one Opportunity with the total amount unless your plan calls for splitting.

Data Team DDS pipeline stage names map to Twenty's Opportunity stage pick-list values. Stage probability percentages map as-is if the source exposes them, or are set as a custom field on Opportunities. Stage order is preserved for kanban view sequencing.

Data Team DDS call logs migrate as Twenty Tasks with Type='Call' in the subject or a custom type field. Original call date, duration (if stored), owner, and notes are preserved. The Task is linked back to the People record via Twenty's relation field.

Email engagement records map to Twenty Tasks with Type='Email'. Subject line, body content, sent/received timestamp, and owner are migrated. Thread linkage is flattened — individual emails become separate Task records rather than a threaded conversation view. If the source email includes attachments, the file references are preserved as URL attachments on the Task or re-uploaded to Twenty's file storage.

Meeting records from Data Team DDS map to Twenty Tasks with the meeting title as subject, start/end times as task date fields, and the invitee list as a comma-separated custom field or as linked People records if the meeting-object schema supports it.

Notes migrate as Twenty Notes attached to People, Companies, or Opportunities by their record ID. Rich-text formatting is preserved where Data Team DDS supports it; plain-text notes map without transformation. Each note's creation date and owner are stored as custom datetime and assignee fields to preserve audit trails.

Data Team DDS tasks and to-dos migrate directly to Twenty's Tasks object. Due date, assignee (resolved by email match to Twenty workspace members), status (open/closed), and subject are all carried over. Any custom task fields (e.g., priority, category) must be pre-created in Twenty Settings before migration, and are imported as custom fields on the Tasks object.

Data Team DDS owner and user IDs are resolved by email against Twenty workspace members. Users who exist in both systems map by email match. Users present only in Data Team DDS are flagged for your team to either invite to Twenty or assign to a fallback member before migration.

Data Team DDS custom contact properties migrate as Twenty People custom fields. These must be pre-created in Twenty Settings Data Model before migration runs — the CSV import does not auto-create fields. Text, number, date, and select field types are supported natively.

Data Team DDS custom company properties become Twenty Companies custom fields. Same constraint as People custom fields — create them in Settings before importing data. Industry and employee count may already exist as standard Twenty fields depending on your version.

Data Team DDS custom objects map 1:1 to Twenty custom objects. Custom-object-to-standard-object relationships that use N:N associations in Data Team DDS may need junction objects in Twenty — this is surfaced in the migration plan before execution. All fields within custom objects are migrated as their respective types, and any missing field definitions are flagged for creation in Twenty Settings prior to the import run.

File attachments linked to Data Team DDS records are preserved as URL references where the source exposes them. If Data Team DDS stores files internally, FlitStack downloads and re-uploads them to Twenty's file storage. Inline images in notes are extracted and re-hosted.

Data Team DDS workflows, automations, and sequences do not migrate to Twenty. Twenty's workflow builder supports basic field-update and notification automations. FlitStack exports your Data Team DDS workflow definitions as a rebuild reference document for your Twenty admin. Your admin can use this export to recreate each workflow step manually in Twenty's builder, or leverage the v2.0 SDK to implement custom automation logic programmatically.