Migrate from SalesPro CRM to Salesforce Sales Cloud

SalesPro Contact records map directly to Salesforce Contact. The primary fields — Name, Email, Phone, Company association — map to FirstName, LastName, Email, Phone, and AccountId respectively. We resolve the AccountId reference by querying the Salesforce Account created from the corresponding SalesPro Company record. Permission-based sharing flags from SalesPro map to Salesforce manual sharing rules or Territory fields if the customer has Territory Management enabled.

SalesPro Company records map to Salesforce Account. The Company Name becomes Account Name, and the associated domain or website field maps to Account Website. We use Company record ID as the dedupe key during import to prevent duplicate Accounts. Account is imported before Contact so that AccountId is available on the Contact insert.

SalesPro Events — which contain date ranges, group size, venue details, and BEO references — map to Salesforce Event for scheduling purposes and optionally to Opportunity if the Event represents a revenue-bearing booking. We preserve the event timeline as structured milestones by mapping SalesPro Milestone records to Salesforce Task or a custom Milestone__c object depending on the customer's reporting needs. The original Event-to-BEO linkage is preserved via a lookup field that we reconstruct in Salesforce.

BEO records are derived outputs in SalesPro, auto-generated from Event data with cost calculations, timeline details, and event specifications. They do not exist as standalone records in the source schema. We reconstruct them as a Salesforce custom object BEO__c with fields for Event__c (lookup to the mapped Event), Cost__c, Timeline__c, Specs__c, and SigningStatus__c. The custom object is pre-created in the Salesforce org before migration begins, including all fields, lookup relationship, and page layout. The Event-to-BEO linkage is preserved explicitly via the lookup.

SalesPro Tasks map to Salesforce Task with Subject, Status, Priority, ActivityDate, and Description preserved. Assignee resolution maps the SalesPro user reference to Salesforce OwnerId via email lookup against the destination User table. Tasks without a matching User are placed in a reconciliation queue for the customer's admin to provision before Task import proceeds.

SalesPro Milestones are tied to the pipeline or individual deals and support custom definitions per sales cycle. We map them to Salesforce Task records with a Milestone__c custom flag if the customer reports milestones as activity-level checkboxes, or to a Milestone__c custom object with a lookup to Opportunity if milestones represent deal-stage gates. The customer chooses the strategy during scoping.

SalesPro pipeline stages map to Salesforce Opportunity StageName values, and the pipeline itself maps to a Salesforce Record Type on Opportunity. Each Record Type gets a corresponding Sales Process that whitelists the stage values. Stage ordering and probability percentages migrate from SalesPro to Salesforce StageProbability, rounded to Salesforce-allowed integer values.

SalesPro Users assigned to Contacts, Tasks, and Events are resolved by email match against the destination Salesforce User table. We flag any SalesPro User with no matching Salesforce User for admin provisioning before record import. Owner reassignment during migration requires explicit admin sign-off because Salesforce OwnerId is a required field on most standard objects.

SalesPro calendar entries map to Salesforce Event with StartDateTime, EndDateTime, Subject, and Location preserved. Resource assignments on SalesPro calendar records map to Salesforce EventRelation records linking the Event to the relevant Contacts and Users. Note that the webhook API only fires on calendar view opens, so calendar export depends on the Leap Digital data export delivery.

SalesPro's People Tracker live-dashboard data — which captures real-time task completion and deal milestone progress — is treated as time-stamped Activity records. Each People Tracker entry migrates as a Salesforce Task with ActivityDate set to the original tracker timestamp, Subject reflecting the tracked action, and a custom field people_tracker_source__c set to true for audit traceability.

SalesPro does not expose a bulk attachment export endpoint via its webhook API. Attachments associated with Events, BEOs, or Contacts cannot be programmatically retrieved. We notify customers during scoping that attachment migration requires manual export from SalesPro, and we provide a structured template for customers to deliver files to us for upload into Salesforce ContentDocument via the REST API. ContentDocumentLink associates each file to its parent record (Contact, Account, Event, or BEO__c) post-upload.

SalesPro tenants frequently use custom fields on Contact, Company, and Event records for industry-specific data. We audit the exported schema from the Leap Digital data delivery and create matching Salesforce custom fields on the corresponding objects before record import begins. Field types are mapped: text to Text, dates to Date, numbers to Number, dropdowns to Picklist with the source values whitelisted as valid Salesforce picklist values.