Migrate from Freshsales to Twenty CRM

Freshsales Leads with a lifecycle stage of New, Open, or Unqualified map to Twenty Person records with lifecycle_type set to lead. The original Freshsales lifecycle stage is preserved in a custom field for reporting continuity. We import Leads first so that the migration creates Person records before any Contacts are mapped, preventing duplicate entries when a Freshsales Lead has the same email as an existing Contact.

Freshsales Contacts map to Twenty Person records with lifecycle_type set to customer (or the equivalent stage from the Freshsales lifecycle matrix). The contact's linked Account becomes a Company lookup in Twenty. We preserve the Freshsales contact type, job title, phone, email, and any custom fields on the Person record. After migration, the Freshsales distinction between Lead (pre-conversion) and Contact (post-conversion) collapses into a single Person object with a lifecycle_type field for segmentation.

Freshsales Accounts map directly to Twenty Companies. The account name becomes the Company name; the domain field maps to the website URL; address fields transfer in full. We import Companies before Contacts so that the Person-to-Company relationship (stored as a company_id foreign key on the Person record in Twenty) is satisfied at insert time. Multi-address accounts are flattened to the primary address in Twenty with secondary addresses noted in a custom field.

Freshsales Deals map to Twenty Opportunities. The deal name becomes the Opportunity name, amount transfers directly, and pipeline stage maps to Twenty's stage field using the customer-defined stage names from the Freshsales pipeline configuration. The probability percentage transfers as a custom field if Twenty's stage-based defaults do not match the customer's original probabilities. The deal owner resolves to a Twenty workspace member by email match.

Freshsales pipeline configurations (multiple pipelines available on Pro and above) map to Twenty Pipeline records. Each Freshsales pipeline becomes a distinct Twenty Pipeline with its stage sequence preserved. Stage order, stage names, and stage-level probabilities transfer. Closed-Lost and Closed-Won stages are retained in Twenty even though they may represent a different set of final states than Freshsales.

Freshsales Products map to a custom object in Twenty that we name Products to match the source terminology. Product name, SKU (hs_sku equivalent), unit price, and description transfer. Products are imported before Deals so that line items can reference product records by ID during Deal migration. If the customer uses Freshsales CPQ for quotes, the CPQ license flag is noted and the customer is advised to evaluate Twenty's third-party quoting integrations or custom object setup for quote management.

Freshsales custom fields (plan-gated: basic on Growth, advanced on Pro and Enterprise) map to Twenty's customizable field system. We read all custom field definitions from the Freshsales API during scoping, then pre-create matching fields in Twenty before data import. Field types are mapped: text fields to text, number fields to number, date fields to date, dropdown fields to select or multi-select, and checkbox fields to boolean. Custom field values migrate as values, not as field definitions. If a Freshsales custom field uses an advanced type only available on Pro or Enterprise, we flag it for review during scoping.

Freshsales Tasks map to Twenty Tasks with subject, status, due date, and owner preserved. Freshsales Events (calendar appointments) map to Twenty Tasks with a meeting type flag since Twenty does not have a native Event object. Call logs from Freshsales telephony migrate as Twenty Tasks with a call type flag and duration field. We resolve task assignees by email match against the Twenty workspace member list. Event attendees are noted in the task description field.

Freshsales file attachments are associated with Contact, Account, and Deal records. Twenty does not natively support file attachment imports via CSV. We flag every attachment with its source URL (from Freshsales), record association, file name, and size in a migration inventory. Customers have three options: re-upload manually post-migration, use the Freshsales API to download attachments and push them to Twenty's storage layer via a custom script, or engage FlitStack AI for an assisted API-based attachment migration. We do not include manual re-uploads in standard scope but document the process.

Territory management is a Pro-tier feature in Freshsales. Territory assignments do not map to a native Twenty object because Twenty does not have a territories module. We preserve territory data as a custom field (territory__c) on the relevant Person and Opportunity records during migration. If the customer relies heavily on territory-based assignment rules, we document the territories as a named-values list and advise on using Twenty's filter views and bulk assignment capabilities as a manual workaround.