Migrate from OnePageCRM to Salesforce Sales Cloud

OnePageCRM Contacts map to Salesforce Leads (unqualified prospects) or Contacts attached to Accounts (qualified buyers). We design the split rule during scoping based on the contact's status in OnePageCRM (e.g., Prospect, Customer, Inactive) and the customer's business definition of qualified. The original OnePageCRM status is preserved in a custom field opc_status__c on both Lead and Contact for audit and reporting continuity.

OnePageCRM Organization records map directly to Salesforce Account. The organization's name, phone, address, and custom fields migrate to the Account object. Organization is the parent of the Contact in OnePageCRM, and we maintain that relationship by creating the Account first and resolving the AccountId on each Contact during the Contact import phase.

OnePageCRM Deals map to Salesforce Opportunity. Each Deal's associated Contact becomes the Opportunity's Account lookup (via the Organization-to-Account mapping), and the Deal owner maps to the Salesforce User. Deal amount, close date, pipeline, stage, margin, commission, and cost migrate to Opportunity standard and custom fields. We configure Salesforce Record Types and Sales Processes before migration so that the Deal pipeline becomes a named Sales Process in Salesforce.

OnePageCRM Business tier supports multiple pipelines and Kanban views. We convert each OnePageCRM pipeline to a Salesforce Record Type on Opportunity, with a corresponding Sales Process that whitelists the relevant stage values. Stage probability percentages migrate from OnePageCRM to Salesforce StageProbability, with rounding to Salesforce-allowed integers.

OnePageCRM statuses (Prospect, Qualified, Customer, etc.) are pre-populated but editable per organisation. We capture the full status taxonomy during scoping, map each status to a Salesforce Lead Status value or a Contact custom field, and document the mapping so the customer's admin can adjust Salesforce picklist values before import. The mapping preserves the sales-stage meaning for reporting continuity.

OnePageCRM Lead Sources (website inquiry, phone call, referral, etc.) are pre-populated and editable per org. We preserve lead source as a contact property, mapping to Salesforce LeadSource on Lead and Contact. Any OnePageCRM lead source values not present in Salesforce are added as new picklist values before import.

OnePageCRM's Next Action field is a first-class contact property with a date and descriptive text. This has no direct Salesforce equivalent because Salesforce separates date (ActivityDate) and description (Subject, Description) into separate Task fields. We replay Next Action records as Salesforce Tasks linked to the Contact or Account, with the original Next Action date as ActivityDate and the Next Action text as Subject and Description. This preserves the sales rep's prioritised follow-up queue within Salesforce's activity timeline.

OnePageCRM Predefined Items represent products or services used in Deal creation. They support name, price, quantity, and grouping. We map these to Salesforce Product2 records and create Standard Price Book entries during import, preserving product codes from the opc_sku field where populated.

OnePageCRM Predefined Actions are saved task templates that users assign to contacts. We do not migrate Autoflow workflows or Predefined Actions as code because Salesforce Flow and OnePageCRM Autoflow are different automation models with incompatible trigger/action architectures. Instead, we deliver a written inventory of every Predefined Action template with its task sequence, conditions, and recommended Salesforce Flow equivalent for the customer's admin to rebuild.

OnePageCRM notes and call logs attached to contacts are included in the contacts export dataset. We replay call logs as Salesforce Task records with TaskSubtype = Call, preserving call disposition and duration in custom Task fields. Notes migrate as Salesforce Note records linked via ContentDocumentLink to the parent Contact or Account. Note ordering is preserved by ActivityDate. We do not migrate email body content (see email content gotcha).

OnePageCRM tags are assigned to contacts and can also apply to deals. We carry flat tags through as a Salesforce multi-select picklist on Contact if the tag set is small (under 30 unique tags) and manageable as a picklist. For large or unbounded tag sets, we recommend Salesforce Topics with TopicAssignment records, or a custom field. The customer chooses tag strategy during scoping.

Admin-created custom fields on OnePageCRM contacts, organizations, and deals map to Salesforce custom fields on the equivalent destination object. We pre-create the destination schema (all __c custom fields, field types, and validation rules) in a Salesforce Sandbox before any data import. Field types that do not map directly (e.g., OnePageCRM multi-select arrays that exceed Salesforce picklist limits) are flagged during scoping with a recommended transformation or drop decision.