Migrate from BoldTrail to HubSpot

BoldTrail contact records map directly to HubSpot contacts. The BoldTrail owner field resolves by email match to a HubSpot user. BoldTrail lead status values map to HubSpot's hs_lead_status property via value mapping. Original create dates are preserved as a custom datetime field since HubSpot's CreatedDate is set at migration time.

BoldTrail leads that are not yet converted to contacts merge into HubSpot contacts with the lead status field set to match BoldTrail's lead state. If your BoldTrail account uses a separate Lead object for referral leads, those records also land as HubSpot contacts with a referral source custom property set from the source lead's origin field.

BoldTrail company records map 1:1 to HubSpot companies. Company name, domain, industry, phone, and address fields migrate as direct mappings. BoldTrail's parent-company hierarchy maps to HubSpot's parent company association. Multi-contact companies collapse cleanly in HubSpot's company-contact relationship model. Industry taxonomy values are mapped value-by-value to ensure consistent categorization in HubSpot.

BoldTrail has a native Property object with MLS number, listing price, status, bedrooms, bathrooms, square footage, and property address fields. HubSpot has no native real estate property object. FlitStack creates a custom property field set on HubSpot deals and maps BoldTrail property fields into those custom fields. Each property becomes a deal linked to the associated contact and company records.

BoldTrail Transaction records hold deal amount, transaction status (Active, Pending, Under Contract, Sold, Closed), milestone dates (inspection, appraisal, closing), and agent role assignments. These map to HubSpot deals with a custom stage mapping defined per your transaction lifecycle. Milestone dates that have no HubSpot equivalent are preserved as custom date fields on the deal.

BoldTrail tasks and follow-up reminders map to HubSpot engagements — tasks for to-do items, meetings for scheduled property showings or client appointments, and calls for logged phone conversations. Original timestamps, owners, and associated contact or deal links are preserved across all activity types.

BoldTrail email logs migrate to HubSpot as email engagements with subject, body, direction (sent or received), timestamp, and recipient information preserved. Emails are linked to the correct HubSpot contact and company records. Attachments referenced in email bodies are flagged for re-upload as HubSpot files.

BoldTrail notes on contacts, properties, or transactions migrate as HubSpot notes with body text, author, and original create date preserved. Rich-text formatting is maintained where BoldTrail stores it. Notes are associated to the same HubSpot record (contact, company, or deal) based on the BoldTrail association.

BoldTrail files attached to contacts, properties, or transactions are downloaded and re-uploaded to HubSpot Files, associated to the matching HubSpot record. HubSpot's file size limits apply (25MB default). Files originally embedded in BoldTrail email bodies are extracted, rehosted, and linked in the migrated email body.

BoldTrail owner records resolve to HubSpot users by email address matching. Unmatched owners are flagged before migration — your team either creates HubSpot user accounts for them or assigns their records to a designated fallback owner. Role labels (Listing Agent, Buyer's Agent, Transaction Coordinator) are preserved as custom properties on the owner record.

BoldTrail property custom fields — such as HOA fees, lot size, year built, property type, listing source, and showing instructions — have no HubSpot native equivalents. FlitStack creates custom properties on the HubSpot deal object to hold each custom field value. Field types are matched (number, text, date, picklist) to maintain data integrity.

BoldTrail Smart Campaigns and drip sequences are automation logic — trigger conditions, wait steps, and action sequences tied to lead status changes and contact properties. These do not have a HubSpot equivalent because HubSpot separates CRM data from automation into distinct objects. FlitStack exports your BoldTrail campaign definitions as a structured reference document so your HubSpot admin can rebuild them in HubSpot Workflows.

BoldTrail IDX websites and landing pages are CMS assets built inside BoldTrail's platform. They do not migrate to HubSpot — HubSpot Content Hub is a separate product with its own CMS and requires a rebuild. Property listings and agent bio pages need to be recreated in HubSpot Content Hub or linked from your existing website.

BoldTrail BackOffice handles commission tracking, transaction milestones, and brokerage-level reporting. This is a separate product within the BoldTrail ecosystem. HubSpot CRM does not include commission or back-office transaction management — those workflows must continue in BoldTrail BackOffice or migrate to a dedicated commission management tool. Data in BackOffice is accessed separately from the BoldTrail CRM export.