Migrate from Results to Salesforce Sales Cloud

Results Contacts without a Company association or in a pre-qualification stage map to Salesforce Lead. Results Contacts attached to a Company and marked as active buyers map to Salesforce Contact tied to an Account. We compute the split during scoping based on the customer's Results instance configuration, apply it as the first transform during migration, and preserve the original Results contact status in a custom field results_contact_status__c on both Lead and Contact for audit trail integrity.

Results Company records map directly to Salesforce Account. The Company domain or website field becomes the Account's Website field and is used as the dedupe key during import. Account is created before any Contact import so that the AccountId Lookup relationship is satisfied at the moment of Contact insert.

Results Deals map to Salesforce Opportunity. The Results deal stage maps to Salesforce StageName, and the pipeline assignment maps to a Salesforce Sales Process or Record Type that we configure before migration. Deal value, close date, and owner migrate directly. Any Results custom deal fields map to custom Opportunity fields created in the destination org.

Each Results pipeline becomes a Salesforce Record Type with a corresponding Sales Process that whitelists the relevant stage values. Stage probability percentages migrate from Results to Salesforce StageProbability, rounded to the nearest integer allowed by the platform.

Results pipelines map to Salesforce Record Types on Opportunity. Each Record Type gets its own Page Layout and Sales Process so that stage values remain scoped per line of business. If Results supports multiple pipelines, each maps to a separate Record Type.

Results Products map to Salesforce Product2 records with Standard Price Book entries created during import. Product code or SKU migrates to ProductCode on Product2.

Results Line Items map to Salesforce OpportunityLineItem. We resolve the Pricebook2 reference, the Product2 reference, and the parent Opportunity at migration time. Quantity, UnitPrice, and TotalPrice migrate directly. If Results supports bundle or sub-line structures, we flatten them per the customer's preferred Salesforce data model.

Results Owners map to Salesforce User records by email match. Any Results Owner without a matching Salesforce User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive owners receive an inactive User with the correct email to preserve historical assignment.

Results email engagements migrate to Salesforce EmailMessage records (email content) linked to an Activity Task record (activity timeline entry). The WhoId on Task points to the Lead or Contact; WhatId points to the related Opportunity or Account. Email body and headers preserve with original timestamp.

Results call engagements map to Salesforce Task with TaskSubtype = Call. Call disposition, duration, and any recording URL transfer to custom Task fields. Activity timeline ordering is preserved by setting ActivityDate to the original Results timestamp.

Results meeting engagements map to Salesforce Event. StartDateTime, EndDateTime, and Location preserve. Attendee mapping links to EventRelation records pointing at the related Leads, Contacts, and Users. If Results stores meeting notes, those migrate as Task records linked to the Event.

Results Notes migrate to Salesforce Note records linked via ContentDocumentLink to the parent record (Lead, Contact, Account, Opportunity). Note body migrates as rich text. Any embedded images in Results notes are extracted and stored as separate ContentDocument records.

Results Task engagements map to Salesforce Task with Status, Priority, and ActivityDate preserved. Task assignment migrates by resolving the Results owner reference to Salesforce OwnerId via the User mapping. Open/closed status maps directly to Salesforce Task Status values.

Results Tickets migrate to Salesforce Case if the destination org includes Service Cloud or if the customer enables Cases on their Sales Cloud org. Ticket pipeline becomes Case Record Type, ticket stages become Case Status values, and ticket comments migrate as CaseComments linked to the Case.

Results custom fields map to Salesforce custom fields with equivalent data types. We verify field type compatibility during scoping (text vs. textarea, number vs. currency, date vs. datetime, single-select vs. picklist). Multi-select picklist values from Results become Salesforce multi-select picklists. Required field constraints on Results custom fields map to either required Salesforce fields or validation rules depending on the customer's preference.

Results custom objects migrate to Salesforce custom objects of equivalent API name. We pre-create the destination schema in Salesforce before any data import, including all custom fields, lookup relationships to standard objects (Account, Contact, Opportunity), and validation rules. Custom object naming follows Salesforce __c suffix convention matched to the Results object API name.

Results Attachments migrate to Salesforce ContentDocument records linked via ContentDocumentLink to the parent record (Contact, Account, Opportunity). We extract binary file content and metadata (filename, content type, size) and reconstruct them in Salesforce. If Results stores attachments inline within notes or activities, we extract and promote them to standalone ContentDocument records.

Results tags stored as multi-checkbox properties migrate to Salesforce multi-select picklist fields on the target object. Tags used for content classification migrate to Salesforce Topics with TopicAssignment records linked to the relevant object. The customer chooses the tag strategy during scoping based on reporting needs.