Migrate from UPilot to Salesforce Sales Cloud

UPilot's 360-degree contact view stores all contact data in a single object with company association and task context embedded. Salesforce splits unqualified prospects into Leads and qualified buyers into Contacts attached to Accounts. We define the split rule during scoping based on the customer's contact lifecycle, apply it during transformation, and preserve the original UPilot contact record ID in a custom field upilot_contact_id__c on both Lead and Contact for audit and cross-reference.

UPilot Company records map directly to Salesforce Account. Company name becomes Account Name, website becomes Website, and industry becomes Industry (mapped from UPilot's industry taxonomy to Salesforce's picklist values). Account is created before any Contact import so that AccountId lookup is satisfied at the moment of Contact insert.

UPilot Deals map to Salesforce Opportunity. Deal value maps to Amount, expected close date maps to CloseDate, and deal stage maps to StageName. UPilot's pipeline assignment maps to a Salesforce Record Type that we configure before migration. Multiple Contacts per Deal migrate as OpportunityContactRole records with their role assignments preserved.

UPilot's color-coded pipelines with customizable stages map to Salesforce Record Types on Opportunity, each paired with a Sales Process that whitelists the relevant stage values. Stage probability percentages migrate from UPilot to Salesforce StageProbability. Stage names are mapped individually during discovery to account for UPilot's flexible stage naming.

UPilot Tasks migrate to Salesforce Task with Status, Priority, and ActivityDate preserved. Task assignment resolves UPilot owner references to Salesforce OwnerId via the User mapping. The critical mapping decision is whether tasks attach to the Contact record (WhoId) or the related Opportunity (WhatId) based on the task's original context in UPilot's 360-degree view.

UPilot Support Tickets migrate to Salesforce Case if the destination org includes Service Cloud. Ticket pipeline becomes Case Record Type, ticket stages become Case Status values, and conversation threads migrate to EmailMessage records linked to the Case. Ticket priority maps to Case Priority.

UPilot custom fields on standard objects map to Salesforce custom fields with type-appropriate field types (text, number, picklist, date, checkbox). We pre-create the destination schema before any data import, including all custom fields, validation rules, and required flags that may differ between UPilot and Salesforce type definitions.

UPilot includes forecast projection tied to pipeline stages with custom probability weights. Salesforce calculates forecast differently using Opportunity Stage Probability and Forecast Category. We extract UPilot's stage-level forecast data and map it to custom numeric fields on Opportunity so that historical forecast assumptions remain visible for reporting.

UPilot's two-way email sync maintains conversation threads linked to Contact records. We disable sync before export to prevent orphaned threads. Migrated emails land as Salesforce EmailMessage records linked to a Task for the activity timeline. Email addresses and conversation continuity are preserved by matching on Contact email and thread date range.

UPilot stores Company-Contact as a direct relationship within the contact record. Salesforce requires Contact to have an AccountId lookup. We resolve the Account reference during migration by matching the contact's associated company name to the migrated Account record.

UPilot lead source data migrates to Salesforce LeadSource field on Lead and Contact. Marketing campaign attribution stored in UPilot migrates to Salesforce Campaign and CampaignMember if the customer is migrating marketing data in scope.

UPilot marketing campaign associations migrate to Salesforce Campaign if the customer includes marketing data in migration scope. Campaign type, status, and target audience map directly. Campaign Member history (which contacts were in which campaigns) migrates to CampaignMember records. Workflow-based marketing automation requires separate rebuild documentation.