Migrate your bxp software data

Forms are BXP's primary data containers and can hold arbitrary field configurations. We export via the bxp API using the Form endpoint, selecting specific fields per form and generating a structured file. Every client's Forms schema must be enumerated during scoping.

The core CRM object. Contacts are linked to Forms and can carry custom fields. We map Contact records to the destination CRM's contact or person object, preserving email, phone, and any custom fields discovered in the instance.

BXP logs call activities and agent interactions. The schema varies by client deployment. We map standard activity fields to the destination CRM's activity or engagement object, flagging any non-standard fields for manual review.

BXP's value proposition is custom fields built per client. We treat every custom field as a mapping candidate. During scoping we enumerate all custom field names and types so we can build a field-level mapping table before export.

Contact-centre-specific metrics like call duration, wrap time, and QA scores are stored in BXP. These do not map directly to standard CRM objects. We export them as structured attachments or custom objects depending on the destination platform.

BXP includes an eLearning module. Training completion records, scores, and module assignments are stored in BXP but may not have a direct equivalent in the destination CRM. We export these as structured data for re-import as custom objects.

QA evaluations tied to calls are stored in BXP. These are typically bespoke to each deployment. We export QA records alongside the associated contact and activity to preserve the evaluation context.

BXP can export custom archives in CDA and CCL formats. These are proprietary archive formats that require parsing before migration. We convert CDA/CCL exports into standard CSV or JSON before loading into the destination system.