Migrate from PipeRun CRM de Vendas to Freshsales

PipeRun Contacts map directly to Freshsales Contacts. We extract name, email, phone, and linked Company reference from the PipeRun export. The Contact-to-Company link is resolved during import by matching the Company name to the Freshsales Account created from the corresponding PipeRun Empresa record.

PipeRun Companies map to Freshsales Accounts. The Company name becomes the Account name and is used as the deduplication key during import. Address, domain, and custom field values transfer to the corresponding Freshsales Account fields. PipeRun's single-empresa-per-contact model maps cleanly to Freshsales's Contact-Account relationship.

PipeRun Deals are the primary revenue object and map to Freshsales Deals. Each Deal carries a value (valor), expected close date, owner, and stage. We resolve the stage value using the Funnel stage-mapping table created during discovery and apply it as the Freshsales Deal Stage. Deal owner maps via email-match to the Freshsales User record.

Each PipeRun Funnel becomes a Freshsales Pipeline. We extract all Funnel definitions and their stage order from PipeRun's admin settings and create a stage-mapping table during discovery. Each Funnel maps to a separate Freshsales Pipeline; stages are created in the same order and named to match the source. Pipeline creation is done before any Deal import to satisfy the pipeline assignment requirement. Note: multiple pipelines are available on Estate and Forest tiers; Starter tier has a single pipeline.

PipeRun Activities (calls, emails, meetings, notes) map to Freshsales Tasks and Events. We preserve the activity type, timestamp, description, and owner. Long free-text note content may need truncation to fit Freshsales field limits. Each Activity record is linked to its parent Contact or Deal via the Freshsales contact_id or deal_id foreign key resolved at migration time.

PipeRun native proposals with line items and ICP-Brasil electronic signature are exported as documents. The proposal content, line items, and signature status are exported from PipeRun and re-attached to the corresponding Freshsales Deal as a Note with an attachment link. Customers should confirm whether Freshsales's higher-tier Quote functionality (available from Blossom) is needed to replace the proposal workflow; we document this as a post-migration configuration decision.

PipeRun custom fields on Contacts, Accounts, Deals, and Activities are exported with their values. Field types (text, date, dropdown, currency) are mapped to the closest Freshsales custom field type during schema design. We pre-create the destination custom field definitions in Freshsales before importing data so that values are written to the correct fields on first insert.

PipeRun Users are extracted by email address and matched to Freshsales User accounts. The customer provides the destination Freshsales User list during scoping. Any PipeRun Owner without a matching Freshsales User is held in a reconciliation queue for the admin to provision before Deal and Activity import resumes.

PipeRun tags applied to Deals and Contacts are exported as tag values. Freshsales supports native tagging on Contacts and Deals. We import tags as Freshsales Tags, preserving the original tag names. If a customer uses tags for segmentation rather than labeling, we recommend a multi-select custom field as an alternative during scoping.

Files linked to PipeRun Deals or Proposals are batch-downloaded from the web interface and re-associated to the corresponding Freshsales Deal record as attachments. File naming preserves the original PipeRun record identifier for traceability. Very large attachment sets (over 500 files) may require a multi-session batch approach.