CRM migration

Migrate from LeadTrac to Nutshell

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

LeadTrac logo

LeadTrac

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

13 of 13

objects map 1:1 between LeadTrac and Nutshell.

Complexity

BStandard

Timeline

24–48 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

LeadTrac organizes sales data around leads and lead activities, with people and companies as secondary record types. Nutshell uses a four-object model: People (individual contacts), Companies (business accounts), Leads (prospects), and Deals (opportunities with stage-tracking). The core migration challenge is that LeadTrac does not appear in Nutshell's native import wizard (which supports HubSpot, Salesforce, Pipedrive, Close, and others), so FlitStack AI extracts LeadTrac data via its API, transforms the schema, and pushes records into Nutshell's JSON-RPC API. We map LeadTrac leads directly to Nutshell Leads, LeadTrac people to Nutshell People, and LeadTrac companies to Nutshell Companies, with Deal records created from any deal-like activity in LeadTrac. LeadTrac's custom fields become Nutshell custom fields on the matching object. Activity history (calls, emails, notes) migrates as Nutshell Activities linked to the parent record. Workflows, automations, and document-management logic in LeadTrac do not migrate and must be rebuilt in Nutshell manually or with the help of Nutshell's workflow builder. FlitStack runs a sample migration first with field-level diff, then executes the full migration with a 24-48 hour delta pickup window to capture any records modified during cutover.

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

LeadTrac logo

LeadTrac

What's pushing teams away

  • Only 4 verified reviews on G2 with an average of 3.6 stars — the platform has a very small customer base, making peer validation and independent benchmarking difficult.
  • LeadTrac has no publicly documented API, meaning there is no programmatic export path; data extraction requires manual CSV pulls or vendor-assisted exports with no guarantee of completeness.
  • Users report lack of customization at the user level — configuration changes require administrative access or vendor involvement, limiting how fast a team can adapt the system to new workflows.
  • G2 alternatives lists name Clio Manage, Smokeball, and MyCase as top competitors — firms migrating typically cite wanting broader ecosystem integrations and stronger mobile access than LeadTrac offers.
  • No free trial and inconsistent published pricing across Capterra ($20/user/month) versus SoftwareAdvice ($39.95/month) creates hesitation during vendor evaluation.

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 LeadTrac objects map to Nutshell

Each row shows how a LeadTrac 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.

LeadTrac

LeadTrac Lead

maps to

Nutshell

Nutshell Lead

1:1
Fully supported

LeadTrac leads map 1:1 to Nutshell Leads. Nutshell Lead records include status, source, owner, and custom fields. We preserve the original lead create date as Created Date and map LeadTrac owner email to Nutshell user lookup. Any custom fields on the LeadTrac lead become Nutshell custom fields on the corresponding Nutshell Lead record.

LeadTrac

LeadTrac Person

maps to

Nutshell

Nutshell Person

1:1
Fully supported

LeadTrac people (contacts) map to Nutshell People. Name, email, phone, address, title, and custom properties transfer directly. Nutshell People can be linked to a primary Nutshell Company via the Company lookup field. If a LeadTrac person has multiple company associations, the primary company link transfers first.

LeadTrac

LeadTrac Company

maps to

Nutshell

Nutshell Company

1:1
Fully supported

LeadTrac company records map to Nutshell Companies. Company name, domain, address, industry, and employee count fields transfer directly. Parent-company hierarchies in LeadTrac map to Nutshell's parent Company lookup if configured, preserving organizational structures within the migrated dataset.

LeadTrac

LeadTrac Lead-Person Link

maps to

Nutshell

Nutshell Lead (person_id)

1:1
Fully supported

LeadTrac associates people with leads via a linking table. In Nutshell, leads can have an associated Person record. We attach the mapped Nutshell Person to the Nutshell Lead to preserve the original relationship, using the most recently modified person or a specified primary person rule.

LeadTrac

LeadTrac Activity (Call)

maps to

Nutshell

Nutshell Activity

1:1
Fully supported

LeadTrac call logs migrate as Nutshell Activities with type='Call'. Original call date, duration note, outcome, and owner transfer. The activity is linked to the parent Nutshell record (Lead, Person, or Deal) to maintain the full interaction history in context.

LeadTrac

LeadTrac Activity (Email)

maps to

Nutshell

Nutshell Activity

1:1
Fully supported

LeadTrac email activity migrates as Nutshell Activities with type='Email'. Subject, body text, timestamp, and owner transfer. Links to the parent Nutshell record (Lead, Person, or Deal) are preserved so each email appears in the correct record timeline after migration.

LeadTrac

