Migrate from Bluetrait to HubSpot

Bluetrait contact records migrate as HubSpot Contacts. The key translation is resolving Bluetrait's flat company-name text field into a HubSpot primary-company lookup. We create the Account record first, then attach each Contact to the resolved AccountId. Unmatched company names get a default 'Unassigned Account' record, flagged for manual review post-migration.

Bluetrait company records map 1:1 to HubSpot Company records. Company name, domain/website, address fields, industry, employee count, and annual revenue transfer directly. HubSpot's N:1 association model (many Contacts → one primary Company) handles what Bluetrait stores as separate contact records — we collapse multi-contact companies to one HubSpot Company with all contacts linked.

Bluetrait deal records — name, amount, stage, close date, owner — map to HubSpot Deals. The owner resolves by email match to HubSpot users. HubSpot's deal stage becomes a pick-list value within your configured Sales Pipeline. If Bluetrait stores deal probability or priority as custom fields, those require HubSpot custom properties created before migration.

Bluetrait does not expose multi-pipeline configuration in the base CRM — deals use a single stage pick-list. If your Bluetrait setup has multiple pipeline configurations (e.g., via custom fields), each pipeline name becomes a separate HubSpot Sales Pipeline. Stage names map to HubSpot stage values within each pipeline, and stage order and probabilities are preserved. We deliver a pipeline-configuration plan before data lands in HubSpot.

Bluetrait ticket records map to HubSpot Tickets, a first-class object in HubSpot Service Hub. Ticket subject, description, status, priority, and due date transfer directly. The original Bluetrait ticket ID is preserved as a custom property (bluetrait_ticket_id__c) on the HubSpot Ticket for traceability. Ticket owner resolves by email match to HubSpot users. Ticket contacts associate through HubSpot's ticket contact property.

Bluetrait product records (name, SKU, description, price, cost, quantity on hand) map to HubSpot Products. HubSpot Products are used in conjunction with Line Items on Deals to model complex quoting. We map Bluetrait product cost as HubSpot's custom property (product_cost__c) since HubSpot Products carry price but not separate cost by default. Quantity on hand transfers as a custom property (quantity_on_hand__c).

All Bluetrait custom fields map to HubSpot custom properties. We create HubSpot custom properties with the same label and data type before migration runs. Field-level validation (required, regex, pick-list) translates to HubSpot property settings. Properties referencing SAP Business One data (Enterprise tier) that have no HubSpot equivalent are created as read-only custom text fields and flagged for manual remediation during the post-migration review.

Bluetrait user records map to HubSpot Users by email address. Owner resolution matches Bluetrait user email to a HubSpot user email — if no match exists, we flag the unresolved owner before migration and your team either invites the user to HubSpot or reassigns their records to a fallback owner. No record lands without a valid HubSpot owner.

Bluetrait timesheet records do not have a native HubSpot equivalent — timesheet data (date, hours, user, task/project association) migrates as a custom HubSpot object named 'Timesheet Entry' with custom properties for each field. Alternatively, timesheet summaries can attach to the relevant Contact or Company record as a custom property or note. We recommend the custom object approach for timesheet-heavy Bluetrait customers so your HubSpot admin can build reports on logged hours post-migration.

Bluetrait file attachments on tickets, contacts, or companies re-upload to HubSpot Files and attach to the corresponding HubSpot record. File size limits apply — HubSpot's default upload limit is 20MB per file. Inline images in Bluetrait notes are downloaded, re-hosted in HubSpot's file manager, and re-embedded in the relevant note body.

Bluetrait workflows, automation rules, and plugin-based automations do not migrate to HubSpot. They are structurally incompatible — Bluetrait's automation engine uses a plugin-and-trigger model that does not translate to HubSpot's workflow builder logic. We export your Bluetrait workflow definitions as a reference document and recommend your HubSpot admin rebuilds the core automation logic in HubSpot Workflows or Operations Hub.