Migrate from Pipeline CRM to Salesforce Sales Cloud

Pipeline CRM People with early lifecycle stages (subscriber, lead) map to Salesforce Lead. People at later stages (opportunity, customer) map to Salesforce Contact attached to an Account. We compute the split at migration time using Pipeline CRM's lifecycle stage property and preserve the original stage in a custom field hs_original_lifecycle__c on both Lead and Contact for audit and reporting continuity.

Pipeline CRM Company records map directly to Salesforce Account. Company name is the dedupe key during import. We import Accounts first to establish the hierarchy that People and Deals reference. The Pipeline CRM company industry, size, revenue, and website fields map to standard Account fields; custom Company fields map to custom Account fields with __c suffix.

Pipeline CRM Deals map to Salesforce Opportunity. The Pipeline CRM deal stage property maps to Salesforce StageName, and the pipeline assignment maps to a Salesforce Record Type and Sales Process configured before migration. Deal value, close date, probability, and owner all migrate directly. Closed-Lost and Closed-Won reason fields from Pipeline CRM custom fields become Salesforce Loss Reason and Win Reason fields.

Each Pipeline CRM pipeline stage becomes a Salesforce StageName value within a Sales Process. Stage probability percentages migrate from Pipeline CRM to Salesforce StageProbability with rounding to the nearest integer allowed by the platform.

Pipeline CRM's multiple pipelines (up to 10 on Start, 20 on Develop, unlimited on Grow) map to Salesforce Record Types on Opportunity. Each Record Type gets its own Page Layout and Sales Process so that stage values stay scoped per line of business.

Pipeline CRM Activities log email, call, and meeting history linked to People or Companies. We export Activities as a flat list with the linked Person or Company reference and timestamp. Salesforce requires both a WhoId (Contact or Lead) and a WhatId (Opportunity or Account) on activity records, so we resolve AccountId from the related Company and Contact/Lead from the related Person before inserting.

Pipeline CRM assigns an owner to each Deal and Person. User records (name, email, role) export cleanly. We map Owner email in Pipeline CRM to the Salesforce User email field. Owners without a matching Salesforce User go to a reconciliation queue for the customer's admin to provision before record import resumes.

Pipeline CRM email engagements migrate to Salesforce EmailMessage records (the email content) linked to an Activity Task record (the timeline entry). The WhoId on Task points to the migrated Lead or Contact; WhatId points to the related Opportunity or Account. Email direction (inbound/outbound) and status migrate to Salesforce EmailMessage fields.

Pipeline CRM call engagements map to Salesforce Task with TaskSubtype = Call. Call duration, disposition, and recording URL transfer to custom Task fields. Activity timeline ordering is preserved by setting ActivityDate to the original Pipeline CRM timestamp.

Pipeline CRM meeting engagements map to Salesforce Event. StartDateTime, EndDateTime, and location preserve. Attendee mapping links to EventRelation records pointing at the migrated Leads, Contacts, and Users.

Pipeline CRM Notes migrate to Salesforce Note records linked via ContentDocumentLink to the parent record (Lead, Contact, Account, Opportunity). Note body migrates as rich text with image attachments preserved as separate ContentDocument records.

Pipeline CRM's Agenda system stores Tasks as separate record types. Agenda Tasks with a due date and assignee migrate directly to Salesforce Task with Status, Priority, and ActivityDate preserved. Task assignment migrates by resolving Pipeline CRM owner_id to Salesforce OwnerId via the User mapping.

Pipeline CRM Tags applied to People, Companies, and Deals migrate as label arrays. We map Tags to Salesforce multi-select picklist fields on the target object (Contact, Account, Opportunity) or to Salesforce Topics with TopicAssignment records, depending on the customer's preferred strategy for data segmentation.

Pipeline CRM custom fields are defined per object (Company, Deal, Person) and support text, dropdown, date, number, and checkbox types. We export the full field schema alongside data, create matching Salesforce custom fields with __c API names before data migration, and map field types to the closest Salesforce equivalent. Text becomes Text, date becomes Date, number becomes Number, dropdown becomes Picklist, and checkbox becomes Checkbox.