Migrate from InTouch CRM to Salesforce Sales Cloud

InTouch Contacts map to either Salesforce Lead or Contact based on qualification status. We define the split rule during scoping using InTouch properties (contact status, pipeline membership, any lead score field). Unqualified contacts map to Salesforce Lead; contacts with associated Deals or stage progression map to Salesforce Contact tied to an Account. The original InTouch contact status is preserved in a custom field intouch_original_status__c on both Lead and Contact for audit and reporting continuity.

InTouch Company records map directly to Salesforce Account. The company name becomes the Account Name; any domain or website field becomes Account Website. Account is created before any Contact import so that the AccountId Lookup is satisfied at the moment of Contact insert. Companies with no name are flagged during extraction for customer review before Account creation.

InTouch Deals map to Salesforce Opportunity. Each InTouch Pipeline maps to a Salesforce Record Type with a corresponding Sales Process. The InTouch deal stage label is remapped to a Salesforce StageName value defined in the target Sales Process. Deal amount, close date, and owner migrate directly. Closed-Lost and Closed-Won states from InTouch are preserved in custom fields for reporting continuity.

Each InTouch Pipeline becomes a Salesforce Record Type on Opportunity, with its stage values defined as picklist entries in a dedicated Sales Process. We preserve stage probability percentages from InTouch by mapping to StageProbability on each stage. The customer selects which InTouch Pipelines become Salesforce Record Types during scoping; Pipelines can also be consolidated into a single Record Type if the customer prefers fewer sales processes.

InTouch Pipelines (the top-level container for stages) map to Salesforce Record Types. Each Record Type gets its own Page Layout and Sales Process. Multiple InTouch Pipelines with similar stage semantics can be consolidated into one Record Type at the customer's choice to reduce admin overhead in Salesforce.

InTouch Activities (calls, emails, meetings, tasks, notes) are extracted via CSV and classified by type at transform time. Call activities map to Task with TaskSubtype=Call and CallDurationInSeconds in a custom field. Email activities map to Salesforce EmailMessage (body) linked to a Task (timeline entry). Meeting activities map to Event with StartDateTime and EndDateTime preserved. Task activities map to Task. All activities link to the parent Contact or Deal via WhoId and WhatId resolved through the Account-Contact lookup chain. Bulk API 2.0 handles the activity load with chunking and exponential backoff.

InTouch custom fields on Contacts, Companies, and Deals map to Salesforce custom fields on the equivalent object. Field type mapping follows the destination schema: text fields map to Text, numeric fields to Number, date fields to Date, checkbox fields to Checkbox, and picklist fields to Picklist or Multi-Select Picklist. Custom fields are pre-created in Salesforce with __c suffix and matching field-level security before migration begins. InTouch pipeline-specific custom fields are mapped to the appropriate Record Type.

InTouch Owners map to Salesforce User records by email match. Any InTouch Owner without a matching Salesforce User is held in a reconciliation queue. The customer's Salesforce admin provisions missing Users (active or inactive depending on whether the original InTouch user remains active). OwnerId references are required on Opportunity and Contact; migration pauses at this step if owners cannot be resolved.

InTouch custom fields scoped to a Pipeline map to Salesforce custom objects if the customer has defined a multi-table relationship. We pre-create the destination schema including all custom fields, lookup relationships to Account or Contact, and validation rules before any data import. Custom object naming follows the InTouch API name with a __c suffix per Salesforce convention.

InTouch Notes attached to Contacts, Companies, or Deals migrate to Salesforce Note records linked via ContentDocumentLink to the parent record. Note body migrates as rich text; any embedded file references are flagged for the customer to re-attach post-migration if they are stored outside InTouch.

Email addresses on InTouch Contact and Company records map to standard Salesforce email fields. Duplicate email addresses across multiple records are flagged during extraction for the customer to resolve before insert because Salesforce enforces Email uniqueness at the Contact level (configurable). The customer decides whether to allow duplicate emails or consolidate before migration.

InTouch activity timestamps and deal close dates are preserved as Salesforce ActivityDate on Task and Event, and as CloseDate on Opportunity. CreatedDate and LastModifiedDate on migrated records reflect the migration load date by default; if the customer requires original InTouch creation timestamps, we set them via the Salesforce API before final commit, subject to admin approval.