Migrate from Pro-Sales CRM to Salesforce Sales Cloud

Pro-Sales CRM stores all people records as Contacts with a lifecycle stage property. We split these at migration time: Contacts with an unqualified lifecycle stage (New, Prospect, Marketing Qualified) map to Salesforce Lead; Contacts with a qualified stage (SQL, Opportunity, Customer) map to Salesforce Contact and are linked to a parent Account. We preserve the original Pro-Sales CRM lifecycle stage in a custom field prc_original_lifecycle__c on both Lead and Contact for audit and reporting continuity.

Pro-Sales CRM Company records map directly to Salesforce Account. Company domain becomes the Account Website field; industry and size fields map to typed Salesforce Account fields. Account is created before any Contact import so that the AccountId Lookup is satisfied at the moment of Contact insert. We use the Company record ID as the dedupe key to prevent duplicate Accounts if multiple Pro-Sales CRM accounts share the same domain.

Pro-Sales CRM Deals map to Salesforce Opportunity. Deal value, close date, stage name, and owner assignment migrate directly. The Pro-Sales CRM deal stage name is resolved against the stage mapping table created during discovery and mapped to a Salesforce StageName value on the corresponding Sales Process. Loss reason and win reason from Pro-Sales CRM custom fields become Salesforce Loss Reason and Win Reason fields.

Pro-Sales CRM allows custom stage names and probability weights per stage, and these vary by customer configuration. We extract the active stage configuration from the source account during discovery, map each Pro-Sales CRM stage to a Salesforce StageName within a Sales Process, and set StageProbability to match the source weight rounded to the nearest integer. The Sales Process is deployed to Sandbox for validation before production migration.

Pro-Sales CRM call logs (built-in call routing and dispositioning) map to Salesforce Task with TaskSubtype set to Call. Call disposition value, duration, and any associated notes migrate to custom Task fields. ActivityDate is set to the original Pro-Sales CRM timestamp. Calls are imported after Contact and Account records so that the WhoId and WhatId lookups are resolved at import time.

Pro-Sales CRM notes map to Salesforce Note records. Note body migrates as rich text. We link each Note to its parent record via ContentDocumentLink with the LinkEntity set to the migrated Contact, Account, or Opportunity ID. Note timestamps are preserved as ActivityDate on the Salesforce Note record.

Pro-Sales CRM task completion records (status, priority, due date, owner) map to Salesforce Task. Status values (Open, Completed, Overdue) are mapped to Salesforce Task Status values (Not Started, Completed, Overdue) using a translation table defined during discovery. Owner assignment requires a resolved Salesforce User ID, which depends on the Owner reconciliation step completing first.

Pro-Sales CRM custom fields on Contact records are created as typed Salesforce custom fields on Contact before migration. We inspect the Pro-Sales CRM field list during discovery, create matching __c fields in Salesforce with the correct data type (text, number, date, picklist), and add them to the relevant Page Layout. Custom field order and section placement are documented in the mapping spec for the customer's admin to finalise.

Pro-Sales CRM custom fields on Deal records are created as typed Salesforce custom fields on Opportunity before migration. Field types are mapped: text to Text(255), numeric values to Number, dates to Date, and picklist-like fields to Picklist or Multi-Select Picklist depending on whether the source field allows multiple values.

Pro-Sales CRM tag assignments on records migrate to Salesforce as either a multi-select picklist field on the relevant object (Contact, Account, or Opportunity) or as Salesforce Topics with TopicAssignment records. The customer selects the tag strategy during scoping. Tag strings are preserved verbatim; the destination field is provisioned with enough picklist value capacity to hold all distinct tags from the source account.

Pro-Sales CRM assigns a single owner per Contact, Company, and Deal record. We resolve each owner by email match against the destination Salesforce org's User table. Owners without a matching Salesforce User are flagged in a reconciliation queue before record migration begins; the customer's Salesforce admin provisions missing Users before we resume. Unmapped owners after provisioning are assigned to a designated fallback User and flagged in the migration report.

Active Pro-Sales CRM user records are mapped to Salesforce User records. Role and permission differences between the platforms mean the mapping is functional rather than a direct permission copy. Pro-Sales CRM role names are preserved in a custom field prc_source_role__c on the Salesforce User for admin reference. The customer provisions Salesforce Users and licenses before migration; we validate that each Pro-Sales CRM user has a corresponding Salesforce User before proceeding.