CRM migration
Field-level mapping, validation, and rollback between Bidtracer and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Bidtracer
Source
Nutshell
Destination
Compatibility
12 of 12
objects map 1:1 between Bidtracer and Nutshell.
Complexity
CModerate
Timeline
24–72 hours
Overview
Bidtracer is a construction-vertical CRM built around bid management, invitation-to-bid workflows, estimating tools, and project management modules. Its data model centers on Companies, People, Deals, and a collection of construction-specific modules (BAC Estimating, Security Estimating, Engineering, Project Management, Service Agreements, Service Repair) that have no equivalent in standard CRMs. Nutshell is a generalist CRM using a People/Companies/Leads/Deals/Activities model with custom field support and an open JSON-RPC API. We map Bidtracer's Companies to Nutshell Companies, People to Nutshell People, and Deals to Nutshell Deals. Bidtracer's custom properties on each object migrate to Nutshell custom fields. Construction-specific modules (bid tracking, estimating, submittals, RFIs, CORs) have no Nutshell equivalent — those records cannot migrate and must be evaluated separately. Nutshell's email integration and activity tracking replace Bidtracer's email logging, calls, and meeting notes. Migration runs via Nutshell's JSON-RPC API with batch operations and rate-limit handling. Owner assignment resolves by email match against Nutshell users. A delta-pickup window captures any Bidtracer changes made during cutover. Reports, dashboards, and workflows are not migrated — we deliver an export of workflow definitions as a rebuild reference.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Bidtracer object lands in Nutshell, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Bidtracer
People (Contacts)
Nutshell
People
1:1Bidtracer People records map directly to Nutshell People. Standard contact fields (name, email, phone, address) transfer as-is. Bidtracer's primary company association maps to Nutshell's Company link. Owner is resolved by email match to a Nutshell user; unmatched owners are flagged for manual assignment before the migration commits.
Bidtracer
Companies
Nutshell
Companies
1:1Bidtracer Companies map 1:1 to Nutshell Companies. Company name, address, phone, website, industry, and employee count transfer directly. Parent-company relationships are preserved as Nutshell's parent company link. Nutshell does not support multi-company associations natively — secondary company links on a person collapse to the primary Company assignment.
Bidtracer
Leads
Nutshell
Leads
1:1Bidtracer leads that have not yet converted to contacts map to Nutshell Leads. Lead status, source, and assigned owner transfer as standard fields. Bidtracer's lead-score property migrates as a Nutshell custom number field if it exists. Leads that have been converted in Bidtracer (with a won deal attached) route to People as contacts.
Bidtracer
Deals
Nutshell
Deals
1:1Bidtracer Deals map to Nutshell Deals with deal name, amount, stage, expected close date, and owner transferred directly. Bidtracer's deal stage values are mapped to Nutshell's pipeline stage values via a value-mapping table built during planning. The deal's linked People and Company transfer as Nutshell's person and company associations.
Bidtracer
Bid Management
Nutshell
Deals + Custom Fields
1:1Bidtracer's Bid Management module (tracking budget, invite subcontractors, send proposals) has no Nutshell equivalent. Bid records, bid amounts, subcontractor lists, and proposal status migrate as Nutshell Deals with Bidtracer's bid-specific fields stored as custom fields. Active bid-tracking workflows cannot migrate — a Bidtracer workflow export is provided for manual rebuild in Nutshell.
Bidtracer
Invitation To Bid Tool
Nutshell
No equivalent
1:1Bidtracer's Invitation To Bid Tool (giving subcontractors free access to plans, tracking addenda and bulletins) has no Nutshell equivalent. Invitation records, plan access logs, and addendum history do not migrate. Subcontractor contact information migrates as People records; the invitation metadata is documented for rebuilding in a dedicated bid-invitation tool.
Bidtracer
BAC Estimating / Security Estimating
Nutshell
No equivalent
1:1Bidtracer's estimating modules store drag-and-drop line items, pricing tables, and scope configurations that are construction-domain specific. Nutshell has no estimating module. Estimating data does not migrate — we export the estimating records as a structured CSV reference for your team to evaluate against dedicated estimating software.
Bidtracer
Project Management
Nutshell
No equivalent
1:1Bidtracer's Project Management module (RFIs, submittals, CORs, schedule of values) has no Nutshell equivalent. Project records, RFI logs, and change-order history do not migrate. We extract project-linked contacts as People records. The project metadata is exported for evaluation against dedicated project management platforms like Procore or Autodesk Construction Cloud.
Bidtracer
Service Agreements / Service Repair
Nutshell
No equivalent
1:1Bidtracer's Service Agreements and Service Repair modules (field technician scheduling, preventive maintenance proposals, quick-start mobile selling) have no Nutshell equivalent. Service records, agreement terms, and tasking configurations do not migrate. Customer contact information from service records migrates to Nutshell People.
Bidtracer
Attachments / Files
Nutshell
Attachments
1:1Bidtracer file attachments (plans, specs, proposals, submittal documents) migrate to Nutshell Attachments on the corresponding record (People, Companies, or Deals). Large files are re-uploaded to Nutshell's storage. Inline images in notes are downloaded and rehosted. Nutshell's file size limits apply — files over the platform limit are flagged before migration commits.
Bidtracer
Custom Properties (all objects)
Nutshell
Custom Fields
1:1Bidtracer custom properties on People, Companies, and Deals (e.g., Division, License Number, Trade Specialty, Union Status, Safety Rating, Prevailing Wage Flag) are created as Nutshell custom fields per object type. Custom field type is inferred from Bidtracer's data (text, number, date, or pick-list). Bidtracer's per-property settings (required, read-only) are noted for manual recreation in Nutshell's field settings.
Bidtracer
Email / Call / Meeting Activities
Nutshell
Activities
1:1Bidtracer's email logs, call records, and meeting notes map to Nutshell Activities on the corresponding People or Deal record. Original timestamps, activity type, and owner are preserved. Nutshell's integrated email tracking (Gmail/Outlook add-in) replaces Bidtracer's Outlook integration going forward — past logged emails migrate but future email tracking requires Nutshell's add-in to be installed.
| Bidtracer | Nutshell | Compatibility | |
|---|---|---|---|
| People (Contacts) | People1:1 | Fully supported | |
| Companies | Companies1:1 | Mapping required | |
| Leads | Leads1:1 | Mapping required | |
| Deals | Deals1:1 | Fully supported | |
| Bid Management | Deals + Custom Fields1:1 | Fully supported | |
| Invitation To Bid Tool | No equivalent1:1 | Fully supported | |
| BAC Estimating / Security Estimating | No equivalent1:1 | Fully supported | |
| Project Management | No equivalent1:1 | Fully supported | |
| Service Agreements / Service Repair | No equivalent1:1 | Fully supported | |
| Attachments / Files | Attachments1:1 | Not supported | |
| Custom Properties (all objects) | Custom Fields1:1 | Fully supported | |
| Email / Call / Meeting Activities | Activities1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Bidtracer gotchas
No public REST API for bulk export
ActiveX requirement blocks file downloads on modern browsers
Per-export convenience charge is not disclosed upfront
Start-up and training fees on smaller tiers
Nutshell gotchas
Contact tier limits enforced on import
No bulk API endpoint requires paginated extraction
Email sequences not exportable via API
Foundation plan disables key sales features
Pair-specific challenges
Migration approach
Profile Bidtracer data and identify migratable versus non-migratable modules
We connect to Bidtracer via your exported data (CSV or API) and profile every record type — People, Companies, Leads, Deals, and Activities. We identify which Bidtracer modules are migratable (People, Companies, Deals, Activities, Attachments) and which are not (Bid Management, Estimating, Project Management, Service modules). We document the record counts, custom property names and types, file attachment volumes, and owner distribution. This produces a migration scope document that both teams sign off on before any data moves.
Create Nutshell custom fields and configure the target schema
Before data lands in Nutshell, we deliver a custom field creation guide based on Bidtracer's custom properties. Your Nutshell admin creates the fields (Division__c, License_Number__c, Trade_Specialty__c, Bid_Amount__c, Bid_Status__c, etc.) under Settings > Custom Fields. We verify the field names and types match the mapping plan before the migration run. If Nutshell does not yet have user accounts for all Bidtracer owners, we flag the email mismatches so your team can invite or create Nutshell users before owner resolution runs.
Run a sample migration with field-level diff
A representative slice of 100–300 records — spanning People, Companies, Deals, and Activities — migrates first. We generate a field-level diff comparing Bidtracer source values against Nutshell destination values so you can verify stage mapping, owner resolution, custom field population, and attachment placement before the full run commits. You review the sample in Nutshell and flag any mapping adjustments. No records are permanently committed during the sample run — it operates against a staging target that is discarded after validation.
Execute full migration with delta-pickup window
The full migration runs against your live Nutshell instance. We sequence the load to respect foreign-key dependencies (People require a Company first; Deals require both a Person and Company). A delta-pickup window of 24–48 hours runs in parallel, capturing any Bidtracer records created or modified during the cutover. Every operation is logged in an audit trail. If reconciliation numbers do not match, one-click rollback reverts the Nutshell target to its pre-migration state so the team can diagnose and re-run.
Deliver non-migratable data export and rebuild reference
For Bidtracer modules that cannot migrate (Bid Management, Estimating, Project Management, Service Agreements), we deliver a structured CSV export of all linked People and Company data so contact records are preserved. We also export Bidtracer workflow definitions as a JSON reference document for your team to use when rebuilding automations or evaluating a dedicated construction management platform. Nutshell workflow setup is outside the migration scope — we provide the export and a guide to Nutshell's workflow configuration so your admin can rebuild the logic manually.
Platform deep dives
Bidtracer
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Moderate CRM migration. 4 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Moderate migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Bidtracer and Nutshell.
Object compatibility
4 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Bidtracer: Not publicly documented.
Data volume sensitivity
Bidtracer doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Bidtracer to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Bidtracer to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Bidtracer
Other ways to arrive at Nutshell
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.