Migrate from LeadPrime to Salesforce Sales Cloud

LeadPrime Lead records map directly to Salesforce Lead. Standard fields (Name, Email, Phone, Company, LeadSource, Status) migrate 1:1. Lead Owner from LeadPrime maps to Salesforce Lead OwnerId via User email lookup. Any Lead Distribution Rule assignment (rep assigned via Round Robin or Shark Tank) is preserved in a custom field lp_original_owner__c before reassignment in Salesforce, since Salesforce Assignment Rules will handle routing going forward.

LeadPrime Contact records map to Salesforce Contact. The mapping includes name fields, email, phone, and any custom properties. Contact.OwnerId resolves via email match against the Salesforce User table. If the Contact originated from a LeadPrime Lead conversion, we preserve the lp_lead_id__c reference in a custom field for audit trail. Contacts without an AccountId are flagged in reconciliation because Salesforce requires the Account-Contact hierarchy.

LeadPrime Company records map to Salesforce Account. Company name becomes Account Name; industry, size, website, and address fields map to standard Account fields. The Company is created before Contact migration so that AccountId is available to satisfy the Contact.Lookup relationship. Custom fields on LeadPrime Company migrate to custom Account fields of equivalent Salesforce data type.

Each LeadPrime Pipeline maps to a Salesforce Opportunity Record Type with a corresponding Sales Process that scopes the valid stage values. We export the full pipeline topology (stage names, sequence, probabilities) from LeadPrime and recreate it in Salesforce during schema design. The pipeline names become Record Type labels; stage probabilities become StageProbability values rounded to the nearest integer.

LeadPrime Pipeline Stage names map to Salesforce Opportunity Stage values under the corresponding Sales Process. Stage probability percentages migrate from LeadPrime to Salesforce StageProbability. If LeadPrime stages have conditional routing triggers, we document them in the routing rules inventory for manual rebuild in Salesforce Flow or Omni-Channel.

LeadPrime Deal records map to Salesforce Opportunity. Deal name becomes Opportunity Name; deal value maps to Amount; pipeline stage maps to the Salesforce StageName under the matching Sales Process; owner maps via email-to-User lookup. If LeadPrime Deals reference a Contact or Company, we resolve the AccountId and ContactId references during migration. Closed-Won and Closed-Lost dates migrate to Opportunity CloseDate and StageName.

LeadPrime User records representing sales reps, admins, and managers map to Salesforce User records by email match. Active/inactive status and role assignments are preserved. Any LeadPrime User without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before production migration proceeds. OwnerId lookups on Lead, Contact, Account, and Opportunity require this resolution.

LeadPrime Round Robin, Blind, Shark Tank, and Hybrid distribution rules are stored as configuration rather than data records. We export the full rule definitions during scoping — rep pools, capacity constraints, territory assignments, daily caps, and assignment logic — and deliver a written routing rules inventory. This document is used by the customer's Salesforce admin to rebuild equivalent Assignment Rules in Salesforce Setup or configure Omni-Channel routing. No rule engine migrates verbatim to any destination platform.

LeadPrime call logs migrate to Salesforce Task with TaskSubtype = Call. Call disposition, duration, and any notes attached to the call in LeadPrime map to custom Task fields. ActivityDate is set to the original LeadPrime timestamp to preserve timeline ordering. WhoId resolves to the migrated Lead or Contact; WhatId resolves to the related Account or Opportunity.

LeadPrime email logs migrate to Salesforce EmailMessage records (body and headers) linked to a Task for the activity timeline entry. The EmailMessage is linked to the target Lead or Contact via WhoId and to the related Account or Opportunity via WhatId. Subject line and sent date map to Salesforce EmailMessage standard fields. If an undocumented API is available at discovery, we attempt API-based export; otherwise we use available CSV export with field mapping to EmailMessage structure.

LeadPrime notes migrate to Salesforce Note records linked via ContentDocumentLink to the parent Lead, Contact, Account, or Opportunity. Note body migrates as plain text. If LeadPrime supports rich-text notes or attachments, these migrate as separate ContentDocument records with the appropriate ContentDocumentLink.

Custom fields on LeadPrime Lead, Contact, and Company objects are inventoried during scoping. We read the full field list and map each to an equivalent Salesforce field type (text, number, date, picklist, checkbox, etc.). Custom fields are pre-created in the Salesforce Sandbox before migration testing. If LeadPrime uses a field type not natively supported in Salesforce, we document the transformation approach during scoping.

LeadPrime tags are flat label structures applied across records. We migrate all tag assignments per contact or lead. Where Salesforce uses a hierarchical taxonomy or a different labeling system, we flatten the tag list and migrate to a multi-select picklist on the target object. The customer selects the target strategy during scoping.

Lead Finder Credits are a billing token in LeadPrime's credit economy and do not represent contact records or enrichment data. They do not migrate. We confirm the credit balance at cutover, flag it in the migration report, and recommend the customer download their credit purchase history separately for financial records. Any enrichment results already written to lead records (verified emails, phone numbers) migrate as part of those records because they are data, not billing tokens.