LeadTrac Activity (Note)

maps to

Nutshell

Nutshell Note

1:1
Fully supported

LeadTrac notes migrate as Nutshell Notes on the parent record. Note content, create date, and author transfer. Nutshell Notes display inline on the record timeline alongside activities, preserving the full narrative history of each Lead, Person, or Company.

LeadTrac

LeadTrac Activity (Meeting/Appointment)

maps to

Nutshell

Nutshell Activity

1:1
Fully supported

LeadTrac meeting or appointment records become Nutshell Activities with type='Meeting'. Start/end time, location, title, and attendee notes transfer. The activity links to the parent Nutshell record (Lead, Person, Company, or Deal) to keep appointments visible in context.

LeadTrac

LeadTrac Lead Status

maps to

Nutshell

Nutshell Lead Status

1:1
Fully supported

LeadTrac lead status values (New, Contacted, Qualified, Lost, etc.) map to Nutshell's lead status pick-list. Any custom LeadTrac statuses that have no direct Nutshell equivalent become custom status options created in Nutshell before migration begins, ensuring no status values are lost.

LeadTrac

LeadTrac Lead Source

maps to

Nutshell

Nutshell Lead Source

1:1
Fully supported

LeadTrac lead source attribution (Web Form, Referral, Trade Show, etc.) maps to Nutshell's Source pick-list. Custom source values in LeadTrac require custom source options to be created in Nutshell first, so your source attribution data transfers completely without manual re-entry.

LeadTrac

LeadTrac Custom Fields (Lead)

maps to

Nutshell

Nutshell Custom Fields (Lead)

1:1
Fully supported

LeadTrac custom fields on leads — such as internal case numbers, settlement amounts, or product interest — require corresponding Nutshell custom fields to be created on the Lead object before migration. We create these via Nutshell's API or guide your admin through manual setup using the Nutshell Settings UI.

LeadTrac

LeadTrac Custom Fields (Person)

maps to

Nutshell

Nutshell Custom Fields (Person)

1:1
Fully supported

LeadTrac custom fields on people — e.g., preferred contact method, birthday, spouse name — migrate as Nutshell Person custom fields. Field type mapping (text, date, number, pick-list) is preserved from LeadTrac's field definition, maintaining data integrity across all contact custom properties.

LeadTrac

LeadTrac Document/Reference

maps to

Nutshell

Nutshell Attachment (external)

1:1
Fully supported

LeadTrac's document management and reference attachments, including signed agreements via DocuSign integration, have no direct Nutshell equivalent. We export file URLs, file names, and DocuSign envelope IDs as a custom reference field on the Nutshell record for manual retrieval by your team after cutover.

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.

LeadTrac logo

LeadTrac gotchas

High

No public API means all data extraction is manual or vendor-dependent

Medium

Document and FlexNote export requires separate vendor access

Medium

Small review base and minimal independent benchmarks

Low

Custom Properties schema not externally documented

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

  • LeadTrac does not appear in Nutshell's native import wizard

    Nutshell's built-in import wizard at Settings > Data > Import supports 25+ CRMs including HubSpot, Salesforce, Pipedrive, Close, and Zoho — but LeadTrac is not among them. This means LeadTrac data cannot be pulled via Nutshell's one-click importer. FlitStack AI extracts LeadTrac data via its API, transforms the schema, and pushes records through Nutshell's JSON-RPC API instead. Your team does not need to manually export CSV files; we handle the full technical extraction and import pipeline.

  • LeadTrac's lead-person-company relationships require careful re-linkage in Nutshell

    LeadTrac supports N:N associations between people and companies, and between people and leads. Nutshell's model is different: People have one primary Company, and Leads can have one associated Person. When a LeadTrac lead has multiple linked people, FlitStack maps the primary person (most recently modified or by your specified rule) to the Nutshell Lead's person_id field. Secondary associations are preserved in a custom multi-value reference field on the Nutshell Lead for manual reconciliation.

  • LeadTrac document references and DocuSign links have no Nutshell equivalent

    LeadTrac includes document management with DocuSign integration for e-signatures — critical for debt settlement, legal, and enrollment workflows. Nutshell does not have native document storage or e-signature capability. FlitStack exports document reference URLs, file names, and DocuSign envelope IDs from LeadTrac as custom fields on the corresponding Nutshell record. Your team must re-establish document workflows using external tools such as standalone DocuSign, Google Drive, or Dropbox after migration is complete.

  • Custom fields in LeadTrac require pre-creation in Nutshell

    Nutshell custom fields must be created manually in the Nutshell UI (Settings > Data > Custom Fields) or via API before migration begins. LeadTrac custom fields (e.g., settlement amount, case number, referral source detail) do not auto-provision in Nutshell. FlitStack delivers a custom field creation checklist based on your LeadTrac field inventory, so your Nutshell admin can create the matching fields before the migration run commits any records to the target system.

  • LeadTrac workflows and automations do not migrate to Nutshell

    Any automated rules, assignment logic, reminder triggers, or communication sequences configured in LeadTrac are platform-specific and cannot be exported. Nutshell's automation model (automated sequences, task triggers, stage-change actions) must be rebuilt manually using Nutshell's workflow builder or Nutshell's API-based automation tools. FlitStack provides a structured export of your LeadTrac workflow definitions to serve as a rebuild reference document.

