Migrate from Twenty CRM to Freshsales

Twenty Companies map to Freshsales Accounts. We use domain as the dedupe key — Twenty's domain field becomes the Account Website field — so that duplicate Company names do not create duplicate Accounts during import. Accounts must be created first because Freshsales Contacts require Account linkage and Twenty People records may carry a companyId reference. If Twenty companies lack a domain value, we use the company name as the matching key and flag any ambiguous matches for customer review.

Twenty People records map to Freshsales Contacts. Freshsales requires each Contact to be linked to an Account; we resolve companyId from Twenty at migration time and map it to the Freshsales AccountId. Where a Twenty Person has no companyId, we create a placeholder Account or map to a catch-all account as agreed during scoping. Email serves as the unique identifier for deduplication. Phone, job title, city, and custom People fields migrate to typed Freshsales Contact fields or custom contact fields.

Twenty Opportunities map to Freshsales Deals. Stage names from Twenty require explicit mapping to Freshsales Deal Status values — there is no bulk stage import in Freshsales, so we configure each stage individually during the Freshsales setup phase. Amount, close date, probability (where available), and the Opportunity's linked Company and Person references migrate with OwnerId resolved via Owner email matching. Closed-won and closed-lost reasons from Twenty become Freshsales Deal custom fields.

Twenty Tasks map directly to Freshsales Tasks. Title, due date, assignee (Owner email resolved to Freshsales User), completion status, and linked record reference migrate. The linked record reference (People, Company, or Opportunity) is resolved to the corresponding Freshsales Contact, Account, or Deal ID at migration time using the pre-built ID mapping from earlier phases.

Twenty Notes are free-form text blocks linked to any record. Freshsales embeds Notes within Contacts and Deals rather than maintaining a standalone Note object. We present two options during scoping: (a) migrate each Note as an embedded Contact Note or Deal Note in Freshsales, preserving body text and linked record reference, or (b) create a custom Note activity record to preserve a standalone Note object if the customer's workflow depends on Note-level reporting. The choice is made before migration runs.

Twenty Custom Objects migrate to Freshsales Custom Modules with equivalent field definitions. We pre-create the Custom Module schema in Freshsales — including all custom fields, field types, and picklist option sets — before any data import. Note that Freshsales picklist option values must be recreated manually in the Freshsales UI; there is no bulk import of picklist options. Custom Object records import last because they may contain lookup relationships to standard objects (Company, People, Opportunity) that must exist first.

Twenty Owner references (on People, Companies, Opportunities, Tasks) map to Freshsales Users by email match. We extract all distinct Owner emails from Twenty records, check for a matching User record in the destination Freshsales org, and flag any Owners without a corresponding User for the customer to provision before migration resumes. Owner resolution must complete before any record phase begins because OwnerId is required on most standard object imports.

Twenty deal pipelines map to Freshsales Deal pipelines. Each pipeline in Twenty requires a corresponding pipeline to be created in Freshsales, and each stage within that pipeline must be added individually — there is no CSV import for stage values. We configure all pipelines and stages during the Freshsales setup phase, mapping Twenty pipeline names and stage labels to Freshsales equivalents with probability percentages preserved.