Migrate from bxp software to monday CRM

BXP Forms are the primary data containers and map to Monday.com CRM boards. Each BXP Form becomes a CRM Board with the Form name as the board name. The Form's custom field configurations map to Monday.com column types: text fields become Text columns, numeric fields become Numbers columns, date fields become Date columns, dropdown fields become Dropdown or Status columns. We enumerate all Forms and their field configurations during scoping before designing the column schema for each destination board.

BXP Contact records map to Monday.com CRM Contacts. Email, phone, name, and any custom fields migrate directly. The Contact's linked Form data (activity history tied to the contact) migrates as Timeline entries or linked Items. We preserve the original bxp contact ID as a custom column for audit trail. Where BXP contacts have no email, we create a placeholder using the format [email protected] to satisfy Monday.com's email requirement.

BXP call logs, agent interactions, and activity records vary by client deployment schema. We map standard activity fields (timestamp, type, duration, disposition) to Monday.com Activity entries or structured Item updates. Non-standard fields from the bespoke BXP deployment are evaluated during scoping and mapped to custom columns on the relevant Contact or Board Item. We flag any activity types that have no Monday.com equivalent as a written recommendation for manual tracking or a custom integration.

BXP's bespoke custom fields per client are enumerated during schema scoping and mapped to typed Monday.com columns. We handle text, number, date, checkbox, dropdown, email, phone, and URL field types. Multi-select fields from BXP become Monday.com Tags or Dropdown columns. We do not assume a standard field set across bxp instances; every mapping is designed against the specific source schema enumerated during discovery.

Contact-centre-specific metrics like call duration, wrap time, QA scores, and agent performance data stored in BXP do not map to standard Monday.com CRM objects. We export these as structured data and create a dedicated Monday.com board (Agent Performance or similar) with columns for each metric type. The board links to the Contact record via a relation column so agents see their CRM profile alongside their performance data.

BXP eLearning module stores training completion records, module scores, and assignment data. We export these as a structured dataset and create a Training Board in Monday.com where each training module is an Item and completion records are sub-items linked to the agent Contact. Scores migrate as Numbers columns, completion status as Status columns.

QA evaluations tied to calls in BXP are typically bespoke to each deployment. We export QA records alongside the associated Contact and Activity, preserving the evaluation context. These load into a dedicated QA Board in Monday.com with Items representing each evaluation, linked to the Contact and the relevant Activity Item. QA score fields become Numbers columns; evaluation notes become Text columns.

BXP exports custom archives in CDA and CCL proprietary formats that require parsing before migration. We convert CDA/CCL exports into standard CSV or JSON using a custom parsing pipeline, then load into Monday.com via the standard import flow or API. The parsing step adds scope during discovery because the format structure is not publicly documented and must be tested against actual archive exports from the specific bxp instance.