Migrate from Bidtracer to Microsoft Dynamics 365 Sales

Bidtracer leads map directly to Dynamics 365 Sales Lead table. The Lead record retains original createdate, modifieddate, and owner assignment. Bidtracer lead status values map to Dynamics 365 Lead Status picklist via value-by-value translation before the Lead qualifies into a Contact/Account.

Bidtracer opportunities (bid records) map to Dynamics 365 Sales Opportunity. The opportunity name, amount, close date, and probability translate directly. Bidtracer's bid stage names map to Dynamics 365 Opportunity Stage values per pipeline using value_mapping, preserving stage probability and forecast category from the destination side.

Bidtracer contacts map to Dynamics 365 Sales Contact table. Primary fields (name, email, phone, address) translate 1:1. Bidtracer contact records without a company association land as Contacts with no AccountId lookup, which is valid in Dynamics 365 and can be linked later.

Bidtracer company records map to Dynamics 365 Sales Account. Company name, website, address, industry, employee count, and annual revenue fields translate directly. Parent-company hierarchies in Bidtracer map to Account.ParentAccountId lookup, requiring the parent Account to migrate first. and preserves the original parent-child relationship in the target system.

Bidtracer custom fields migrate as new_-prefixed custom fields in Dynamics 365 Sales. Field type mapping handles text to SingleLine.Text, number to Whole.Number, currency to Currency, and date to DateAndTime.DateAndTime. Custom fields require creation in a Dynamics 365 solution before migration runs.

Bidtracer proposal attachments and O&M documents migrate as Note records in Dynamics 365 Sales, attached to the corresponding Opportunity. File size limits of 25MB per annotation apply. Large files may require SharePoint document location configuration for the destination org. and ensures consistent attachment handling across records.

Bidtracer activity records—calls, emails, follow-up tasks—map to Dynamics 365 Sales Task entity. Original timestamps, subject, description, and ownerId preserve from Bidtracer. Completed flag translates to ActivityPointer.StateCode and ActivityPointer.StatusCode. Each task's due date maps to the ScheduledEnd field, and any related notes also migrate as associated Note records. This ensures that all activity history is available in Dynamics 365 for reporting and follow-up tracking.

Bidtracer user IDs resolve by email match against Microsoft 365 users in the destination Dynamics 365 tenant. Unmatched owners flag before migration runs. Your admin either invites the user to Dynamics 365 first or assigns their records to a fallback owner for post-migration reassignment.

Bidtracer bid line items (materials, labor) migrate as Dynamics 365 Products with a corresponding Price List. Unit group, quantity, and pricing fields translate from Bidtracer's cost/sell structure into Dynamics 365's product pricing model. Products require a unique name and product structure before OpportunityProducts can link.

Bidtracer proposals generated from bid records map to Dynamics 365 Sales Quote. Quote status (Draft, Active, Revised), expiration date, and total amount translate directly. Quote Products link the migrated Products to the Quote with pricing from Bidtracer's proposal terms. and ensures accurate revenue forecasting based on the migrated pricing.

Bidtracer bid stage transition timestamps preserve as custom datetime fields on the Opportunity record (e.g., StageEnteredDate__c). Dynamics 365 Sales does not natively audit stage-change timestamps, so the original history lives in these custom fields for reporting continuity. and supports historical analysis of pipeline performance.

Bidtracer bid pipelines map to Dynamics 365 Sales Business Process Flows. Each Bidtracer pipeline becomes a separate Business Process Flow definition, with stage names translated to the corresponding Opportunity Stage picklist values. Teams use the Business Process Flow to guide sales reps through the bid lifecycle.