Migrate from Thunderbolt Pipeline to Microsoft Dynamics 365 Sales

Thunderbolt bid records migrate directly to Dynamics 365 Opportunities as the destination entity. The bid name field becomes Opportunity.Name, the award date maps to CloseDate, estimated value transfers to EstimatedRevenue, and bid status translates to Opportunity Stage through value mapping rules configured per source stage label. Each Thunderbolt bid stage (Bid, Submitted, Under Review, Awarded, Lost) maps to a corresponding Dynamics 365 stage name with probability percentages carried forward as a custom field. Stage-entered timestamps from Thunderbolt require custom datetime fields in Dynamics 365 since the standard CreatedOn field captures migration timestamp rather than original entry date.

Contact records migrate on a one-to-one basis to Dynamics 365 Contacts. The full name field from Thunderbolt splits into separate FirstName and LastName fields in Dynamics 365. Email addresses, phone numbers, and job titles transfer directly without transformation. The primary company association from Thunderbolt connects to the AccountId lookup in Dynamics 365, requiring the corresponding Account record to exist first in the migration sequence to maintain referential integrity.

Thunderbolt company records map to Dynamics 365 Accounts with straightforward field translations. Company name becomes Account.Name, domain maps to Website, industry values translate via value mapping to the Dynamics 365 Industry pick-list codes, and employee count transfers to NumberOfEmployees. Billing address components from Thunderbolt split across Address1_Line1, Address1_City, Address1_StateOrProvince, and Address1_PostalCode fields in the destination.

Thunderbolt pipeline stages (Bid, Submitted, Under Review, Awarded, Lost) translate value-by-value to Dynamics 365 stage names. Each stage mapping carries forward the probability percentage from Thunderbolt as a custom field since Dynamics 365 derives probability from business process flow stage step weights. Thunderbolt stage-entered timestamps require custom datetime fields in Dynamics 365 to preserve the original progression timeline.

Thunderbolt workforce planning records — labor categories, estimated hours, crew assignments — have no native Dynamics 365 equivalent. FlitStack creates a Dataverse custom table (WorkforceAllocation__c) with a lookup to the corresponding Opportunity so resource plans attach to bids in the destination.

Thunderbolt's consolidated bid invite feature (email-to-bid) stores invite metadata that does not map to standard Dynamics 365 entities. A custom BidInvite__c Dataverse table with a lookup to the parent Opportunity preserves invite sender address, recipient address, timestamp, and bid reference for compliance and audit purposes without relying on Dynamics 365's native email tracking which requires separate EmailServerProfile configuration.

Thunderbolt compliance records (insurance certificates, bonding limits, safety attestations) require a Dataverse custom table since Dynamics 365 lacks native compliance tracking. A custom ComplianceRecord__c table with columns for certificate type, expiration date, and carrier information links to the relevant Account or Opportunity. Compliance documents attach via SharePoint/OneDrive integration on the custom record, requiring SharePoint integration to be enabled and document locations mapped before migration.

Thunderbolt notes attached to bids or contacts migrate as Dynamics 365 Notes with preserved creation timestamps and owner assignment from the source record. Activity logs such as calls logged against a bid transfer as Tasks with Type='Call', preserving the original call duration and start time from Thunderbolt. This ensures historical interaction context remains available for relationship intelligence in Dynamics 365.

Thunderbolt user accounts resolve by matching email addresses against Dynamics 365 SystemUser records during migration. Unmatched users are flagged in a pre-flight report generated before the migration run — your team either provisions the missing Dynamics 365 user accounts or assigns records to a designated fallback owner to prevent orphaned opportunities that cannot be assigned post-load.

Thunderbolt file attachments on bids and projects download from the source API and re-upload to Dynamics 365 SharePoint integration. Files exceeding Dynamics 365's 32MB per-attachment limit are flagged in the migration report for manual chunked upload or SharePoint direct link reference to avoid upload failures.

Thunderbolt custom fields on bids such as bonding percentage, insurance carrier name, and CSI division codes require Dataverse custom columns on the Opportunity table with the __pc naming convention. Field type mapping converts Thunderbolt field types to equivalent Dataverse column types: decimal for percentages, text for carrier names, and pick-list for CSI codes. The __c suffix on custom columns follows Dataverse naming standards and ensures Power Platform tooling recognizes these as custom fields.