Migrate from Bidtracer to Salesforce Sales Cloud

Bidtracer Client records map to Salesforce Account. Primary company address, phone, and domain map directly. Parent-child company hierarchies in Bidtracer map to Salesforce ParentId — circular references flagged and flagged before migration runs. We validate each parent exists before linking, and apply duplicate detection using name and address matching.

Bidtracer Contact records map to Salesforce Contact with AccountId lookup — requires the Client→Account mapping to resolve first. Multi-company contacts (one Contact linked to multiple Bidtracer Clients) collapse to one primary AccountId plus Account Contact Relationships in Salesforce. We assign the primary client as AccountId and create additional Account Contact Relationships for other linked clients, preserving full visibility.

Bidtracer CRM leads map to Salesforce Lead with Bidtracer lead status mapped to Salesforce Lead Status via value-mapping table. Owner resolution by email match against Salesforce users before migration commits. We also preserve the original lead score and source information, and we flag any leads with missing email addresses for manual review prior to import.

Bidtracer Bid records map to Salesforce Opportunity. Bid status (Awarded, Pending, Lost, Withdrawn) maps to Opportunity StageName via a pre-built value-mapping table. Bid amount maps to Opportunity Amount. Pipeline-specific stage values require Salesforce Sales Process assignment post-migration. We also migrate custom fields such as Bid_Type__c, Division__c, and Contract_Type__c, and set the Opportunity's OwnerId based on the Bid owner email lookup.

Bidtracer bid-status pick-list values (e.g., Awarded, Pending, Lost, Withdrawn) are mapped one-to-one to Salesforce StageName values. Your Salesforce admin pre-creates matching stage names in Setup before the migration runs; stage probability re-applied per Salesforce business process rules. We provide a StageName mapping worksheet and verify the existence of each value in your org prior to data load, reducing the risk of null stages.

Bidtracer's invitation-to-bid records track vendors per bid with response status and bid amount. Salesforce has no native vendor-per-opportunity tracking object. We create a custom Bid_Invitation__c junction object with Vendor__c (Contact lookup), Bid__c (Opportunity lookup), Response_Status__c, Bid_Amount__c, and Closing_Date__c. The junction object also includes a custom link to the original Bidtracer invitation ID for traceability, and we set field-level security so only relevant sales roles can view sensitive vendor pricing.

Bidtracer's drag-and-drop estimating tool stores node trees with parent-child relationships, line items, quantities, unit costs, and markups per project bid. We create a custom Estimate__c object with Node_Reference__c, Line_Items__c (long text), Unit_Cost__c, Quantity__c, Markup__c, and a self-referential Parent_Node__c lookup for hierarchy.

Bidtracer Project Management records map to a custom Project__c object linked to the corresponding Opportunity. Fields include Project_Name__c, Bid_Date__c, Awarded_Date__c, Project_Start__c, Project_End__c, Awarded_Amount__c, and Status__c pick-list.

Bidtracer Service Agreements tool records map to custom Service_Agreement__c with Start_Date__c, End_Date__c, Agreement_Type__c pick-list, Amount__c, and related Account lookup. Service Repair records map similarly with custom status and priority fields. We also include a link to the associated Project__c for reference and set validation rules to enforce date ranges. Service Repair records include a custom Priority__c pick-list and a Status__c field that aligns with your internal workflow stages.

Bidtracer's free customizations and per-user field additions map to Salesforce custom fields with __c suffix on the target object. We create these during schema-setup phase before data loads. Field type mapping: text→Text, number→Number, date→Date, picklist→Picklist. We also preserve help text and default values, and map calculated fields to Salesforce formula fields where possible. A post-migration field inventory report details each source field and its target custom field.

Bidtracer's Outlook integration emails map to Salesforce Task records with Type='Email', Subject, Description, and ActivityDate preserved. Owner matches by email. Tasks are linked to the corresponding Account or Opportunity by ParentId. We also capture email attachments and store them as Salesforce Files related to the Task. Emails without a related Account or Opportunity are attached to a default 'General' Task for review.

Bidtracer file attachments (plans, proposals, submittals) are downloaded and re-uploaded to Salesforce Files via the ContentDocument model. File size limits apply: Salesforce default 25MB per file. Inline images in notes are extracted and rehosted. We preserve the original file name and creation date, and link each to the related Account, Contact, or Opportunity via ContentDocumentLink. Files over 25MB are split and the admin is notified.