Migrate from bxp software to Pipedrive

BXP Forms are the primary data container for contact records. Each Form can hold arbitrary field configurations built for the specific client deployment. We export contacts via the bxp API using the Form endpoint, selecting specific fields per form and generating structured output. During scoping we enumerate all Form field names and types for the specific BXP instance so we can build a field-level map to Pipedrive's Person object, preserving email, phone, and any matched custom fields. Email address serves as the dedupe key during Pipedrive import.

BXP's value proposition is custom fields built per client. Every custom field in the source instance is a mapping candidate. We enumerate all custom field names and types during scoping, then pre-create equivalent custom fields in Pipedrive before any record import. Field type translation follows: BXP free-text maps to Pipedrive text, BXP dropdown maps to Pipedrive picklist, BXP multi-select maps to Pipedrive multi-select, BXP date maps to Pipedrive date. Fields with no Pipedrive equivalent are held for admin review.

BXP can export custom archives in CDA and CCL formats, which are proprietary archive formats that require parsing before migration. We convert CDA/CCL exports into standard CSV or JSON before any mapping. Within these archives, contact records, company records, and deal records may be interleaved; we split by record type at transform time and route to the appropriate Pipedrive object. Archive data older than five years with no activity history is flagged for the customer to decide whether migration adds value.

BXP logs call activities and agent interactions in its Activities module. The schema varies by client deployment. We map standard activity fields (call date, duration, disposition, notes) to Pipedrive Activity records, preserving the activity timestamp for timeline ordering. Non-standard fields unique to the BXP deployment are held in a custom JSON field or structured attachment for admin review.

Contact-centre-specific metrics — call duration, wrap time, QA scores, average handling time — stored in BXP do not map directly to Pipedrive's standard objects because Pipedrive is a sales CRM, not a contact-centre WFM platform. We export agent metrics as structured CSV attached to the associated Person record, or as custom fields on a separate Activity record if the customer has purchased Pipedrive's Advanced Reports and Custom Objects add-on. The customer decides which approach based on reporting needs.

QA evaluations tied to calls are stored in BXP and are typically bespoke to each deployment. We export QA records alongside the associated contact and activity to preserve evaluation context. Pipedrive has no native QA evaluation object; we map QA score, evaluator name, and evaluation date to a structured Activity note or to a Pipedrive Custom Object if the customer licenses that feature. The customer chooses the target during scoping.

BXP's eLearning module stores training completion records, scores, and module assignments. These do not have a direct Pipedrive equivalent. We export eLearning records as structured CSV attached to the associated Person record, with module name, completion date, and score mapped to columns. Tags on the Person record identify training categories for segmentation. If the customer needs a native training tracker, we recommend a dedicated LMS integration post-migration.

Some BXP Form deployments include company-level fields (company name, address, industry) alongside contact fields. Where the source instance stores both contact and company data in a single Form, we split the company fields into a Pipedrive Organization record and link it to the Person record via the Person's org_id field. The dedupe key for Organization is company name, with domain-based secondary matching if available.

BXP stores owner and agent information tied to records. We extract distinct owner references from the export and match by email or display name against Pipedrive Users. Owners without a matching Pipedrive User go to a reconciliation queue for the customer's admin to provision before record import resumes. Pipedrive's per-user licensing model means the customer needs to confirm active user count against their chosen Pipedrive plan before migration.

We preserve original BXP create and update timestamps as custom fields on migrated records (bxpc_created_at__c, bxpc_updated_at__c) rather than overwriting them with the import date. This maintains historical data integrity for audit purposes and allows the customer to sort by original creation date in Pipedrive reports after migration.