Migrate from Bolten CRM to HubSpot

Bolten contacts map directly to HubSpot contacts. The flat properties bag on a Bolten contact (name, email, phone, job title, address fields) lands in HubSpot's corresponding standard properties. Custom properties on the Bolten contact get created as HubSpot custom properties before the import sequence runs. Original create timestamps are preserved in a custom field since HubSpot's CreatedDate reflects the migration import date, not the original record creation date.

Bolten company records map 1:1 to HubSpot company records. Company name, domain, industry, employee count, and annual revenue move to their HubSpot equivalents. If Bolten has a parent-company relationship, the primary company becomes the HubSpot company's Parent Company link. Multi-company contacts in Bolten (if supported) associate to the primary company in HubSpot with additional companies surfaced as associated companies.

Bolten deal records migrate to HubSpot deals within a named pipeline. The Kanban stage names from Bolten become HubSpot pipeline stage labels. Each stage is created in HubSpot with a probability percentage and display order matching Bolten's original sequence. Deal amount, close date, owner, and deal name map directly. HubSpot's deal object does not have a native probability override per deal — stage probability applies by default.

Bolten's customizable Kanban funnel maps to a HubSpot pipeline. If Bolten has multiple funnels for different deal types, each funnel becomes a separate HubSpot pipeline. HubSpot Sales Hub Professional and above are required for multiple pipelines. Stage labels are value-mapped and each stage is assigned a display order and probability.

Bolten tasks and assignees migrate to HubSpot tasks. Subject, due date, assigned owner, and completion status transfer. Open tasks retain their status in HubSpot; completed tasks migrate with the completed timestamp preserved. Task associations to contacts, companies, and deals are rebuilt using HubSpot's association model.

Bolten call logs migrate as HubSpot call engagements. Call direction (inbound/outbound), duration, outcome, and notes transfer. The HubSpot call engagement records the owner, associated contact or deal, and original call timestamp from Bolten. Call recordings do not transfer since Bolten stores them on its own infrastructure.

Bolten email logs migrate as HubSpot email engagements. Subject, body, send/receive timestamp, and owner transfer. The engagement is associated to the relevant contact, company, or deal in HubSpot. Email attachments are flagged as files to re-upload since attachment storage paths differ between platforms.

Bolten meeting records map to HubSpot meeting engagements. Meeting title, start and end time, location, outcome, and attendees transfer. Owner and associated records are re-linked in HubSpot. Meetings created in Bolten's calendar view are mapped to the HubSpot meeting object with the original meeting date preserved.

Bolten notes migrate to HubSpot notes on the associated record (contact, company, or deal). Note body and original create date transfer. If Bolten notes contain rich text, the content is preserved as-is; complex formatting may be simplified to plain text to ensure compatibility with HubSpot's note rendering.

Bolten custom fields on contacts get created as HubSpot custom properties before the migration import runs. Field types are matched: text fields to text properties, pick-lists to dropdown properties, date fields to date properties. Value mappings for pick-list options are preserved per-option. Any Bolten field without a HubSpot equivalent is created as a text property for reference.

Bolten's native WhatsApp integration stores conversation threads within its platform. These conversations cannot be imported into HubSpot's timeline as native engagements because the WhatsApp sessions are Bolten-specific. We recommend reconnecting WhatsApp directly in HubSpot via HubSpot's WhatsApp Business integration after migration so new conversations land in HubSpot from the go-live date forward.

Bolten's AI-assisted automatic field-filling feature populates contact and deal properties using enrichment. These enriched values exist as property data in Bolten and will migrate as standard field values in HubSpot. However, the AI-fill logic itself is a Bolten workflow mechanism and has no HubSpot equivalent — the behavior must be recreated using HubSpot's AI tools or a third-party enrichment integration.

Bolten owner IDs and task assignees are resolved by email match against HubSpot users. We query HubSpot's user list and match each Bolten owner email to an existing HubSpot user. Unmatched owners are flagged before migration with a fallback owner assignment plan. Bolten users who do not yet have HubSpot accounts need to be provisioned first.