Migrate from bxp software to Salesforce Sales Cloud

Forms are bxp's primary data containers, holding arbitrary field configurations per client instance. We enumerate every Form during scoping, identify the contact-linked fields, and map them to Salesforce Contact fields. Non-contact fields (agent metrics, custom attributes) become Salesforce custom fields or a custom object named after the source Form. The Form's own record IDs are preserved as an external ID for relationship resolution.

BXP Contacts map directly to Salesforce Contact. Email, phone, and standard identity fields migrate 1:1. Custom fields from the associated Form schema map to Salesforce custom fields on Contact, with type mapping confirmed during enumeration (date fields to Date, numeric fields to Number, dropdowns to Picklist). OwnerId is resolved by email against the Salesforce User table.

BXP call activity logs migrate to Salesforce Task with TaskSubtype set to Call. Call duration, disposition, and agent ID migrate to custom Task fields. ActivityDate is set to the original BXP timestamp. Parent Contact or Form record is resolved via the BXP record identifier preserved as an external ID.

Contact-centre metrics such as average handle time, wrap time, call count, and QA scores stored in BXP do not map to any standard Salesforce object. We create a custom object Agent_Metrics__c with a Lookup to Contact, pre-create all custom fields during Salesforce schema design, and import the metrics as structured records. The customer decides whether to display this in a custom Lightning component or report type.

BXP Quality Assurance evaluations tied to specific calls are bespoke per deployment. We export them alongside the associated Contact and Activity, then create a custom object QA_Evaluation__c with a Lookup to the Contact record and custom fields for each evaluation criterion. Evaluation date and score migrate as Salesforce-native Date and Number fields.

BXP's eLearning module stores training completion records, scores, and module assignments. These have no Salesforce standard equivalent. We create a Training_Record__c custom object with Lookups to the Contact (as trainee) and a module custom object, preserving completion dates, scores, and status. The customer configures a related list on the Contact page layout.

BXP custom archives in CDA and CCL formats are proprietary and require parsing before loading into Salesforce. We convert CDA/CCL exports into structured CSV or JSON, then load through the Salesforce Bulk API. Any records that cannot be parsed cleanly are held in a reconciliation queue with a sample of 20 records flagged for customer review before we commit to the load.

Every custom field in the BXP instance is a mapping candidate. During scoping we enumerate all field names, data types, and associated Forms. We pre-create every Salesforce custom field (with __c suffix, matching API name, and correct field type) in a Sandbox org before any data moves. Required fields, validation rules, and picklist values are configured during this phase.

BXP agent and user records map to Salesforce User by email match. We extract every distinct owner reference from Contacts, Activities, and Form records and match against the destination org's User table. Missing Users go to a reconciliation queue for the customer's admin to provision before record import proceeds.

Form submission records that contain bespoke data not attributable to a Contact become Salesforce Note records or a custom object named after the source Form. We flag these during scoping and confirm with the customer's admin which pattern applies to each Form before migration begins.

BXP Workflows and QA evaluation templates do not migrate as code. We document every active automation and QA rule encountered during schema enumeration, describing its trigger, conditions, and actions, and recommend a Salesforce Flow equivalent or Service Cloud QA app from the AppExchange. The customer's admin or a Salesforce partner rebuilds these post-migration.

Where BXP stores created_date and last_modified_date on Form records and Activities, we preserve these as custom fields (bxp_created_date__c, bxp_modified_date__c) on the corresponding Salesforce objects. This maintains audit trail continuity and allows the customer to query historical data in Salesforce using the original timestamps.