Migrate from Thunderbolt Pipeline to Pipedrive

Thunderbolt Pipeline Person records map directly to Pipedrive Person records. All standard contact fields — name, email, phone, address, job title, and associated company — transfer as-is. Name fields from Thunderbolt are concatenated into Pipedrive's single name field. Person records without an associated company land as standalone Persons in Pipedrive with no org_id link. Any custom properties on the Person record are created as custom fields in Pipedrive before migration begins.

Thunderbolt Pipeline Company records map directly to Pipedrive Organization records. Fields including company name, domain or website URL, physical address, industry classification, and employee count transfer as-is. Parent-child company hierarchies in Thunderbolt Pipeline map to Pipedrive's parent_org_id field on the Organization object. The parent Organization must be migrated before the child so the relationship link resolves correctly during the migration run.

Thunderbolt Pipeline Bid Record is the primary entity containing bid amount, bid status, contract type, trade type, award date, and estimator assignment. This maps to Pipedrive Deal, with bid-specific metadata stored in custom fields on the Deal. Bid stage names in Thunderbolt map to Pipedrive stage values within the designated pipeline.

Each named stage in Thunderbolt Pipeline's bid pipeline maps to a corresponding Pipedrive stage value within the migrated pipeline. Stage ordering, probability percentages, and forecast category are configured per Pipedrive's stage settings. We apply the same stage probability model used in Thunderbolt if the values are available in the export.

Thunderbolt Pipeline tracks bid status as a discrete property on the Bid Record. Pipedrive Deal has no native bid-status field. We create a Bid_Status__c custom pick-list field on the Deal object and map each Thunderbolt status value to the corresponding Pipedrive stage plus a custom field value for reference.

Construction contract and trade classifications in Thunderbolt Pipeline — such as Lump Sum, Cost Plus, or specific trade categories — do not have Pipedrive native equivalents. We create Contract_Type__c and Trade_Type__c custom pick-list fields on the Deal object and map values one-for-one from the Thunderbolt export.

Thunderbolt Pipeline owner and estimator assignments resolve by email match against Pipedrive users. Records with no matching Pipedrive user are flagged before migration; you can invite the user to Pipedrive first or assign to a fallback owner. Original owner name is preserved as Owner_Source__c text field for audit continuity.

Call logs, meeting records, and notes attached to a Bid Record in Thunderbolt Pipeline migrate as Pipedrive Activities linked to the corresponding Deal. Notes migrate as Pipedrive Notes. Timestamps, activity type, and owner assignment are preserved. Attachments require re-upload to Pipedrive's file storage.

Thunderbolt Pipeline supports N:N contact-to-company associations. Pipedrive Persons have a single primary org_id. For contacts linked to multiple companies in Thunderbolt, we assign the most recently modified company as the primary org and surface the additional company links through linked_contact relations in Pipedrive.

Any custom properties configured in Thunderbolt Pipeline for Bid Records, Contacts, or Companies are created as custom fields in Pipedrive on the corresponding object. Pipedrive generates a 40-character hash key for each custom field — we map these dynamically during migration so field values land in the correct Pipedrive custom field regardless of the key generated during setup.

File attachments associated with Bid Records in Thunderbolt Pipeline — such as bid documents, drawings, or spec sheets — are downloaded and re-uploaded to the corresponding Deal record in Pipedrive as Files. Pipedrive's per-plan storage limits apply: Lite includes 5GB per user, scaling up to Unlimited on Enterprise. Files exceeding plan limits require storage management before migration.

Thunderbolt Pipeline records stage-transition timestamps for each bid as it moves through the pipeline. Pipedrive Deal tracks current stage only with no native history log. We create Stage_History__c as a long-text custom field on the Deal, storing each transition as a formatted entry (stage name, timestamp, user) for reporting continuity.