Migrate from PipelineManager to Salesforce Sales Cloud

PipelineManager Pipelines map to Salesforce Record Types on Opportunity. Each Pipeline's ordered Stage list becomes a Salesforce Sales Process whitelisted to that Record Type. Stage probability percentages migrate from PipelineManager to StageProbability on each OpportunityStage record. If the destination org already has Record Types configured, we append the PipelineManager pipeline as a new Record Type rather than overwriting existing ones.

PipelineManager Deals map to Salesforce Opportunity. The Deal's Pipeline assignment determines Opportunity.RecordTypeId, the stage name maps to Opportunity.StageName via the Sales Process, Deal value maps to Amount, expected close date maps to CloseDate, and owner maps to Opportunity.OwnerId via email-matched User lookup. Any PipelineManager custom fields on Deals migrate to custom Opportunity fields pre-created during schema design.

PipelineManager People with no associated Company map to Salesforce Lead. PipelineManager People with an associated Company map to Salesforce Contact attached to the corresponding Account. We apply the split using the Company association in PipelineManager as the routing key. Any PipelineManager custom properties on People migrate to custom fields on Lead or Contact pre-created during schema design. The customer's admin decides whether to use the Salesforce Lead object for all prospects or to use Contacts only with a custom stage field.

PipelineManager Company records map to Salesforce Account. Company name becomes Account.Name, used as the dedupe key during import. Account is created before any Contact import so that AccountId is available at Contact insert time. Billing address, phone, website, and any custom Company properties migrate to the equivalent Account fields.

PipelineManager Activities (calls, emails, meetings, notes) map to Salesforce Task (for calls and tasks) and Event (for meetings). Email content migrates to Salesforce EmailMessage linked to a Task record. Activity type from PipelineManager maps to Task.TaskSubtype (Call, Email, Task). Activity timestamp preserves timeline ordering via ActivityDate on Task and StartDateTime on Event. The parent record reference (Deal or Person) resolves to the migrated Opportunity or Contact ID before insert.

PipelineManager file attachments migrate as Salesforce ContentVersion records with the original filename preserved. Each ContentVersion is linked to the parent record (Opportunity, Contact, Account, or Lead) via a ContentDocumentLink. File size, content type, and upload timestamp are preserved in Salesforce metadata fields. If the source file storage uses a path structure, the destination folder organization is documented separately for the customer's admin to configure in Salesforce Files or Experience Cloud if needed.

PipelineManager custom fields on People are identified during discovery. We pre-create corresponding custom fields on Salesforce Lead and Contact before migration. Field type mapping follows Salesforce's type system: text custom fields become Text(255), date fields become Date, number fields become Number, and checkbox fields become Checkbox. Required-field validation is temporarily relaxed during migration load and re-enabled post-import.

PipelineManager custom fields on Companies migrate to custom Account fields. We pre-create all destination fields during schema design. Picklist values from PipelineManager custom fields map to Salesforce picklist or multi-select picklist values on the equivalent Account field.

PipelineManager custom fields on Deals migrate to custom Opportunity fields. All custom Opportunity fields are created during schema design before any Opportunity data loads. The Salesforce migration user is granted field-level read/write access to these fields during the migration window.

PipelineManager Users referenced as Deal owners map to Salesforce Users by email address lookup. We extract all distinct owner emails from Deals, People, Companies, and Activities and match against the destination Salesforce org's User table. Any PipelineManager User without a matching Salesforce User is placed in a reconciliation queue for the customer's admin to provision before record import begins. Inactive PipelineManager users are flagged with a deactivation date so the admin can decide whether to map them to active or inactive Salesforce Users.

PipelineManager Stage names map to Salesforce StageName values within the appropriate Sales Process. We preserve stage order from PipelineManager in the Sales Process configuration. Stage probability percentages migrate to StageProbability on OpportunityStage. If PipelineManager has closed-lost and closed-won stages, we map them to the corresponding Salesforce standard stages (Closed Lost, Closed Won) rather than creating custom stage values.

PipelineManager notes (activity type NOTE) migrate to Salesforce Note. Rich-text notes migrate to ContentNote using Salesforce's enhanced note format. Notes are linked to the parent record (Opportunity, Contact, Account, or Lead) via ContentDocumentLink. Note body content, creation date, and last-modified date are preserved. If PipelineManager stores notes as plain text only, they migrate as standard Note records.