Migrate from Reach to Salesforce Sales Cloud

Reach Contacts map to Salesforce Lead or Contact depending on the status and stage columns present in the export. We infer qualification status from any pipeline, stage, or lifecycle columns in the export and apply the split rule during the transform phase. Any status column not matching a known Salesforce Lead Status is mapped as a custom picklist value. The original Reach status value is preserved in a custom field reach_original_status__c on both Lead and Contact for audit continuity.

Reach's undocumented field model means we discover custom properties only at export time by comparing the full column set of the export against a baseline Reach contact export. Each column not matching a known Salesforce standard field is treated as custom and mapped to a typed Salesforce custom field (Text, Number, Picklist, Date, etc.) on the appropriate object. We pre-create these fields in the destination Salesforce org during the schema design phase before any data loads begin.

If Reach stores company information as contact-level properties (company name, website, industry, address), we extract these into a normalized staging table and create Salesforce Account records before the Contact import. Each unique company value becomes one Account record; contacts are linked via AccountId Lookup after Account creation. This N:1 merge is resolved during the transform step before the Account load phase.

Reach's tagging and label functionality is implied by content management workflows mentioned in reviews. Any tag-equivalent column in the export (comma-separated values or multi-select format) is mapped to a Salesforce multi-select picklist on Contact or Lead. If tags are used for content classification, we map them to Salesforce Topics with TopicAssignment records. The customer chooses the tag strategy during scoping.

Reach stores media assets tied to contacts or accounts for multi-screen content management. We extract these as ContentVersion records (file binary) and create ContentDocumentLink records linking to the parent Contact or Account. Playlist metadata (name, sequence, schedule) is stored as a custom ContentPlaylist__c object with child ContentPlaylistItem__c records. We document the full playlist structure as a written inventory and do not migrate the actual media files unless the customer provides direct file access.

Reach Enterprise tier documents a seat-license model with reassignable admin accounts. User records (name, email, role, status) are extracted from the export or from the license management portal and mapped to Salesforce User records by email match. Any Reach user without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before Contact import resumes, because OwnerId is a required reference on most standard Salesforce objects.

If the Reach export includes engagement timestamps, call disposition, or activity history columns, these migrate to Salesforce Task (TaskSubtype=Call for phone interactions), Event (for meetings), and EmailMessage (for email content) linked to the parent Contact or Lead. Activity ordering is preserved by setting ActivityDate to the original Reach timestamp. We use the Salesforce Bulk API 2.0 with batch chunking and exponential backoff on API limit responses for large activity volumes.

Reach note records migrate to Salesforce Note objects linked via ContentDocumentLink to the parent Contact, Lead, or Account. Note body migrates as plain text with any embedded media preserved as separate ContentDocument records. Rich-text formatting is converted to Salesforce's rich-text subset during transform.

If the Reach export reveals an undocumented record type beyond Contact (implied by reviews referencing custom workflows and business-specific data), we create a Salesforce custom object with matching API name (with __c suffix), pre-create all inferred custom fields during schema design, and establish any implied lookup relationships to Contact or Account before loading the custom object as the final import phase.

If the Reach export includes support tickets or issue records, these map to Salesforce Case if the destination org includes Service Cloud. Ticket pipeline becomes Case Record Type; ticket stages become Case Status values; ticket conversations migrate as EmailMessage records linked to the Case. Case Origin maps from the Reach ticket source channel.

If Reach contains product or service records referenced in contact or deal data, these migrate to Salesforce Product2 with Standard Price Book entries. ProductCode maps from any Reach SKU field. The Pricebook2 reference is resolved at migration time to the customer's active Pricebook before PricebookEntry records are created.

Reach's CSV export includes system-level timestamps (record creation date, last modified date, export run ID) that we preserve as custom Salesforce fields (reach_created_date__c, reach_modified_date__c, reach_export_id__c) on every migrated object. These fields provide audit continuity and allow the customer's admin to identify which records were migrated from Reach versus created natively in Salesforce after cutover.