Migrate from Convert Wire to Twenty CRM

Convert Wire's person or contact records map directly to Twenty's People object. Each person record must include a companyId linking to a Twenty Company record — if Convert Wire stores no primary company, the person lands unlinked and can be associated manually or via bulk-edit after migration.

Convert Wire's organization or company records map 1:1 to Twenty's Companies object. Company records migrate first because Twenty's People import requires a valid companyId for each contact — parent-child hierarchies in Convert Wire map to the Twenty company hierarchy via a parentCompanyId field if that relationship exists.

Convert Wire deal records map to Twenty Opportunities. The deal's linked organization maps to the Twenty opportunity's companyId; if Convert Wire tracks person associations on deals, those link to the opportunity's personId relations in Twenty. Pipeline stage names from Convert Wire become Twenty opportunity stage pick-list values — these must be configured in Twenty's Data Model before the import.

Convert Wire pipeline definitions and their stage names require value-by-value mapping to Twenty's Opportunity stage options. Each distinct Convert Wire stage name creates a corresponding Twenty pick-list value; if Convert Wire supports weighted probability per stage, those percentages map to the stage's probability field on the Twenty opportunity record.

Convert Wire task records migrate to Twenty Tasks. The task title, description, due date, and completion flag transfer directly. Each migrated task links to the appropriate People, Company, or Opportunity record via relation fields that mirror Convert Wire's parent object. Assignee resolution maps the Convert Wire assignee to a Twenty WorkspaceMember by matching email addresses; any assignee without a matching email is flagged for admin review before the migration commits.

Convert Wire note records, call logs, and email log entries migrate to Twenty Notes with their rich-text body and original create timestamp preserved. Notes in Twenty can be linked to People, Companies, or Opportunities via relation fields — the parent object type in Convert Wire determines the relation target in Twenty.

Convert Wire file attachments and inline images stored on records have no direct equivalent in Twenty's standard import flow. FlitStack exports files from Convert Wire's storage and re-uploads them to Twenty's file storage, linking each file to the relevant People, Company, or Opportunity record. Files exceeding Twenty's storage limits are flagged for manual handling.

Convert Wire custom objects migrate to Twenty custom objects. Twenty requires all custom object schemas to be created in Settings → Data Model before the import begins — custom objects are defined via metadata API calls, then data is loaded via CSV or bulk API. Custom-object relationships that use N:N links in Convert Wire need junction objects in Twenty's relational model.

Convert Wire owner or assignee references resolve to Twenty WorkspaceMembers by matching the owner's email address. If a Convert Wire owner has no corresponding email in Twenty, their records assign to a fallback WorkspaceMember or remain flagged for manual reassignment after migration.

Twenty's native createdAt timestamp reflects the migration import date, not the original Convert Wire record creation date. FlitStack preserves the original Convert Wire created_at and updated_at values as custom datetime fields on each Twenty record (Original_Created_Date__c and Original_Updated_Date__c) so reporting continuity is maintained.

Convert Wire's internal record IDs are stored on each migrated Twenty record as a custom text field (Source_System_ID__c). This enables FlitStack's delta-run logic to de-duplicate records on subsequent migration passes and allows support teams to trace a Twenty record back to its Convert Wire origin.

Convert Wire workflows, sequence rules, and automation triggers do not have a functional equivalent in Twenty's migration layer. These must be rebuilt in Twenty's Workflow Builder after the data migration completes. FlitStack exports Convert Wire workflow definitions as a structured reference document for the rebuilding team.