CRM migration

Migrate from Bidtracer to Nutshell

Field-level mapping, validation, and rollback between Bidtracer and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.

Bidtracer logo

Bidtracer

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

12 of 12

objects map 1:1 between Bidtracer and Nutshell.

Complexity

CModerate

Timeline

24–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Bidtracer logo

Bidtracer

What's pushing teams away

  • Performance is a consistent complaint — basic tasks take 5–10 seconds, and users report that high-volume operations during peak bidding periods destroy productivity and motivation.
  • The product feels unfinished to some users, who describe it as being perpetually in beta with bugs and UI polish issues that never fully get resolved.
  • ActiveX and Internet Explorer dependencies for core features like file downloads create friction for users on modern browsers and operating systems, requiring IT workarounds.
  • Some users feel the all-in-one approach means Bidtracer does not excel at any single function compared to purpose-built tools for estimating, CRM, or project management.
  • Lack of a publicly documented REST API limits integration options and makes automated data export or migration support difficult to arrange.

Choosing

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How Bidtracer objects map to Nutshell

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)

maps to

Nutshell

People

1:1
Fully supported

Bidtracer 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

maps to

Nutshell

Companies

1:1
Mapping required

Bidtracer 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

maps to

Nutshell

Leads

1:1
Mapping required

Bidtracer 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

maps to

Nutshell

Deals

1:1
Fully supported

Bidtracer 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

maps to

Nutshell

Deals + Custom Fields

1:1
Fully supported

Bidtracer'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

maps to

Nutshell

No equivalent

1:1
Fully supported

Bidtracer'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

maps to

Nutshell

No equivalent

1:1
Fully supported

Bidtracer'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

maps to

Nutshell

No equivalent

1:1
Fully supported

Bidtracer'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

maps to

Nutshell

No equivalent

1:1
Fully supported

Bidtracer'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

maps to

Nutshell

Attachments

1:1
Not supported

Bidtracer 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)

maps to

Nutshell

Custom Fields

1:1
Fully supported

Bidtracer 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

maps to

Nutshell

Activities

1:1
Fully supported

Bidtracer'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.

Gotchas + challenges

What specifically takes care here

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 logo

Bidtracer gotchas

High

No public REST API for bulk export

Medium

ActiveX requirement blocks file downloads on modern browsers

Medium

Per-export convenience charge is not disclosed upfront

Low

Start-up and training fees on smaller tiers

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Pair-specific challenges

  • Construction-specific modules have no Nutshell equivalent and will not migrate

    Bidtracer's Bid Management, Invitation To Bid, BAC Estimating, Security Estimating, Engineering, Project Management (RFIs, submittals, CORs), Service Agreements, and Service Repair modules are construction-vertical features with no equivalent in Nutshell's generalist CRM model. The data in those modules — bid records, subcontractor lists, estimating line items, RFI logs, change orders, and service agreements — does not migrate. We export the People and Company data that lives inside those modules so contact records are not lost. An export of workflow definitions is provided for manual evaluation of whether those workflows can be rebuilt in a dedicated construction management tool or documented for process documentation purposes.

  • Nutshell's JSON-RPC API has rate limits that affect large-volume migration runs

    Nutshell's API operates with per-key rate limits on its JSON-RPC endpoint. For migrations exceeding 10,000 records, we batch API calls and implement exponential backoff to stay within Nutshell's stated limits. Nutshell also requires API impersonation permissions to attribute migrated activities to the correct user — the API key used for migration must have impersonation enabled, which is a setting configured in Nutshell's account under API key management. If impersonation is not available, all migrated activities log under the API key's name rather than the original record owner, which may affect audit trails.

  • File attachments exceeding Nutshell's storage limits must be flagged before migration

    Nutshell stores attachments directly on records and integrates with Google Drive for larger files. Bidtracer's file attachments (plans, specs, proposals, addenda) that are large or in unsupported formats may exceed Nutshell's upload limits. We profile file sizes during the discovery phase and flag any files over Nutshell's threshold before migration runs. Those files are exported as a compressed archive and re-uploaded to the linked Nutshell Google Drive account where available. This is a pre-migration validation step — the archive is delivered alongside the Nutshell migration so no attachments are lost even if they cannot be attached directly to records.

  • Bidtracer's Outlook email integration does not translate to Nutshell's email add-in

    Bidtracer logs emails through an Outlook integration that stores email metadata on Bidtracer records. Nutshell's email tracking uses its own Gmail and Outlook add-ins, which log emails to Nutshell Activities when the add-in is active. Migrated email logs transfer as Activity notes with the original timestamp and a reference to the original sender. However, the Nutshell email add-in must be installed and configured by each user post-migration for new emails to log automatically. We provide a configuration guide and install instructions as part of the post-migration handoff. Bidtracer's email integration does not carry forward — this is a re-implementation item.

  • Bidtracer custom properties require manual configuration in Nutshell before migration

    Bidtracer's custom properties (Division, License Number, Trade Specialty, Union Status, Safety Rating, Prevailing Wage Flag) are stored per-object in Bidtracer's schema. Nutshell requires custom fields to be created manually in the Nutshell UI under Settings > Custom Fields before data lands. We provide a custom field creation guide with field names, types, and pick-list values based on Bidtracer's property definitions. If custom fields are not created before the migration run, Bidtracer's custom property data is exported as a separate CSV and loaded as a one-time import after the fields are configured — this requires a second import pass and is flagged as an additional step in the migration plan.

Migration approach

Six steps for a successful Bidtracer to Nutshell data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

Context on both ends of the pair

Bidtracer logo

Bidtracer

Source

Strengths

  • Consolidates CRM, bid management, invitations, estimating, engineering, and project management into one platform for trade contractors.
  • All-included pricing with unlimited storage per user, mobile access, and free customizations on larger tiers.
  • Bid invitation tool lets subcontractors access plans and specs for free without requiring them to create an account.
  • Service agreements and service repair modules extend the platform beyond bidding into post-award job management.
  • Customer support rated highly by construction-industry reviewers who value staff understanding of their trade workflows.

Weaknesses

  • No publicly documented REST API for bulk export, making programmatic migration and third-party integrations difficult to arrange.
  • Performance issues reported across multiple reviews — task latency of 5–10 seconds per operation is a known friction point for high-volume users.
  • ActiveX component required for file downloads on certain pages, creating compatibility issues on modern browsers and Windows environments.
  • Customization options are described as limited, and larger tiers still charge start-up and training fees beyond the per-user subscription.
  • Some users report the product feels perpetually beta, with UI polish and reliability gaps that frustrate experienced users.
Nutshell logo

Nutshell

Destination

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Moderate CRM migration. 4 of 8 objects need a mapping; the rest are 1:1.

C

Overall complexity

Moderate migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Bidtracer and Nutshell.

  • Object compatibility

    C

    4 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Bidtracer: Not publicly documented.

  • Data volume sensitivity

    B

    Bidtracer doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Bidtracer to Nutshell migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Bidtracer to Nutshell data migrations

Answers to the questions buyers ask most during Bidtracer to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Bidtracer to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most Bidtracer to Nutshell migrations complete in 24–72 hours of clock time for datasets under 20,000 records. The fastest component is People and Companies — Deals take longer when stage-value mapping requires a custom table. Datasets exceeding 100,000 records or those with extensive custom property schemas extend to 5–10 days. The longest planning step is custom field setup in Nutshell, which is done manually by your admin before data lands — that prep work is not counted in migration clock time.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Bidtracer.
Land in Nutshell, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day