Migrate from Thunderbolt Pipeline to HighLevel

Thunderbolt Contact records map directly to HighLevel Contacts using a straightforward field-to-field correspondence. All standard fields including email address, phone number, full name, and physical address transfer as-is without transformation. Custom per-contact fields defined in Thunderbolt (such as union status, trade certifications, or licensing details) also transfer to their corresponding HighLevel custom field equivalents. Owner resolution during migration uses email address matching against existing HighLevel user accounts — any owners whose emails cannot be matched are flagged in a pre-migration report for your team to resolve before the final migration commit.

Thunderbolt Company records — including general contractor and prime company names, billing addresses, and corporate contact information — map directly to HighLevel Companies. Parent-company hierarchies and subsidiary relationships are preserved during migration using HighLevel's native Company relationship fields. For companies with multiple associated contacts in Thunderbolt, the migration collapses these to the primary contact link in HighLevel, ensuring clean data structure without duplicate company entries for the same organization.

Thunderbolt bid records represent the primary migration object in most construction CRM transfers. Each individual bid record maps to a corresponding HighLevel Opportunity, which is then linked to the appropriate Contact or Company record. Key transformations include: bid amount becomes the Opportunity monetary value field, bid submission date becomes the Opportunity created date, and the Thunderbolt bid status translates directly to the matching HighLevel pipeline stage. The Opportunity name defaults to the original bid name or is auto-generated as a concatenation of the contact name plus project description for clarity.

Thunderbolt's construction-specific bid stages — including Bid Submitted, Awarded, Lost, Won, and Not Bid — require value-by-value mapping to your configured HighLevel pipeline stage names. This is a manual step that must be completed before migration runs, as HighLevel pipeline stages must already exist to receive mapped data. After the stage name mapping is confirmed in the migration plan, stage probability percentages and forecast categories are applied according to your HighLevel pipeline stage configuration settings.

Thunderbolt tracks the trade or work type associated with each bid record, covering categories such as electrical, plumbing, HVAC, roofing, concrete, and general contracting. HighLevel's standard Opportunity object includes no native field for this construction-specific classification. To preserve this data, FlitStack AI creates a custom text or pick-list field (Trade_Type__c) on the HighLevel Opportunity object and populates it directly from the corresponding Thunderbolt bid record's trade type value.

Thunderbolt stores contractor license numbers, bonding information, and regulatory credentials directly on company records for each contractor or subcontractor. HighLevel's standard Company object does not include fields for license numbers or bonding limits. To preserve this critical construction-industry data, FlitStack AI creates custom text fields (License_Number__c and Bonding_Limit__c) on the HighLevel Company object, maintaining the full license information for each migrated company record.

Thunderbolt's labor-forecasting and crew-capacity planning data has no direct equivalent in HighLevel's native object model. To handle this, FlitStack AI creates a HighLevel Custom Object called Workforce_Forecast__c with dedicated fields for labor hours, crew size, forecast date, and related workforce metrics. Historical forecast records from Thunderbolt are migrated as read-only entries to preserve the data for reporting purposes. Note that any active workforce planning automation logic — such as triggers that notify crew leads of upcoming labor demand — must be rebuilt using HighLevel Workflows, as automation rules do not migrate between platforms.

Thunderbolt's built-in compliance module stores critical construction documents — including bond certificates, insurance policies, union agreements, and regulatory filings — attached directly to bid records. HighLevel handles file attachments differently, storing them as Files that link to CRM records. During migration, FlitStack AI downloads all Thunderbolt compliance attachments and re-uploads them to HighLevel Files, then establishes the appropriate links to the corresponding Opportunity record. The original filename and attachment timestamp are preserved in the HighLevel File metadata for audit trail purposes.

Thunderbolt's real-time job notes and field observations — documenting progress updates, issue flags, client communications, and site conditions — map directly to HighLevel Notes attached to the appropriate Contact, Company, or Opportunity record. The original note author and creation timestamp are both preserved during migration, maintaining the full audit trail and attribution for each observation. Note that rich-text formatting present in Thunderbolt notes may be simplified to plain text in HighLevel depending on the formatting complexity involved.

Thunderbolt's automated bid-deadline reminders, follow-up notifications, and escalation alerts are configured within Thunderbolt's proprietary automation engine and cannot be exported in a format compatible with HighLevel Workflows. HighLevel's Workflow system uses a different trigger-and-action model based on Opportunity stage changes, date-based triggers, and tag-based conditions. FlitStack AI exports your Thunderbolt automation logic — including trigger events, recipient lists, message templates, and escalation rules — as a detailed text reference document. Your HighLevel administrator then uses this document as a rebuild checklist to recreate equivalent automations in HighLevel Workflows.

Thunderbolt file attachments stored on bid records, contact records, or company records are downloaded from the source system and re-uploaded to HighLevel Files. Each file is then linked to its corresponding record in HighLevel — bid attachments link to the Opportunity, contact attachments link to the Contact, and company attachments link to the Company. File size limits apply based on your HighLevel storage configuration plan, and large files may require compression or resizing before re-upload to ensure successful migration.

Thunderbolt team members and users who own bid records are resolved during migration by matching their email address against existing HighLevel user accounts. This email-to-user resolution ensures that migrated Opportunities retain proper ownership assignments in HighLevel. Any Thunderbolt owners whose email addresses do not match an existing HighLevel user are flagged in a pre-migration report. Your team then decides whether to create new HighLevel user accounts for these individuals or assign their records to a designated fallback user before the migration finalizes.