Migrate from BenchmarkONE to Pipedrive

BenchmarkONE Contact maps to Pipedrive Person. Standard fields (name, email, phone, title, address) map 1:1. Contact Status maps to a custom field or Person Notes since Pipedrive does not have a native contact status concept. Temperature (Hot/Warm/Cold) migrates as a custom field temperature_score__c to preserve lead scoring history. Lead Source maps to a custom field lead_source__c because Pipedrive captures lead source differently (via Label or Activity type). Social profile URLs from BenchmarkONE migrate to the Person's website_links or a custom URL field.

BenchmarkONE Company maps directly to Pipedrive Organization. Company Name maps to Organization name, Website URL maps to Organization website, and the contact-to-company link is preserved as the Person-Organization relationship in Pipedrive. Organizations are created before Person records to satisfy the OrganizationId lookup at Person import time.

BenchmarkONE Deal maps to Pipedrive Deal. The Deal title, amount, expected close date, stage, and associated Contact and Company links migrate directly. Pipedrive Deal stages are configurable and may need remapping if the source BenchmarkONE pipeline uses stage names not present in the destination pipeline configuration.

BenchmarkONE supports a single deal pipeline with configurable stages. If the source account uses multiple named pipelines (via custom configurations), each maps to a separate Pipedrive Pipeline object. Stage order and probability percentages migrate from BenchmarkONE to Pipedrive stage definitions. If the customer has one pipeline in BenchmarkONE, we configure one Pipedrive Pipeline with matching stage names.

BenchmarkONE Tasks linked to Contacts, Companies, or Deals migrate to Pipedrive Activities. Task subject maps to Activity subject, due date maps to Activity due_date, status maps to Activity done (boolean), and assignee maps to Activity user_id. Tasks that overlap semantically with Deals (some reviewers note redundancy) are assessed during scoping to determine whether both migrate or if the customer prefers to consolidate.

BenchmarkONE free-form tags applied to contacts migrate to Pipedrive Labels on the Person record. Tags are comma-separated in the BenchmarkONE export and are split into individual Label values during transformation. Pipedrive Labels support multiple values per Person. If tags are used for complex segmentation, we document the full tag taxonomy during scoping and map each tag group to a corresponding Label structure in Pipedrive.

BenchmarkONE custom fields on Contacts and Companies migrate to Pipedrive custom fields on Person and Organization. We audit the source custom field schema during scoping, validate field types against Pipedrive's supported types (text, number, date, single-select, multi-select, phone, email, URL), and flag any type mismatches for transformation or manual review before import.

BenchmarkONE users assigned as owners to contacts, companies, deals, and tasks map to Pipedrive Users by email match. We resolve every distinct owner reference in the source data against the destination User table before record import. Owners without a matching Pipedrive User go to a reconciliation queue for the customer's admin to provision before migration resumes.

BenchmarkONE email campaign metadata (campaign name, send date, audience size, open rate, click rate, bounce count) migrates to Pipedrive as Activity records with type=campaign and aggregate metrics stored in custom fields on the linked Person. Individual email event logs (which contact opened which email, at what timestamp) may require separate export and are mapped to Activity notes if the volume is manageable; large event logs are flagged for a separate engagement.

BenchmarkONE stores social profile URLs (LinkedIn, Twitter, Facebook) on the contact record. These migrate to Pipedrive as website_links on Person, or to custom fields social_linkedin__c, social_twitter__c if the destination does not have a structured social field. We assess the source social field count during scoping.

BenchmarkONE automations are triggered by form submissions, link clicks, website visits, tag changes, or purchases. These are platform-specific constructs that do not export as data and do not have a direct Pipedrive equivalent. We document each active automation's trigger, conditions, and actions during discovery and deliver a written mapping to equivalent Pipedrive Workflow rules. This is a manual reconstruction step, not a data migration, handled as a separate workstream after cutover.