CRM migration

Migrate from InfoTrack to Nutshell

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

InfoTrack logo

InfoTrack

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

10 of 10

objects map 1:1 between InfoTrack and Nutshell.

Complexity

CModerate

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

InfoTrack logo

InfoTrack

What's pushing teams away

  • Court-stamped documents and expenses stop syncing back to the Matter when the eFiling service connection drops or the integration with the case management system expires, requiring manual re-authentication to resolve.
  • Credit card processing fees apply to every transaction, and ACH carries a state-variable flat fee that accumulates into a visible line item on invoices for high-volume litigation firms.
  • No public API means there is no programmatic way to extract bulk data from InfoTrack—all data retrieval requires manual CSV export from the admin UI, which limits what can be migrated to a new platform without vendor coordination.
  • Integration keys can be lost if the account admin closes the browser during onboarding, requiring a support request to regenerate the unique firm integration key for re-establishing the case management connection.

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

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

maps to

Nutshell

Nutshell Company

1:1
Fully supported

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

maps to

Nutshell

Nutshell Person

1:1
Fully supported

InfoTrack 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

maps to

Nutshell

Nutshell Deal

1:1
Fully supported

Each 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

maps to

Nutshell

Nutshell Pipeline Stage

1:1
Fully supported

InfoTrack 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

maps to

Nutshell

Nutshell Note

1:1
Fully supported

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

maps to

Nutshell

Nutshell Custom Field

1:1
Fully supported

InfoTrack 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

maps to

Nutshell

Nutshell Note

1:1
Fully supported

InfoTrack 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

maps to

Nutshell

Nutshell File Attachment + Note

1:1
Fully supported

InfoTrack 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

maps to

Nutshell

Nutshell User

1:1
Fully supported

InfoTrack 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

maps to

Nutshell

Nutshell Note on Deal

1:1
Fully supported

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

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.

InfoTrack logo

InfoTrack gotchas

High

InfoTrack is a workflow layer with no standalone CRM data model

Medium

Custom folder sync for documents requires Time Matters 16.6+

High

No public API means bulk export requires manual CSV downloads

Medium

Integration keys must be regenerated when reconnecting to a new case management system

Medium

Per-order invoice granularity complicates matter-level billing reconstruction

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

  • InfoTrack exposes no standalone contact API — contacts live inside order records

    InfoTrack does not maintain a top-level contact database accessible via API. Contacts are embedded as objects within order JSON (attorney name, client contact) with no persistent contact ID. We must extract unique email/name combinations across all order records, deduplicate by email, and create Nutshell People from the resulting set. This means contact creation order depends on order volume, and the initial People import must complete before Deals can link to them via PersonId. Firms with high order counts relative to unique contacts should expect the disambiguation phase to extend planning by 1–2 days.

  • Nutshell contact-tier billing means migrated contacts count toward plan limits

    Nutshell pricing tiers are scoped by contact volume (100 contacts at $13/user/month up to 500,000 at higher tiers). Every InfoTrack contact extracted from order records becomes a Nutshell Person and counts toward this limit. Firms with large client databases should verify their target Nutshell plan accommodates the migrated contact count before migration — overage billing applies if the plan cap is exceeded. We provide a pre-migration contact count estimate so the firm can select the correct Nutshell tier upfront.

  • InfoTrack integration connections cannot migrate — practice management links must be rebuilt

    InfoTrack integrations with Time Matters, Clio, LEAP, and other practice management systems are connection-level configurations stored on InfoTrack's platform side. These cannot be extracted and replayed in Nutshell because the authentication tokens, webhook endpoints, and sync rules are specific to InfoTrack's architecture. The integration logs are preserved as Notes on the relevant Company records for audit purposes, but the firm must configure new integrations in Nutshell separately. Nutshell's integration marketplace with Slack, Gmail, Zapier, and other tools serves as the rebuild target for workflow automation after migration is complete.

  • Order-to-Deal disambiguation requires a Nutshell pipeline configured before migration

    InfoTrack order statuses (Pending, In Progress, Completed, Failed) must map to Nutshell pipeline stages. If the firm has multiple practice-area workflows, each may need its own Nutshell pipeline with distinct stage sets. We cannot write Deals until at least one pipeline and its stages exist in Nutshell. We deliver a pipeline definition plan as part of the migration package so the firm's Nutshell admin creates the schema before data lands — this is the longest pre-migration planning step for legal-to-CRM migrations.

Migration approach

Six steps for a successful InfoTrack to Nutshell data migration

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

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

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

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

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

Context on both ends of the pair

InfoTrack logo

InfoTrack

Source

Strengths

  • Covers US federal, bankruptcy, and state court eFiling in a single platform with real-time docket syncing.
  • Bidirectional sync with integrated case management systems means court-returned documents and expenses land directly in the Matter without manual steps.
  • Pay-per-use model with no subscription, no per-seat licensing, and no setup fees for firms with variable litigation volume.
  • Integrated process serving network with up to five attempts per order and automated status updates.
  • Pre-population of court forms from Matter data reduces data entry errors and accelerates filing turnaround.

Weaknesses

  • InfoTrack is not a standalone practice management system—it requires an integrated case management system to manage contacts, matters, and client billing.
  • No documented public API for bulk data retrieval; all exports require manual CSV download from the admin panel.
  • Limited to US federal and state court workflows; not applicable for international, immigration, or transactional law practices.
  • Credit card processing fees and state-variable ACH fees add cost complexity for high-volume litigation firms.
  • Integration key loss during onboarding requires a support ticket to resolve, creating friction when reconfiguring integrations.
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. 1 of 8 objects need a manual workaround.

C

Overall complexity

Moderate migration

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

  • Object compatibility

    C

    1 of 8 objects need a manual workaround.

  • 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

    InfoTrack: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Most InfoTrack-to-Nutshell migrations complete in 48–72 hours for setups with fewer than 10,000 order records. Larger firms with 50,000+ orders or multiple practice-area pipelines requiring separate stage configurations extend to 5–7 days. The longest single step is designing the Nutshell pipeline schema and resolving attorney-to-user email matches before data load begins — we front-load this in the planning phase to avoid delays during the actual migration window.

Adjacent paths

Related migrations to explore

Ready when you are

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