Migrate from Tango CRM to Salesforce Sales Cloud

Tango CRM Contact records are evaluated against the customer's qualification criteria (engagement history, deal association, or custom status field) to determine whether they land as Salesforce Lead or Contact. Unqualified contacts map to Lead; contacts with associated open Deals or historical activity map to Contact attached to an Account. We preserve the original Tango CRM contact identifier in a custom field tango_contact_id__c for audit and cross-reference.

Tango CRM Company records map directly to Salesforce Account. Company name becomes Account Name; industry and address fields map to typed Salesforce fields. The dedupe key during import is Account Name (fuzzy match) supplemented by domain match where available. Account is created before any Contact import so that AccountId is resolved at Contact insert time.

Tango CRM Deal records map to Salesforce Opportunity. Deal name becomes Opportunity Name; deal value maps to Amount; expected close date maps to CloseDate. The owner assignment resolves via email match against Salesforce Users. Closed-won and closed-lost status maps to Salesforce Opportunity Stage values defined in the Sales Process.

Tango CRM stage labels (e.g. Qualified, Proposal Sent, Negotiation) do not map 1:1 to Salesforce Stage values. We produce a stage mapping worksheet during the mapping phase that assigns each Tango CRM stage to a Salesforce StageName within a configured Sales Process, preserves stage order, and sets StageProbability percentages. Stage labels and probability values are reconciled at import time, not after.

Tango CRM pipeline configurations (stage sequence, stage labels, stage-level actions) map to Salesforce Record Types and Sales Processes. Each Tango CRM pipeline becomes a Salesforce Record Type on Opportunity, with a corresponding Sales Process that whitelists the migrated stage values and applies the correct probability matrix per stage.

Tango CRM email activities logged against Contacts or Deals migrate to Salesforce Task records (the activity timeline entry) with EmailMessage records (the email content) linked via the WhatId to the Opportunity or Account. The ActivityDate on Task preserves the original timestamp. Without a confirmed bulk email export endpoint, we sequence email migration using the confirmed export pathway identified during discovery.

Tango CRM call logs migrate to Salesforce Task with TaskSubtype = Call. Call duration and disposition text (if stored in a custom field) transfer to custom Task fields. Activity ordering is preserved by setting ActivityDate to the original Tango CRM timestamp. Owner resolution by email match applies to call records as to other activity types.

Tango CRM meeting records migrate to Salesforce Event with StartDateTime and EndDateTime preserved. Location maps to Event Location. If attendee data is available in the export, we create EventRelation records linking the meeting to the related Contacts, Leads, and Users. Event subject is derived from the meeting title in Tango CRM.

Tango CRM task records (follow-up items, to-dos) map directly to Salesforce Task. Task Status, Priority, and ActivityDate preserve from the source. Task assignment resolves via email-matching the owner to a Salesforce User. Open tasks are imported with Status = Not Started; completed tasks import with Status = Completed and CompletedDateTime set.

Free-text notes attached to Contacts, Companies, or Deals in Tango CRM migrate to Salesforce Note records linked via ContentDocumentLink to the parent record. HTML-formatted notes are stripped to plain text unless the destination org supports rich-text Note fields. Note timestamps are preserved as the CreatedDate equivalent.

Tags applied to Contacts or Deals in Tango CRM (stored as multi-value fields) split into individual label values during transformation. The migrated values write to a Salesforce multi-select picklist field on the target object. If the number of distinct tags exceeds Salesforce's multi-select picklist limit of 500 values per field, we create a custom text field and store tag arrays as delimited strings.

Tango CRM owners referenced on Contact, Company, and Deal records are resolved by email match against the Salesforce destination org's User table. Any Tango CRM owner without a matching Salesforce User is held in a reconciliation queue. The customer's Salesforce admin provisions missing Users before record import resumes. Role and permission sets are not transferred; they are rebuilt in Salesforce post-migration.

Custom properties on Tango CRM Contact records require explicit field-level mapping. Field types (dropdown, date, number, text, checkbox) are matched to Salesforce field types during the mapping phase. Dropdown fields need a value-mapping table where source values are reconciled against Salesforce picklist values. All custom Contact fields are pre-created in Salesforce before Contact import begins.

Custom properties on Tango CRM Company records map to Salesforce Account custom fields. Industry, employee count, annual revenue, and address custom fields follow the same type-matching approach as Contact custom fields. Company-level custom fields are deployed to Salesforce before Account import begins.

Custom properties on Tango CRM Deal records map to Salesforce Opportunity custom fields. Custom fields carrying deal-specific data (contract type, renewal date, product line, custom probability override) are pre-created in Salesforce with appropriate field types. All Opportunity custom fields must be deployed before the Deal-to-Opportunity import phase begins.