Migrate from bxp software to Zoho CRM

BXP Contact records map directly to Zoho CRM Contacts. Standard fields (email, phone, name, address) migrate with direct field mapping. Any BXP custom fields on Contact records are enumerated during scoping and mapped to Zoho custom fields, which we pre-create as text, picklist, numeric, or date fields based on the source data type. Duplicate resolution uses email as the primary key.

BXP Forms are the primary data containers and hold arbitrary field configurations per client deployment. Where a Form maps directly to a Zoho standard module (Leads, Contacts, Accounts), we map it 1:1. Where a Form represents a bespoke record type unique to the client, we create a Zoho Custom Module and map the Form fields as custom fields on that module. The decision between standard module and custom module is made during schema enumeration.

BXP organisation records map to Zoho Accounts. The organisation name maps to Account Name, and any industry or sector custom fields map to Zoho custom fields on the Account. If BXP stores multiple contact relationships per organisation, we preserve the 1:N Contact-to-Organisation relationship by resolving AccountId during Contact import.

BXP activity logs are stored with variable schemas per client deployment. Call activities map to Zoho Task with TaskSubtype=Call and Call Duration preserved in a custom field. Email and meeting activities map to Zoho Event records. We enumerate the full activity schema during scoping and map each activity type to the closest Zoho equivalent, flagging any activity types that have no Zoho equivalent as candidates for custom field attachment to the parent Contact or Account record.

Contact-centre-specific metrics (call duration, wrap time, QA scores) are stored in BXP but have no direct Zoho CRM equivalent. We create a Zoho Custom Module called Agent Metrics or Contact Centre Performance with fields for each metric enumerated during scoping. The module links to the relevant Contact or User record via lookup relationship. Historical agent metric records are loaded as structured data against this module after the parent Contact import is complete.

QA evaluations tied to calls are stored in BXP with bespoke field structures per deployment. We create a Zoho Custom Module (e.g. QA Evaluations) with fields matching the enumerated QA schema. Each QA record links to the associated Contact and the related Activity (call or meeting) via Zoho lookup fields. This preserves the evaluation context in the destination system.

BXP eLearning module stores training completion records, scores, and module assignments. Zoho Learn is a separate product and not part of Zoho CRM. We create a Custom Module (Training Records) in Zoho CRM with fields for course name, completion date, score, and assignment status. Training documents are attached as Zoho Attachments linked to the relevant Contact or User record.

BXP custom archives in CDA and CCL formats require parsing before migration. We convert CDA/CCL exports into standard CSV or JSON using custom parsers built during scoping. The converted data is then mapped using the same field enumeration process as the API export path. CDA/CCL parsing is a discovery-phase task; we cannot estimate migration volume until the archive format is reviewed.

Every BXP custom field is treated as a mapping candidate. During schema enumeration we document all custom field names, data types, and picklist values. We pre-create Zoho custom fields with the equivalent data type before any data import. Multi-select picklists from BXP map to Zoho multi-select picklists. Date fields are normalised to YYYY-MM-DD format before import to satisfy Zoho's date format requirements.

BXP user records map to Zoho CRM Users. We resolve by email match where possible. Any BXP owner without a matching Zoho User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Zoho's role and profile system is documented and auditable during scoping.