Migrate from Thunderbolt Pipeline to Freshsales

Thunderbolt Pipeline Customers who are individuals (contacts without a company role) migrate directly to Freshsales Contacts. The contact's name, email, phone, and address fields map to Freshsales Contact fields. Freshsales requires each Contact to have a valid email address — contacts without an @ symbol are flagged before migration for pre-flight correction or manual exception handling.

Thunderbolt Pipeline Customers that are companies or organizations (identified by having a domain or no individual contact name) migrate as Freshsales Accounts. The company name maps to Account Name, domain to Website, industry to Industry pick-list, and employee count to NumberOfEmployees. Account records must exist before Contacts can link to them via the AccountId lookup in Freshsales.

Thunderbolt Pipeline sub-records tagged as individual Contacts (name, email, phone) map directly to Freshsales Contacts. All standard contact fields — first name, last name, email address, phone number, job title, address fields — transfer as direct field mappings. Owner resolution runs by email match against Freshsales users.

Thunderbolt Pipeline Bids are the closest equivalent to Freshsales Deals (Opportunities). We map Bid Name to Deal Name, Bid Amount to Deal Amount, Bid Status to Deal Stage via value mapping, and Expected Close Date to Close Date. Pipeline mapping in Freshsales is plan-dependent — Growth supports one pipeline, Pro and Enterprise support multiple pipelines and multi-stage views.

Thunderbolt Pipeline bid lifecycle stages (e.g., Invite Received, Scope Reviewed, Bid Submitted, Won, Lost) map to Freshsales Deal Stage values via a value-mapping table built from your source stage names. Stage probability percentages and forecast category are re-applied based on Freshsales stage configuration. We preserve original stage-transition timestamps in custom datetime fields on the Deal record.

Thunderbolt Pipeline Projects represent awarded or active construction projects — these map to Freshsales Deals where the Deal Name and Amount carry forward, and project-specific fields (project type, start date, completion date, project manager) migrate as custom fields on the Deal. Active projects keep their original create timestamps in Original_Create_Date__c since Freshsales sets CreatedDate at import time.

Thunderbolt Pipeline Workforce Planning records have no equivalent native object in Freshsales. On Freshsales Enterprise plans we create a Custom Module (Workforce_Records__c) matching the source record schema — fields include trade, labor count, start date, end date, and assignment status. Records link back to the parent Deal or Account via a lookup relationship. For Growth and Pro plans, workforce data is stored in custom fields on the Account or Deal.

Thunderbolt Pipeline Resource Planning data (equipment, crew allocation, material scheduling) is construction-specific and not representable in Freshsales standard objects. We store resource type, quantity, and allocation date in a custom text area field (Resource_Planning_Data__c) on the parent Deal, with a note in the migration plan that this data should be reviewed and potentially re-entered in a project management tool post-migration.

Thunderbolt Pipeline task records (bid follow-up tasks, document requests, compliance checks) migrate as Freshsales Tasks. Task Subject maps to Task Subject, due date to Due Date, and owner to OwnerId resolved by email match. Completed status and completion timestamps are preserved. Original Thunderbolt Pipeline task IDs are stored in Source_System_ID__c for traceability.

Thunderbolt Pipeline file attachments linked to Customers, Bids, or Projects are downloaded, re-uploaded to Freshsales Files, and linked to the corresponding record. Freshsales file size limits of 25MB per file apply — larger files are flagged for chunked upload or alternative storage with a reference link stored on the record.

Thunderbolt Pipeline notes migrate as Freshsales Notes. The note title and body text transfer directly. Rich-text formatting in notes is preserved where the source export supports HTML encoding. Original note timestamps and owner IDs are stored in Source_System_ID__c and Original_Create_Date__c for audit continuity.