Migrate your Bidtracer data

Bidtracer's CRM tracks leads with standard fields (name, contact info, source). We preserve lifecycle stage as a custom property during migration and map to the destination's corresponding lead or contact object.

Contact records include phone, email, company association, and communication history. Bidtracer stores contact details per construction-project context, so we map company relationships carefully to avoid orphaned records.

Company records hold billing, trade type, and association to multiple projects. We map company names and trade tags, noting that some companies are subcontractors rather than direct customers.

Opportunities in Bidtracer track a construction bid from initial budget through award. We map stage, estimated value, and close date, preserving bid-specific fields that may not exist in standard CRM schemas.

Bid records are a first-class object tracking the full bid lifecycle — budget, estimator assignment, invite list, closing date, and award status. We migrate bid records with their associated line items and document references intact.

Invitation records track which subcontractors were invited to a bid, their response status, and what plan/spec documents they accessed. We preserve invitee email and response status; full document access logs require separate handling.

Proposals are generated from bid data and sent to customers. We map proposal text, pricing, and attachment references. Bidder copy-from-previous-proposal data requires value-level mapping.

Project records in Bidtracer carry the job post-award through completion. We map project name, stage, assigned users, and dates. Phase or milestone tracking inside projects may need custom field mapping to the destination system.

Bidtracer supports planroom documents, specs, addenda, and uploaded files per bid or project. We migrate document references and metadata; actual file blobs require a separate transfer step with attention to the platform's file-size handling.

The Service Agreements module stores recurring contract terms tied to customers or properties. We map agreement type, start/end dates, and renewal status as custom fields in the destination.

Bidtracer supports limited custom fields within modules. We inventory custom field definitions during scoping and apply value mapping for dropdown, text, and numeric types.

User records include name, email, and role. We map owner assignment on bids and projects; Bidtracer user-role granularity may differ from the destination's permission model.

The BAC Estimating and Security Estimating modules store node-tree estimating structures with line-item pricing. We extract the itemized takeoffs and cost data as structured records, noting that the tree structure itself may not translate directly to flat-destination schemas.