Migrate from PipeRun CRM de Vendas to Pipedrive

PipeRun Contacts map directly to Pipedrive Person records. Name, email, phone, and custom field values migrate 1:1. The PipeRun Contact-to-Company link migrates as a Person-to-Organization relationship in Pipedrive. Email address is used as the primary dedupe key during import. Any PipeRun Contact without an email address is held in a reconciliation queue for manual email verification before insert.

PipeRun Companies map to Pipedrive Organizations. Company name becomes the Organization name, domain extracts to the Website field, and address fields map to Pipedrive's address composite. If the destination Pipedrive account does not use Organizations (configured via Settings > Data > People > Organizations), Contacts are created without an Organization link and tags carry the original company name as a fallback segmentation marker.

PipeRun Deals migrate to Pipedrive Deals. The Deal title, value (Valor), expected close date, owner, and linked Contact and Company references migrate directly. Stage mapping is handled by the Funnel-to-Pipeline configuration. Closed-Won and Closed-Lost status from PipeRun map to Pipedrive Deal status with the original stage name preserved in a custom field pr_original_stage__c.

PipeRun supports multiple simultaneous Funnels; Pipedrive supports multiple Pipelines via Business Intelligence settings (available from the Advanced plan and above). Each PipeRun Funil becomes a separate Pipedrive Pipeline with stages created in the same order and named to match the source. If the destination Pipedrive account is on a lower tier that limits pipeline count, we consolidate secondary Funils into stages within a single pipeline and document the original Funil names in custom fields for reference.

PipeRun Activities (calls, emails, meetings, notes) migrate to Pipedrive Activities. Activity type, timestamp, owner, and free-text content transfer directly. Long notes may be truncated to Pipedrive's 100,000-character Activity body limit — this is verified during staging. The Contact and Deal linkage is resolved via the owner email lookup completed in the scoping phase before Activity import begins.

PipeRun Proposals (CPQ module with ICP-Brasil electronic signature) do not have a direct equivalent in Pipedrive. We export proposal content, line items, and signature status as a Pipedrive Deal note and attach the proposal PDF as a Deal file. Signature status (signed, pending, expired) is stored in a custom field pr_signature_status__c. If the customer requires ongoing proposal management post-migration, we document a Productivo or PandaDoc integration as the replacement CPQ layer.

PipeRun Users assigned as Deal Owners, Activity owners, and stage assignees map to Pipedrive Users resolved by email address. We extract every distinct owner email from the source export and match against Pipedrive User emails before any record with an OwnerId is imported. Any PipeRun owner without a matching Pipedrive User goes to a reconciliation queue for the customer's admin to provision before the migration phase that requires owner assignment resumes.

PipeRun custom fields on Contacts, Companies, Deals, and Activities are exported with their field types (text, date, dropdown, currency). We pre-create matching custom fields in Pipedrive during the schema phase, applying the closest Pipedrive field type for each source type. Note: formula fields, user specification fields, and pipeline-specific custom fields require Pipedrive Premium ($58/user/month) and are documented with a plan-upgrade recommendation if any PipeRun source fields are of these restricted types.

Files and attachments linked to PipeRun Deals or Proposals are batch-downloaded from the web interface and re-associated as Deal files in Pipedrive. We preserve the original filename and, where available, the upload date. Attachments that exceed 100 MB are excluded and listed separately for manual upload post-migration.

PipeRun tags applied to Deals and Contacts migrate to Pipedrive native Tags. Multi-select tags from PipeRun custom fields map to Pipedrive Tags with one tag per PipeRun tag value. If Pipedrive's tag limit is reached (typically 1,000 unique tags per account), overflow tags are migrated as a comma-separated custom field value on the record.