Migrate from PipelinePRO to Freshsales

PipelinePRO Contact records export as CSV with name, email, phone, and any custom field columns. We map these directly to Freshsales Contact fields. Email address is used as the dedupe key during import to prevent duplicate Contact creation. Custom fields must be pre-created in Freshsales with identical names and matching field types (text, number, dropdown) before the import CSV is submitted. We flag any PipelinePRO contact records with empty email addresses for manual review because Freshsales requires an email for Contact creation via API.

PipelinePRO Company records map to Freshsales Organization. The mapping quality depends on whether PipelinePRO users consistently populated the company field on their Contact records — many small teams leave the company field blank or use free-text variations that produce duplicate Organizations. We flag duplicate Organization candidates (same domain, different name) for the customer to resolve before bulk import. We use the company domain as the dedupe key where present.

PipelinePRO Deal records include name, value, stage, owner, and expected close date. We map PipelinePRO deal stages to Freshsales Deal stages using a customer-reviewed stage mapping table. Deal owner resolves by matching the PipelinePRO owner email to a Freshsales User. Any PipelinePRO deals without an assigned owner are held in a reconciliation queue. Closed-won and closed-lost stages from PipelinePRO map to Freshsales Deal status values.

PipelinePRO pipelines export as named pipeline boards with their stage lists. Freshsales supports up to 10 pipelines via its import tool. We extract the pipeline name and stage order from PipelinePRO and create matching Pipelines in Freshsales before Deal records are imported. Stages are created in Freshsales before Deals to satisfy the stage dependency. If PipelinePRO has more than 10 pipelines, the customer selects the 10 most active for migration; the remainder are documented with their deal counts for manual rebuild.

Stage names and order are configured per PipelinePRO pipeline. We extract the stage list from each PipelinePRO pipeline and map it to Freshsales Deal stage names. Freshsales uses a default New → Qualification → Discovery → Demo → Negotiation → Won/Lost stage sequence, which we customize to match the PipelinePRO naming convention exactly. Stage probabilities from PipelinePRO migrate as custom fields on the Deal record if they differ from Freshsales defaults.

PipelinePRO custom fields exist per object but have no bulk schema export. We ask the customer to provide a screenshot or list of custom field names, their object assignment, and field types before migration. We create matching custom fields in Freshsales with the same name, object, and field type before any record import begins. Field type mismatches (e.g., exporting a numeric custom field as text in CSV, then importing into a Freshsales numeric field) cause import failures that require re-export and re-import.

Tags on PipelinePRO Contacts and Deals export as comma-separated values within the record CSV. We parse these into individual tag values and apply them as native Freshsales Tags on the corresponding Contact and Deal records during import. Tag preservation is important for teams that used tags for lead source, deal category, or team segmentation in PipelinePRO.

PipelinePRO User accounts export as a simple list of names and email addresses. We map these to Freshsales User records by email match. Owners without a matching Freshsales User are held in a reconciliation queue for the customer to provision before Deal and Contact import resumes. Inactive PipelinePRO users who no longer have accounts are preserved as historical owners on Deals but are not provisioned as active Freshsales Users.