Migrate from bxp software to Nutshell

bxp API documentation is an internal PDF with no public access

bxp software's API documentation (v6.0-5) is distributed as an internal PDF not publicly indexed online. There is no developer portal, no Swagger spec, and no public rate-limit documentation. We request the PDF directly from bxp during scoping and test API connectivity in a sandbox environment before committing to an API-based migration path. Where the API is restricted or unavailable, we fall back to Form exports and custom archive exports (CDA/CCL formats). Customers should confirm bxp's willingness to share API documentation early in the scoping process because it directly affects the migration path and timeline.

Every bxp instance has a unique data schema requiring full enumeration

bxp's core differentiator is that each client deployment is custom-built around their specific workflows and metrics. There is no standard object set we can assume across instances. Forms, fields, and relationships vary per client. We cannot pre-build a migration template. Every engagement requires a full schema enumeration of the source bxp instance before we can design the export and load strategy. This enumeration step adds one to two weeks to the scoping phase and must complete before we can finalise the migration quote.

CDA and CCL archive formats require custom parsing before import

bxp's custom archive formats (CDA and CCL) are proprietary file formats that cannot be loaded directly into Nutshell. We convert CDA/CCL exports into standard CSV or JSON before loading. The conversion process is dependent on the specific archive structure of the source bxp instance, which varies by deployment. We test the conversion against a sample archive before running the full export. Any records that fail conversion are logged separately for manual reconciliation.

Telephony and QA records have no native Nutshell equivalent

bxp's native telephony module (IVR, call recording, click-to-dial, outbound dialer) and its integrated QA evaluation module have no equivalent objects in Nutshell's standard data model. Call records, QA scores, and eLearning completion data migrate as structured JSON attachments to Person or Activity records rather than as native objects. This preserves the data for audit purposes but does not surface it natively in Nutshell's UI. Customers requiring native call logging or QA tracking in Nutshell should plan to integrate a third-party telephony app (such as a compatible VoIP or call tracking solution) post-migration.

bxp implementation costs add significant switching overhead

bxp implementation costs of $5,000-$50,000 on top of per-user subscription create a financial lock-in that makes switching feel expensive relative to the ongoing Nutshell subscription cost. We include the bxp contract wind-down timeline in our scoping checklist. Customers should confirm any minimum contract term commitments with bxp before beginning migration planning to avoid paying for two platforms simultaneously during the transition window.