Migrate from Tango CRM to Freshsales

Tango CRM Contact records map to Freshsales Contact with standard fields (first_name, last_name, email, phone, address). Email address serves as the merge key to prevent duplicate records during import. Any custom fields present on Contact require explicit type-mapped equivalents in Freshsales. Without a confirmed public API for Tango CRM, extraction relies on CSV export where available or browser-based record capture, which may limit field coverage to standard fields only.

Tango CRM Company records map to Freshsales Account. Company name becomes the Account Name field; industry, size, website, and address fields map to their Freshsales equivalents. Account records are imported before Contact records so that the AccountId lookup is satisfied at the time of Contact insert. Domain-based matching is used as a secondary dedupe strategy where company website domain is populated.

Tango CRM Deal records map to Freshsales Deal. Deal name, value, expected close date, owner, and stage transfer. Pipeline stage labels from Tango CRM do not map 1:1 to Freshsales deal stages — we produce a stage mapping worksheet during the mapping phase and reconcile labels at import time. Historical deal amounts and close dates are preserved independently of stage labels.

Tango CRM pipeline definitions (stage names, stage order, stage-level probabilities) are exported as configuration metadata. We configure Freshsales deal pipelines to match the source stage sequence. Each pipeline in Tango CRM becomes a separate Freshsales Deal Pipeline. Stage probability percentages are set on Freshsales stage configuration. This is a schema-configuration step, not a data migration step.

Activities logged against Contacts or Deals in Tango CRM transfer to Freshsales as Task or Event records depending on activity type (calls and tasks become Task; meetings become Event; notes become Note). Activity text, timestamps, and owner assignment are preserved. Without a bulk API confirmed on the source side, activity extraction is sequenced to avoid overwhelming the export pathway. Large activity volumes may require multiple extraction batches.

Free-text notes attached to Contacts or Deals in Tango CRM import as Freshsales Note records linked to the parent Contact or Account. HTML-formatted notes are stripped to plain text unless the destination supports rich-text note fields, which is configurable per the Freshsales plan tier.

Tags applied to Contacts or Deals in Tango CRM transfer as individual label values. Multi-select tag fields are split into separate values during the transformation step. In Freshsales, tag values map to custom multi-select picklist fields or to standard Tags, depending on the customer's preferred organization method chosen during scoping.

Custom properties on Contacts, Companies, and Deals require explicit field-level mapping. Field types (dropdown, date, number, text) are matched to Freshsales equivalent field types. Dropdown fields need a value mapping where source picklist values differ from Freshsales picklist values. We pre-create all required custom fields in Freshsales before any data import begins to avoid import failures due to missing destination fields.

Tango CRM users and record owners map by email address to Freshsales User accounts. We extract every distinct owner email referenced on Contact, Company, Deal, and Activity records and match against the Freshsales user roster. Any owner without a matching Freshsales User goes to a reconciliation queue for the customer's admin to provision before record import resumes.

If Tango CRM stores Products or Line Items associated with Deals, these map to Freshsales Product records. Product name, SKU, and pricing fields transfer. We create Standard Price Book entries for each product during the import phase so that line items can be associated with Deals at migration time.