Migrate from bxp software to Twenty CRM

BXP Forms are the primary data containers and hold arbitrary field configurations per client instance. We enumerate every Form in the BXP instance during scoping, then map each Form to the nearest Twenty standard object (People for contact-facing forms, Company for account-facing forms, or a Custom Object for industry-specific record types). Custom fields from each Form are pre-created in Twenty's Data Model before any import begins. Forms that serve as standalone records without clear CRM equivalents migrate as Custom Objects with the Form name preserved as the object label.

BXP Contact records map directly to Twenty People. Email, phone, and standard contact fields transfer directly. Any custom fields on the BXP Contact record are created as custom fields on the Twenty People object before import. We use the BXP Contact email address as the dedupe key during Twenty import to prevent duplicate records.

BXP logs call activities and agent interactions with schema varying by client deployment. Standard call fields (duration, disposition, timestamp) map to Twenty Task records with TaskSubtype set to Call. Interaction notes and free-text activity records map to Twenty Note records linked via ContentDocumentLink to the parent People or Company record. Non-standard BXP activity fields are exported as custom task fields or Note body text depending on content type.

BXP's value proposition is custom fields built per client. Every custom field in the BXP instance is enumerated during scoping and created as a typed custom field in Twenty's Data Model before import. Field types are mapped: BXP text to Twenty TEXT, BXP date to Twenty DATE, BXP dropdown to Twenty SELECT, BXP number to Twenty NUMBER. Fields must exist in Twenty before the CSV import; we create them first so that the import references valid column headers.

BXP can export custom archives in proprietary CDA and CCL formats. These are parsed into standard CSV or JSON before loading into Twenty. The parsing logic is developed during scoping using a test archive sample. Parsed records are then mapped to the appropriate Twenty object (People, Company, Task) based on the archive content type. CDA and CCL parsing adds one to two weeks to the project timeline.

Contact-centre metrics like call duration, wrap time, and QA scores stored in BXP do not map directly to Twenty's standard objects. We export them as structured records in a Twenty Custom Object (AgentMetrics) with custom fields for each metric, linked via lookup to the associated People record for agent attribution. QA scores are exported as Note records linked to the associated Task (the evaluated call).

BXP's eLearning module stores training completion records, scores, and module assignments. These have no direct Twenty CRM equivalent. We export eLearning records as a Custom Object (TrainingRecord) in Twenty with fields for module name, completion date, score, and status, linked to the People record representing the trained agent. If the customer does not require eLearning tracking in Twenty, records are exported as a structured CSV audit file rather than live CRM records.

QA evaluations tied to agent calls are stored in BXP with bespoke schema per deployment. We export QA records alongside the associated Contact and Activity to preserve evaluation context. In Twenty, QA records are stored in a Custom Object (QAEvaluation) with fields for evaluator, score, evaluation date, and evaluation criteria, linked to the associated Task (the evaluated call). The customer defines the criteria fields during scoping based on their BXP QA template.

BXP includes an Accounts module for managing company records alongside Contacts. Where present, BXP Accounts map directly to Twenty Companies. The BXP account name becomes the Company name in Twenty, and the account address maps to the Company address fields. BXP account contacts are linked via the People-to-Company relationship in Twenty.

BXP includes a Leads module for tracking unqualified prospects. BXP Leads map to Twenty People records with a custom field bxp_lead_source__c capturing the original lead source. If the BXP Lead has an associated deal value, it maps to a Twenty Opportunity record linked to the People record.

BXP Opportunities map to Twenty Opportunities with deal name, amount, stage, and close date preserved. BXP pipeline stages are mapped to Twenty Opportunity stage values during the pre-build phase. Opportunity amount maps to the Twenty amount field; any custom deal fields from BXP are created as custom fields on the Twenty Opportunity object before import.

BXP agents and users referenced on Contact, Activity, and QA records are resolved by email against Twenty workspace Members. We extract every distinct owner email from the BXP export and match against the Twenty Members list. Members must be invited to the Twenty workspace and accept their invitation before the import phase because Owner references on People, Company, and Opportunity records require a valid workspace Member to link against.