Migrate from InTouch to Salesforce Sales Cloud

InTouch contacts split based on their deal association and status. Contacts linked to closed-won or closed-lost deals in InTouch route to Salesforce Contact under the primary Account. Contacts without deal history route to Salesforce Lead. The split decision is made during migration validation against InTouch's contact properties and deal association table.

InTouch organizations map directly to Salesforce Account records, preserving the organization name, domain, industry, employee count, and annual revenue data as standard Account fields. Organization hierarchies where a parent organization has child sub-organizations in InTouch map to the Salesforce ParentId lookup on Account, enabling account hierarchy reporting. For InTouch contacts that lack a primary organization assignment, FlitStack creates a default 'Unassigned Account' placeholder record before migration begins, ensuring every contact has a valid AccountId rather than remaining orphaned.

InTouch deals map directly to Salesforce Opportunity records using a field-by-field mapping approach. The deal name becomes Opportunity.Name, the deal amount maps to Opportunity.Amount, and the close date transfers to CloseDate. The stage value requires careful value-by-value mapping against the Salesforce stage pick-list defined on the Opportunity's RecordTypeId, ensuring the InTouch stage name matches the correct Salesforce stage label for the appropriate sales process.

Each InTouch pipeline transforms into a Salesforce Sales Process linked to a specific RecordTypeId. Before migration execution, FlitStack delivers a comprehensive record-type setup plan that documents which RecordTypeId values your team needs to create in Salesforce, which stage pick-list values should belong to each Sales Process, and the order of stage progression for forecasting accuracy. Your Salesforce admin creates these elements during the pre-migration schema phase.

InTouch stage names map value-by-value to Salesforce Opportunity Stage pick-list values, with each InTouch stage matched to its corresponding Salesforce stage label under the appropriate RecordTypeId. Probability percentages from InTouch are re-applied per Salesforce stage configuration, and the Forecast Category (Commit, Best Case, Omitted) is set according to the stage mapping defined in the Sales Process. For organizations using HubSpot-style entered-timestamp tracking, custom datetime fields are required.

InTouch calls and emails are migrated as Salesforce Task records with the Type field set to 'Call' or 'Email' respectively. The Task.Subject field carries the original activity title from InTouch, Task.Description preserves the full body text or notes, and Task.ActivityDate transfers the original timestamp to maintain historical activity records. The OwnerId is resolved by matching the InTouch owner email address to the corresponding Salesforce User record.

InTouch meeting records map to Salesforce Event objects, preserving Event.Subject from the meeting title, Event.StartDateTime from the scheduled start, Event.EndDateTime from the scheduled end, and Event.Location from the venue or call-in details. The OwnerId on each Event follows the same email-match resolution logic used for Tasks, ensuring the calendar event appears in the correct Salesforce user's activity timeline after migration completes.

InTouch notes migrate as Salesforce Notes (Lightning Experience format, not legacy Note object). Note.Title is set from the InTouch note subject; Note.Body carries the full note text. Notes linked to specific InTouch contacts or deals carry the corresponding Salesforce WhatId or WhoId after migration.

InTouch custom fields per matter template require pre-created Salesforce custom fields. FlitStack generates a field creation manifest with label, API name (__c suffix), data type, and pick-list values where applicable. Custom fields are created before data migration runs so the target schema exists at insert time.

InTouch owner IDs are resolved by email match against Salesforce User records. Matched owners map directly to OwnerId. Unmatched owners are flagged before migration with a fallback owner assignment option — either a designated Salesforce admin or a placeholder user created for unmapped records.

InTouch file attachments are re-uploaded to Salesforce as ContentVersion records linked to the parent object (Account, Contact, or Opportunity). File size limits apply: Salesforce default is 25MB per file. Inline images in InTouch notes are extracted, downloaded, and rehosted as Salesforce Files.

InTouch contact tags have no direct Salesforce equivalent. Tags are migrated as a custom multi-select pick-list field (Source_Tags__c) on the Contact or Lead object. If InTouch tags represent segmentation used for marketing, Campaign Member records are created with the tag name as Campaign.CampaignName.