CRM migration
Field-level mapping, validation, and rollback between LeadTrac and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
LeadTrac
Source
Nutshell
Destination
Compatibility
13 of 13
objects map 1:1 between LeadTrac and Nutshell.
Complexity
BStandard
Timeline
24–48 hours
Overview
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.
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 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
Nutshell
Nutshell Lead
1:1LeadTrac 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
Nutshell
Nutshell Person
1:1LeadTrac 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
Nutshell
Nutshell Company
1:1LeadTrac 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
Nutshell
Nutshell Lead (person_id)
1:1LeadTrac 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)
Nutshell
Nutshell Activity
1:1LeadTrac 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)
Nutshell
Nutshell Activity
1:1LeadTrac 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)
Nutshell
Nutshell Note
1:1LeadTrac 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)
Nutshell
Nutshell Activity
1:1LeadTrac 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
Nutshell
Nutshell Lead Status
1:1LeadTrac 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
Nutshell
Nutshell Lead Source
1:1LeadTrac 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)
Nutshell
Nutshell Custom Fields (Lead)
1:1LeadTrac 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)
Nutshell
Nutshell Custom Fields (Person)
1:1LeadTrac 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
Nutshell
Nutshell Attachment (external)
1:1LeadTrac'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.
| LeadTrac | Nutshell | Compatibility | |
|---|---|---|---|
| LeadTrac Lead | Nutshell Lead1:1 | Fully supported | |
| LeadTrac Person | Nutshell Person1:1 | Fully supported | |
| LeadTrac Company | Nutshell Company1:1 | Fully supported | |
| LeadTrac Lead-Person Link | Nutshell Lead (person_id)1:1 | Fully supported | |
| LeadTrac Activity (Call) | Nutshell Activity1:1 | Fully supported | |
| LeadTrac Activity (Email) | Nutshell Activity1:1 | Fully supported | |
| LeadTrac Activity (Note) | Nutshell Note1:1 | Fully supported | |
| LeadTrac Activity (Meeting/Appointment) | Nutshell Activity1:1 | Fully supported | |
| LeadTrac Lead Status | Nutshell Lead Status1:1 | Fully supported | |
| LeadTrac Lead Source | Nutshell Lead Source1:1 | Fully supported | |
| LeadTrac Custom Fields (Lead) | Nutshell Custom Fields (Lead)1:1 | Fully supported | |
| LeadTrac Custom Fields (Person) | Nutshell Custom Fields (Person)1:1 | Fully supported | |
| LeadTrac Document/Reference | Nutshell Attachment (external)1: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.
LeadTrac gotchas
No public API means all data extraction is manual or vendor-dependent
Document and FlexNote export requires separate vendor access
Small review base and minimal independent benchmarks
Custom Properties schema not externally documented
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
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.
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.
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.
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.
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
LeadTrac
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across LeadTrac and Nutshell.
Object compatibility
1 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
LeadTrac: Not publicly documented.
Data volume sensitivity
LeadTrac 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 LeadTrac to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your LeadTrac 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 LeadTrac
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.