Migrate from bxp software to Freshsales

bxp Forms are the primary data containers in a bxp deployment and carry arbitrary field configurations unique to each instance. We enumerate every Form definition during scoping, identify standard fields (name, email, phone) and custom fields per Form, then map each Form to either a Freshsales Contact record (for standard CRM fields) or a Freshsales Custom Object (for industry-specific or contact-centre-specific fields). The Form-to-Object mapping is one of the primary deliverables from the discovery phase.

bxp Contact records map directly to Freshsales Contact. Standard fields including email address, phone number, name, and address data use Freshsales native Contact fields. All bespoke custom fields enumerated during schema discovery map to Freshsales custom fields on the Contact object, preserving field types and picklist values. Freshsales custom fields support text, number, date, picklist, multi-select picklist, and currency types.

bxp activity logs (call interactions, agent notes, interaction records) are extracted via the bxp API or from Form exports. We map call duration and disposition to Freshsales Call records, general interaction notes to Task records, and scheduled activities to Event records. The bxp activity schema varies by deployment, so every field is reviewed during scoping and mapped individually to the closest Freshsales equivalent.

bxp's core value proposition is custom fields built per client. We treat every custom field discovered during schema enumeration as a mapping candidate. Text fields map to Freshsales text custom fields, numeric fields to number or currency custom fields, and date fields to Freshsales date custom fields. Multi-select or tag-style fields map to Freshsales multi-select picklist fields with values preserved from the source. Any field that does not fit a standard Freshsales type is documented for the customer's admin to review.

bxp custom archives in CDA and CCL formats are proprietary binary exports that require parsing before migration. We convert CDA/CCL exports into structured CSV or JSON using a custom parsing routine, then load the converted data as standard records into Freshsales. The conversion step adds time to the discovery and extraction phases and is scoped as a separate workstream during planning.

bxp agent metrics including call duration, wrap time, and QA scores are contact-centre-specific and have no direct Freshsales standard object equivalent. We export these as structured records in a Freshsales Custom Object (agent_metrics) linked to the Contact record via a lookup relationship, or as structured attachments if the destination Freshsales plan does not include Custom Objects. The customer selects the preferred storage strategy during scoping.

bxp eLearning module records (training completion, module scores, assignments) are exported as structured data. They map to a Freshsales Custom Object (training_record) linked to the associated Contact or a dedicated User object. If the destination Freshsales plan does not support Custom Objects, we export these as structured JSON attachments and deliver them alongside the migration for manual import or future Custom Object adoption.

bxp QA evaluations tied to specific calls or interactions are exported alongside the associated Contact and activity record to preserve evaluation context. They map to a Freshsales Custom Object (qa_evaluation) with fields for score, evaluator, evaluation date, and linked call reference. We flag any bxp QA field that has no Freshsales equivalent and document it for admin review.