Migrate your PipeRun CRM de Vendas data

Contacts (Contatos) are the primary person records in PipeRun. They carry name, email, phone, and a link to a Company. We export them 1:1 as Contacts in the destination CRM and preserve the Contact-to-Company association via a foreign-key mapping pass.

Companies (Empresas/Organizações) are separate objects in PipeRun, distinct from Contacts. We export them as Accounts or Companies in the destination. Where the destination does not support a separate Company object, we merge them into Contacts and keep the organization name as a property.

Deals (Negócios) are the central revenue object in PipeRun. Each Deal is assigned to a Funnel (Funil) and a Pipeline Stage (Etapa). We export all deal fields including value, expected close date, owner, custom properties, and stage history. We rebuild the pipeline stages and funnel structure at the destination using a stage-mapping table.

PipeRun supports multiple simultaneous Funnels, each with its own set of stages. This is a platform-specific concept that most destination CRMs do not replicate natively. We map each Funnel to a separate Pipeline in the destination, and note the stage correspondence in the mapping manifest.

Activities include calls, emails, meetings, and notes logged against Contacts or Deals. We export them as Activities or Engagements in the destination. Long free-text notes may need to be truncated or stored as Activity descriptions depending on destination field limits.

PipeRun has a native CPQ and proposal management module with electronic signature (ICP-Brasil compliant). We export proposal content, line items, and signature status as a Proposal or Quote object. Signature records are stored as metadata notes attached to the proposal.

PipeRun's workflow automation rules (ações automáticas) are platform-internal triggers and cannot be exported in a portable format. We do not migrate them. We document the active automation rules so the customer can rebuild them in the destination system.

Users in PipeRun are assigned as Deal Owners, Activity owners, and stage assignees. We map PipeRun user IDs to destination user IDs via an explicit owner-mapping table provided by the customer during scoping.

PipeRun supports custom fields on Contacts, Companies, Deals, and Activities. We export the custom field definitions and their values. Field types (text, date, dropdown, currency) are mapped to the closest equivalent in the destination CRM.

Files and attachments linked to Deals or Proposals can be exported from PipeRun's web interface individually. We batch-download them and re-associate them to the corresponding records at the destination. Multiple files per record are supported but require individual download passes.

WhatsApp conversations conducted through PipeRun MAX (the Chrome extension) are stored in PipeRun's messaging layer and are not accessible via export. Conversation metadata (timestamps, participants) may be recoverable; message content is not. We flag this clearly in the pre-migration scope document.

PipeRun allows tags to be applied to Deals and Contacts. We export tags as Tags in the destination, or as a multi-select custom field if the destination does not have a native tagging model.