Migrate from PipelinePRO to Microsoft Dynamics 365 Sales

PipelinePRO Contact records export as CSV with name, email, phone, custom field columns, and pipeline status. We assess the contact's pipeline stage at migration time to determine whether it maps to a Dynamics 365 Contact (qualified, attached to an Account) or a Lead (unqualified, awaiting qualification). We preserve the original PipelinePRO pipeline stage as a custom field on the destination record for reconciliation. Any tag data stored as comma-separated values in the CSV parses into a multi-select picklist or custom text field in Dynamics 365.

PipelinePRO Company records map to Dynamics 365 Account. Export quality depends on how consistently users populated the company field on Contact records; we flag sparse or duplicate Account records for customer review before load. Account Name becomes the Account's Name field, domain data maps to Website, and any industry or address fields map to typed Account fields or custom fields created during schema setup.

PipelinePRO Deal records map to Microsoft Dynamics 365 Sales Opportunity. Deal name becomes Opportunity Name, deal value maps to Amount, expected close date maps to CloseDate, and owner email resolves to a Dynamics 365 User. PipelinePRO's pipeline stages map to Opportunity Stage via a customer-reviewed mapping table deployed as a Sales Process in Dynamics 365 before the bulk import runs.

PipelinePRO's customizable pipeline boards with drag-and-drop stages map to Dynamics 365 Opportunity Stage values within a configured Sales Process. We extract the stage names and order from PipelinePRO exports and recreate them in Dynamics 365 as stage entries with matching probability percentages. Stage mapping is reviewed by the customer's sales lead before migration to ensure the new pipeline reflects the actual sales motion.

PipelinePRO Lead records function as early-stage contacts with their own status field. These map directly to Dynamics 365 Lead records with the PipelinePRO lead status preserved in a custom field. We resolve the owner email to a Dynamics 365 User and create a Lead Status picklist mapping that the customer's admin approves before import.

PipelinePRO custom fields exist per object but have no bulk schema export. We ask customers to provide a list of custom field names and their types before migration. We create matching custom fields in Dynamics 365 using the appropriate Dataverse field type (text, number, decimal, picklist, date) and deploy them to the destination org before any data loads. Field-level security is set to read-write for the migration user.

PipelinePRO user accounts with names and email addresses export as a simple list. We map these to Dynamics 365 User records by email match. Any PipelinePRO user who does not yet have a Dynamics 365 User account goes into a reconciliation queue for the customer's admin to provision before record reassignment runs. Deal owners and Contact owners update to point to the correct Dynamics 365 User IDs after provisioning.

Uploaded files attached to PipelinePRO deals or contacts are downloaded where accessible via download links in the account view. We upload these to the associated Dynamics 365 Account or Opportunity record where they attach to SharePoint document libraries managed by Dataverse. Files that cannot be retrieved are flagged for manual handling during the migration scoping call.