Migrate from FIVE CRM to Twenty CRM

FIVE CRM Contacts map to Twenty CRM People. Standard fields (name, email, phone, address) transfer directly. FIVE CRM's custom telemarketing fields (lead score, call disposition, last call outcome) require pre-created custom fields in Twenty's Data Model before import; we enumerate these during scoping and create them in Twenty Settings prior to data load. Contact owner resolves by email match against Twenty Members.

FIVE CRM Companies map to Twenty CRM Companies. Company is created before People import so that the relationship lookup is satisfied at the moment of People insert. FIVE CRM's domain field maps to Twenty's website field and is used as the dedupe key. Custom company fields (industry classification, employee count ranges used in telemarketing segmentation) migrate to pre-created custom fields.

FIVE CRM separates Leads from Contacts in its data model. We merge Lead records into Twenty CRM People and set a custom field lead_source__c from FIVE CRM's originating lead source property. If the FIVE CRM Lead has an associated Deal, that Deal migrates to Twenty Opportunity with the Opportunity's primary contact set to the merged People record.

FIVE CRM Deals map to Twenty CRM Opportunities. The deal name, amount, expected close date, and pipeline stage transfer directly. FIVE CRM's custom pipeline stages require mapping to Twenty's Opportunity stage values, which we configure as part of the pre-migration schema build. Deal owner resolves by email match against Twenty Members.

FIVE CRM pipeline stages are tenant-specific custom labels. We capture every active stage label during scoping, map each to a Twenty Opportunity stage value, and configure Twenty's opportunity stage list in Settings before migration. Stage probability percentages transfer where FIVE CRM exposes them; otherwise we set defaults and the customer adjusts post-migration.

FIVE CRM Campaign records track email marketing sequences and campaign membership. Campaign membership transfers as a custom multi-select field or tag on the linked Twenty People or Opportunity record, depending on which object the campaign primarily targets. Individual email event logs (opens, clicks) do not have a direct Twenty equivalent and are documented as not migrating.

FIVE CRM Tasks map to Twenty CRM Tasks with due date, assignee, status, and description preserved. Task assignee resolves by email match against Twenty Members. FIVE CRM task types (call back, follow up, demo scheduled) map to Twenty task categories or custom task type fields created during the schema build phase.

FIVE CRM Users (owner records) map to Twenty CRM Members. We resolve by email match. Any FIVE CRM User without a matching Twenty Member goes to a reconciliation queue for the customer's admin to provision the account in Twenty Settings before record import resumes. Twenty requires Members to be invited and active before owner lookups can resolve.

FIVE CRM custom fields are tenant-specific and not consistently named across deployments. We enumerate every custom field in use during a pre-migration field mapping session, confirm data types, and create matching fields in Twenty's Data Model before import. FIVE CRM's opaque error system means we cannot always rely on the UI to surface field anomalies, so we validate field types against known FIVE CRM schemas and test each custom field independently during the sandbox migration phase.

FIVE CRM tags label records for segmentation and campaign targeting. We map tags to Twenty's tag system or to a custom multi-select field depending on the tag's semantic role (segmentation tag vs. campaign classification). Multi-select tag fields may split into multiple rows during import if the destination uses a single-select field; we document this during scoping and the customer chooses the strategy.

File attachments associated with FIVE CRM Contacts, Companies, or Deals migrate as file references or re-upload depending on the target Twenty deployment. Attachments over 10MB require separate handling due to API upload size constraints. We flag large attachments during scoping and handle them as a post-migration manual upload batch.

FIVE CRM tracks email campaign engagement (opens, clicks, replies) at the contact level. Twenty CRM does not expose a granular per-event engagement log object in its standard data model. We migrate campaign membership and status flags to People and Opportunity records; individual email event logs are documented in a separate export for the customer's admin to import manually if the downstream reporting requires it.