Migrate from Thunderbolt Pipeline to HubSpot

ThunderBolt organizations map 1:1 to HubSpot companies using direct field mapping for company name, domain, address, and industry fields. Multi-location organizations from ThunderBolt create one HubSpot company per physical location — use HubSpot's company hierarchy feature to link parent and child locations under a single organizational structure, preserving regional reporting and location-based filtering capabilities in HubSpot dashboards.

ThunderBolt contacts migrate to HubSpot contacts with direct field mapping for name, email, phone, job title, and address. ThunderBolt allows multiple contacts per organization — each contact in ThunderBolt creates a corresponding HubSpot contact associated to the migrated company via the company association.

ThunderBolt's bid record maps to a HubSpot deal. Bid amount becomes deal amount; bid_submitted_date becomes the close date (or a custom property Original_Bid_Submitted_Date__c if the deal hasn't closed). Bid probability maps to HubSpot's dealstage probability values. Bid name becomes deal name.

ThunderBolt bid statuses (Bid Submitted, Under Review, Shortlisted, Awarded, Lost) map value-by-value to HubSpot deal stages. Each status requires a corresponding stage in the target HubSpot deal pipeline. Stage probabilities are re-applied based on HubSpot's stage configuration defaults or your specified probability values.

HubSpot has no native Job object — we create a custom Jobs object (requires Sales Hub Professional+). Job name, contract value, job stage, start date, and completion date migrate as custom properties on the Jobs object. The Jobs object gets its own pipeline matching ThunderBolt's job stage progression.

ThunderBolt's resource allocation records (assigned workers, labor hours, trade type per job) collapse into a set of custom properties on the HubSpot Jobs custom object: Resource_Crew_Size__c, Primary_Trade__c, Labor_Hours_Allocated__c, Foreman_Email__c. Individual worker assignments migrate as a custom Notes section or a secondary custom object if tracking at the individual level is required.

ThunderBolt compliance properties (union status, bonding capacity, insurance expiry, certification flags) have no native HubSpot equivalent. We migrate them as read-only custom properties — Compliance_Status__c, Bonding_Capacity__c, Insurance_Expiry_Date__c — on the Company record for general compliance and on the Deal for project-specific requirements.

Bid attachments from ThunderBolt are downloaded and re-uploaded to HubSpot Files, then associated to the corresponding migrated deal. File size limits follow HubSpot's upload constraints (25MB default per file via the UI; larger files require file hosting integration). We log the original ThunderBolt document URL in a custom property for audit purposes.

ThunderBolt notes, comments, and activity timestamps migrate as HubSpot engagements. Timestamps and owner email are preserved. Each engagement is associated to the parent contact, company, or deal record. ThunderBolt's internal activity log (stage-change events) migrates as timeline notes for audit continuity.

ThunderBolt user accounts are resolved to HubSpot users by matching the email address. Users with no HubSpot account are flagged before migration — you can either create a HubSpot seat for them or assign their records to a fallback owner. ThunderBolt's role-based permissions do not migrate since HubSpot's role and permission model is destination-side configuration.

ThunderBolt trade-type fields (electrical, mechanical, plumbing, civil, etc.) migrate to a HubSpot custom pick-list property: Trade_Type__c. Value-by-value mapping applies if pick-list values in ThunderBolt differ from HubSpot's options. Used for segmentation and filtering in HubSpot's deal and custom object views.

ThunderBolt's bonding capacity field represents the maximum project value a contractor can bid on without requiring a bond. This migrates as Bonding_Capacity__c on the HubSpot Company record as a read-only custom currency field. Bonding eligibility decisions remain a manual process in HubSpot — your team evaluates bids against this capacity threshold outside the CRM workflow using this migrated reference data.