Migrate from bxp software to HubSpot

bxp contact records map directly to HubSpot Contacts. Every standard bxp contact property (name, email, phone, job title, address) maps to the equivalent HubSpot contact property using the HubSpot Contacts API. Custom bxp contact fields that have no standard HubSpot equivalent are created as HubSpot custom properties before migration begins. The HubSpot contact record inherits the primary company association from bxp's company link, establishing the Contact-to-Company relationship in HubSpot automatically upon import.

bxp company records map 1:1 to HubSpot Companies using direct field mapping for company name, domain, industry, employee count, and address fields. Any custom company properties in bxp that lack a HubSpot standard equivalent are migrated as HubSpot custom properties with matching data types. Parent-company hierarchies in bxp map to the HubSpot Parent Company association, preserving organizational structures. Industry classifications use a value-mapping table to align bxp taxonomy with HubSpot's allowed industry values during import.

bxp deal records map to HubSpot Deals. Each deal carries its pipeline and stage assignment from bxp, which maps to a corresponding HubSpot Deal Pipeline and stage within that pipeline. Deal amount, close date, owner, and custom deal fields migrate as HubSpot Deal properties. Stage values are translated using a pre-configured value-mapping table that your team approves before the migration run executes.

bxp's custom form fields — user-defined properties on contacts, companies, or deals — do not have a direct HubSpot equivalent. We create a HubSpot custom property per bxp field, preserving the original field label, data type, and pick-list values where applicable. The bxp form name is stored as the property description for reference. Picklist values are migrated as HubSpot option labels within the custom property definition.

bxp call logs migrate as HubSpot engagement records of type 'Call' on the associated contact, preserving call duration, disposition, agent ID, and timestamp using the HubSpot Engagements API. Each call log's disposition code is stored as a custom engagement property for downstream reporting. Call recordings referenced in bxp are downloaded, converted if necessary, and re-uploaded as HubSpot file attachments linked to the engagement record. The original recording filename and duration are preserved in HubSpot's file metadata for audit continuity.

bxp email activity records map to HubSpot engagement records of type 'Email', capturing timestamp, subject, and direction (sent or received) for each message via the HubSpot Engagements API. The associated contact is linked via HubSpot's standard engagement association mechanism. The original bxp email body and any HTML formatting are preserved by storing the full email content as an attachment on the engagement record, or as a formatted note if the email is plain text. Email thread identifiers are retained for conversation tracking where available in bxp.

bxp meeting and appointment records migrate as HubSpot engagement records of type 'Meeting', preserving start time, end time, location, associated contact, and meeting title with direct field mapping via the HubSpot Engagements API. Meeting attendees beyond the primary contact are captured as additional engagement associations where supported. Owner assignment is resolved by matching the bxp user email to an existing HubSpot user account, with unmatched owners flagged for manual assignment before migration completes. Any meeting notes or agendas attached to the bxp record are stored as file attachments on the HubSpot engagement.

bxp notes attached to contacts, companies, or deals migrate as HubSpot Notes linked to the equivalent record using HubSpot's native Notes API. The note body text, including any formatting or embedded images, transfers directly to HubSpot's note content field. Note creation timestamp and author information are preserved as HubSpot note metadata, maintaining the original audit trail. If a bxp note references other bxp records (such as linking one contact note to a related deal), those cross-references are flagged for manual re-establishment in HubSpot since native cross-record note linking is not a standard feature.

bxp agent records map to HubSpot users by email address match. Agent performance metrics (average call handle time, QA score, etc.) from bxp's QA module store as custom properties on the corresponding HubSpot contact record since HubSpot has no native agent performance object. Unmatched agent emails are flagged for admin review before the migration run completes.

bxp custom entities created via its form builder map to HubSpot Custom Objects on Enterprise plans. N:N relationships between custom entities and contacts or companies require a HubSpot junction object (a custom object with two association properties pointing to each related entity). We generate the custom object schema in HubSpot before migration begins and map all related records accordingly using the Custom Objects API.

bxp's quality-assurance evaluation records and agent scoring data have no native HubSpot equivalent. We preserve evaluation scores, criteria names, and evaluation dates as a HubSpot custom object with custom properties. Coaching notes and improvement flags store as text properties for reference by managers post-migration. The evaluation template structure is exported as a reference document for manual rebuild in HubSpot's workflow engine.

bxp file attachments linked to contacts, companies, or deals are downloaded from bxp's storage, processed for compatibility with HubSpot's file requirements, and re-uploaded to HubSpot Files using the Files API. Each file is then associated to the equivalent HubSpot record using the engagements or associations endpoint. File metadata including original filename, upload date, file size, and content type are preserved in HubSpot's file properties. Large files over HubSpot's default size limit are handled according to HubSpot's file upload specifications. If duplicate files exist across multiple bxp records, FlitStack AI creates a single HubSpot file and associates it to all relevant records to avoid duplication.