Migration approach

Six steps for a successful LeadTrac to Nutshell data migration

  1. Audit LeadTrac data model and export via API

    FlitStack connects to your LeadTrac instance via API using scoped read credentials. We extract all leads, people, companies, activities, and custom field definitions. We inventory the record counts per object, identify any non-standard field types, and flag any lead-person or person-company links that will need re-linkage in Nutshell. This audit produces a migration scope document and custom field creation checklist.

  2. Create Nutshell custom fields and configure schema

    Based on the LeadTrac audit, your Nutshell admin (or FlitStack, acting as your admin) creates the custom fields needed in Nutshell. This includes custom fields on Leads, People, and Companies. Nutshell's Settings > Data > Custom Fields UI is used, or we create fields via Nutshell's JSON-RPC API. We deliver a field-creation checklist so nothing is missed before the migration run.

  3. Resolve owner and user mappings by email

    LeadTrac owner email addresses are matched against Nutshell user accounts. Nutshell users are identified by their email in the Nutshell user table. Any LeadTrac owner without a matching Nutshell user is flagged before migration — your team either invites the user to Nutshell first or assigns their records to a designated fallback Nutshell user. No record lands without a valid Nutshell owner.

  4. Run sample migration with field-level diff

    A representative slice of 100–500 records migrates first — spanning leads, people, companies, and activities. We generate a field-level diff report showing the before (LeadTrac) and after (Nutshell) values for every mapped field. You verify that lead status, source attribution, owner assignment, activity dates, and custom field values all transferred correctly. No full run commits until you approve the sample.

  5. Execute full migration with delta pickup window

    The full LeadTrac dataset migrates into Nutshell via the JSON-RPC API. A delta-pickup window of 24–48 hours runs after the initial load, capturing any records created or modified in LeadTrac during the cutover period. FlitStack generates an audit log of every record written, and one-click rollback is available if reconciliation identifies unexpected gaps.

Platform deep dives

Context on both ends of the pair

LeadTrac logo

LeadTrac

Source

Strengths

  • Integrated Docusign workflow for electronic agreement sending, signing, and automatic import of completed documents into the record.
  • Unified platform covering lead intake, client management, debt and creditor tracking, settlement negotiation, and client communication in one subscription.
  • Web-based access means no on-premise installation; staff can access from any browser without dedicated client software.
  • Built-in client portal reduces inbound support calls by giving customers self-service access to case status and documents.
  • Per-user pricing model is predictable and accessible for small to mid-size law firms and debt settlement practices.

Weaknesses

  • No publicly documented API means programmatic data export is not available; all extraction requires vendor-assisted processes or manual CSV pulls.
  • Only 4 verified reviews on G2 with a 3.6-star average — a very small review base makes independent assessment of product reliability difficult.
  • Lack of customization at the user level reported by customers; administrative access or vendor involvement is required to change workflows or field configurations.
  • Inconsistent published pricing across different software directories (Capterra vs. SoftwareAdvice) suggests opaque or negotiated pricing with no public standard tier breakdown.
  • Limited information about mobile application availability; teams requiring native iOS or Android access may find LeadTrac unsuitable.
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?

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

B

Overall complexity

Standard migration

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

  • Object compatibility

    B

    1 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

    LeadTrac: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

Estimate your LeadTrac 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 LeadTrac to Nutshell data migrations

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

Can't find your answer?

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

Book a free 30 minute consultation

Most LeadTrac-to-Nutshell migrations complete in 24–48 hours of clock time for datasets under 25,000 records. Larger setups exceeding 100,000 records or those with extensive custom field counts and multi-object relationship chains extend to 5–7 days. The custom field creation step in Nutshell (Step 2 of our approach) is the longest planning-dependent phase and can run in parallel with other prep work.

Adjacent paths

Related migrations to explore

Ready when you are

Move from LeadTrac.
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