CRM migration
Field-level mapping, validation, and rollback between InfoTrack and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
InfoTrack
Source
Nutshell
Destination
Compatibility
10 of 10
objects map 1:1 between InfoTrack and Nutshell.
Complexity
CModerate
Timeline
48–72 hours
Overview
InfoTrack is a legal technology platform built around service orders — eFiling requests, process serving tasks, document management, and matter-level tracking integrated with law practice management systems. It does not expose a conventional CRM data model (contacts, companies, deals) through its API. Nutshell is a sales-focused CRM with People, Companies, Leads, and Deals as its core objects. The migration therefore requires reconstructing a client relationship model from InfoTrack data: contacts extracted from order records and matter associations become Nutshell People; the legal organizations or firms they belong to become Nutshell Companies; and historical service orders with monetary values map to Nutshell Deals so the sales pipeline reflects prior engagement history. We map InfoTrack custom fields on orders and contacts to Nutshell custom fields on the corresponding objects. InfoTrack's billing and payment records, integration logs, and document metadata are preserved as Notes attached to the migrated People and Company records. Workflows, automations, and integration connections in InfoTrack are legal-practice-specific and do not translate to Nutshell's sales automation model — we document them for manual rebuild. We extract data via InfoTrack's export APIs and load into Nutshell using its JSON-RPC API with bulk operations where record volumes allow.
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 InfoTrack 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.
InfoTrack
InfoTrack Matter
Nutshell
Nutshell Company
1:1InfoTrack Matters represent legal cases or file matters tied to a client organization. They map directly to Nutshell Companies — the firm name becomes the Company Name, and matter-specific details (practice area, jurisdiction) become custom fields on the Company record.
InfoTrack
InfoTrack Contact (extracted from order)
Nutshell
Nutshell Person
1:1InfoTrack does not expose a standalone contact API; contacts are embedded in order records (ordering attorney, client contact). We extract unique email and name combinations across all orders and create Nutshell People, deduplicating by email address. The Person is linked to the Company representing their matter.
InfoTrack
InfoTrack Order
Nutshell
Nutshell Deal
1:1Each InfoTrack service order (eFiling, process serving) becomes a Nutshell Deal. The order type becomes the Deal name prefix; the order fee amount becomes the Deal amount. Order status (Pending, In Progress, Complete) maps to Nutshell pipeline stages defined per workflow.
InfoTrack
InfoTrack Order Status
Nutshell
Nutshell Pipeline Stage
1:1InfoTrack order statuses map value-by-value to Nutshell pipeline stages. 'Pending' maps to 'Qualifying', 'In Progress' maps to 'Presentation Scheduled', 'Completed' maps to 'Closed Won', and 'Failed' maps to 'Closed Lost'. Stage probabilities are applied from Nutshell's default probability weights for each mapped stage.
InfoTrack
InfoTrack Invoice
Nutshell
Nutshell Note
1:1InfoTrack invoice records (exported as CSV) are parsed and attached as Notes to the corresponding Nutshell Person or Deal. The Note body includes invoice number, date, amount, and line items. Original invoice files are re-uploaded as Nutshell File Attachments if present in the export.
InfoTrack
InfoTrack Custom Field (on Order)
Nutshell
Nutshell Custom Field
1:1InfoTrack custom fields attached to orders (e.g., Court Code, Service Address, Case Reference) require corresponding custom fields in Nutshell. We create Nutshell custom fields on the Deal object matching the source field type (text, picklist, date) before the migration runs. Field labels are preserved for traceability.
InfoTrack
InfoTrack Integration Log
Nutshell
Nutshell Note
1:1InfoTrack integration connection records including Practice Management system links and API key references are preserved as Notes on the Nutshell Company record for audit trail purposes. These are reference data only and document what integrations existed in the source system — all integrations must be rebuilt in Nutshell separately using the integrations available in Nutshell's marketplace.
InfoTrack
InfoTrack Document Metadata
Nutshell
Nutshell File Attachment + Note
1:1InfoTrack document records include filename, filing date, court, and status. The metadata becomes a Note attached to the corresponding Deal; the actual document file is re-uploaded as a Nutshell File Attachment on the same Deal if the export includes binary files.
InfoTrack
InfoTrack User / Attorney
Nutshell
Nutshell User
1:1InfoTrack user accounts linked to orders are matched to Nutshell users by email address for owner assignment on migrated records. Unmatched attorneys are flagged before migration begins — the firm either creates Nutshell user accounts first or assigns those records to a designated fallback owner during the migration run.
InfoTrack
InfoTrack Payment Record
Nutshell
Nutshell Note on Deal
1:1Payment records attached to InfoTrack orders including ACH confirmation numbers and card transaction IDs are preserved as Notes on the corresponding Nutshell Deal record. Nutshell does not have a native payment or billing object — this Note-based approach preserves the complete billing audit trail for finance team reconciliation after migration.
| InfoTrack | Nutshell | Compatibility | |
|---|---|---|---|
| InfoTrack Matter | Nutshell Company1:1 | Fully supported | |
| InfoTrack Contact (extracted from order) | Nutshell Person1:1 | Fully supported | |
| InfoTrack Order | Nutshell Deal1:1 | Fully supported | |
| InfoTrack Order Status | Nutshell Pipeline Stage1:1 | Fully supported | |
| InfoTrack Invoice | Nutshell Note1:1 | Fully supported | |
| InfoTrack Custom Field (on Order) | Nutshell Custom Field1:1 | Fully supported | |
| InfoTrack Integration Log | Nutshell Note1:1 | Fully supported | |
| InfoTrack Document Metadata | Nutshell File Attachment + Note1:1 | Fully supported | |
| InfoTrack User / Attorney | Nutshell User1:1 | Fully supported | |
| InfoTrack Payment Record | Nutshell Note on Deal1: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.
InfoTrack gotchas
InfoTrack is a workflow layer with no standalone CRM data model
Custom folder sync for documents requires Time Matters 16.6+
No public API means bulk export requires manual CSV downloads
Integration keys must be regenerated when reconnecting to a new case management system
Per-order invoice granularity complicates matter-level billing reconstruction
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
Extract and inventory InfoTrack data via available export endpoints
We connect to InfoTrack using the firm's integration credentials and enumerate all accessible record types: orders by service type, matter records, invoice CSV exports, and document metadata. We produce a data inventory report listing record counts per type, custom field definitions observed in order payloads, and unique contact email addresses extracted across all orders. This report drives the scope and pricing confirmation before migration begins.
Design Nutshell schema: pipelines, stages, and custom fields
Based on the InfoTrack data inventory, we design the Nutshell target schema: one or more pipelines matching practice-area workflows, stage definitions with probability weights, and custom fields on Company, Person, and Deal objects to receive InfoTrack-specific data. We deliver a schema setup plan document so the firm's Nutshell admin creates fields and pipelines before data load. We also resolve attorney email addresses against Nutshell users to flag any owners who need accounts created first.
Run sample migration and generate field-level diff
A representative sample migrates first — typically 100–300 orders spanning multiple service types, practice areas, and attorneys to capture edge cases. We generate a detailed field-level diff comparing source records against migrated Nutshell records so the firm can verify Deal amount accuracy, stage mapping correctness, Person-Company linkage, and custom field population before the full migration run commits. Any field mapping issues or data transformation errors identified are corrected before proceeding.
Execute full migration with delta-pickup window
The full migration loads InfoTrack orders as Nutshell Deals, extracts and deduplicates contacts into Nutshell People, creates or updates Company records for each Matter, and attaches invoice, payment, and document metadata as Notes. A delta-pickup window of 24–48 hours after cutover captures any new orders placed in InfoTrack during the migration run. Audit logging tracks every record written; one-click rollback is available if reconciliation identifies missing or mis-mapped records.
Deliver reconciliation report and rebuild reference documentation
Post-migration, we deliver a reconciliation report comparing InfoTrack record counts against Nutshell record counts by type, flagging any records that could not be migrated due to missing required fields or API errors. We also provide a rebuild reference document listing every InfoTrack workflow and automation type observed, so the firm's Nutshell admin can reconstruct practice-specific automations using Nutshell's rules engine and Zapier integrations.
Platform deep dives
InfoTrack
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Moderate CRM migration. 1 of 8 objects need a manual workaround.
Overall complexity
Moderate migration
Derived from compatibility, mapping clarity, API constraints, and data volume across InfoTrack and Nutshell.
Object compatibility
1 of 8 objects need a manual workaround.
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
InfoTrack: Not publicly documented.
Data volume sensitivity
InfoTrack 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 InfoTrack to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your InfoTrack 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 InfoTrack
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.