CRM migration

Migrate from FactBox to Nutshell

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

FactBox logo

FactBox

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

12 of 12

objects map 1:1 between FactBox and Nutshell.

Complexity

BStandard

Timeline

3–5 days

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

FactBox is a legal practice management platform built around case matters, parties (plaintiff, defendant, witness), documents with versioning, billable hours, and a chronology timeline. Nutshell is a sales CRM built around People (contacts), Companies (accounts), Leads, Deals (pipeline stages), and Activities (tasks, calls, emails). The two data models are fundamentally misaligned — FactBox stores legal-domain objects that have no native Nutshell equivalent — so the migration requires creating a custom Cases object in Nutshell, establishing party-to-contact mappings, and making deliberate choices about document versioning and billable-hour representation. FlitStack AI extracts all FactBox records via your API using HTTP Basic auth over HTTPS, then maps People to Nutshell People, Companies to Nutshell Companies, and case matters to a custom Cases object linked by the primary contact. Document attachments are consolidated to their most-recent version and re-uploaded as Nutshell Files. Billable hours become Activities with custom time-tracking fields. Automation rules, litigation-specific workflows, and document version history do not migrate — FlitStack exports your FactBox rule definitions for manual rebuild in Nutshell's automation tools. The migration uses Nutshell's JSON-RPC API with standard pagination to handle large exports within rate limits.

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

FactBox logo

FactBox

What's pushing teams away

  • Limited public API documentation makes integration with other legal tech tools difficult and custom automation nearly impossible.
  • The platform appears geared toward smaller cases and solo practitioners; larger litigation teams may find collaboration features insufficient.
  • Reviews note the tool works well for organizing facts but lacks broader practice management capabilities some firms need.
  • Some users may outgrow the platform as case volume and complexity increase beyond what FactBox was designed to handle.

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

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

FactBox

FactBox People

maps to

Nutshell

Nutshell Person

1:1
Fully supported

FactBox parties (attorneys, clients, witnesses, opposing counsel) map directly to Nutshell People. Name, email, phone, address, title, and role fields transfer as-is. Custom fields for bar_number and specialty are created as Nutshell custom fields on Person. The direct mapping preserves all standard contact information without transformation.

FactBox

FactBox Company (law firm or client organization)

maps to

Nutshell

Nutshell Company

1:1
Fully supported

FactBox organizations associated with parties map to Nutshell Companies. Company name, address, phone, and website transfer as direct field mappings. Industry type becomes a Nutshell custom field since Nutshell's industry pick-list is sales-oriented and may not reflect legal-sector classifications accurately.

FactBox

FactBox Case / Matter

maps to

Nutshell

Nutshell Custom Object: Cases

1:1
Fully supported

FactBox case matters have no native Nutshell equivalent — they become a custom Cases object created in Nutshell. The Cases object links to the primary Person (client) and Company (law firm or defendant organization) via lookup fields. Case number, case type, case status, and court information become custom fields on the Cases object.

FactBox

FactBox Case Party Role

maps to

Nutshell

Nutshell Person custom field: Party_Role__c

1:1
Fully supported

FactBox stores party roles per case (Lead Attorney, Client, Expert Witness, Opposing Counsel). Nutshell People have no native role-per-case concept. We create a Party_Role__c custom field on Person and populate it from the case-party association. Multiple roles across cases require the role value to be stored per case-person link.

FactBox

FactBox Document

maps to

Nutshell

Nutshell File (attached to Person, Company, or Cases)

1:1
Fully supported

FactBox documents with version history are consolidated — the most-recent version is extracted and re-uploaded as a Nutshell File attached to the relevant Person, Company, or custom Cases record. Version history metadata is preserved as a custom text field on the file attachment record. Earlier versions are optionally attached as additional file records if your plan includes multi-file support.

FactBox

FactBox Billable Hours

maps to

Nutshell

Nutshell Activity (Task) with custom fields

1:1
Fully supported

FactBox time entries including date, duration, rate, and billing_status become Nutshell Activities with custom fields Duration_Minutes__c, Billing_Rate__c, and Billing_Status__c. The activity Subject maps to the FactBox task description. Billable versus non-billable designation migrates to the Billing_Status__c custom field on each Activity record.

FactBox

FactBox Chronology Event

maps to

Nutshell

Nutshell Activity (Task) linked to custom Cases

1:1
Fully supported

FactBox chronology entries (event date, description, source document) become Nutshell Activities with the event date stored in the custom Event_Date__c field and the description in the Activity Subject. Each chronology entry links to the related Cases object so the case timeline is reconstructable from the Activity list.

FactBox

FactBox Task (case-specific)

maps to

Nutshell

Nutshell Activity (Task)

1:1
Fully supported

Case-linked tasks in FactBox map to Nutshell Activities. Task name becomes the Activity Subject. Due date maps to the Activity Due Date field. Assignee resolves by email match to a Nutshell user. Completed status maps to the Activity Completed flag.

FactBox

FactBox Calendar Event (court dates, deadlines)

maps to

Nutshell

Nutshell Activity (Event)

1:1
Fully supported

FactBox court dates and deadlines become Nutshell Event activities. The event start time maps to the Nutshell Event start_datetime. Event subject becomes the Event title. Court location maps to the Event location field. Nutshell Events do not support all-day events natively — we store the all-day flag in a custom field.

FactBox

FactBox Note

maps to

Nutshell

Nutshell Note

1:1
Fully supported

Free-form notes in FactBox map directly to Nutshell Notes. Note body text transfers as-is without transformation. Notes originally attached to a specific case are linked to the corresponding custom Cases object. Rich-text formatting is preserved where the Note body supports it in Nutshell's implementation.

FactBox

FactBox Custom Field (any type)

maps to

Nutshell

Nutshell Custom Field

1:1
Fully supported

Any FactBox custom fields on People, Companies, or Cases are created as Nutshell custom fields before migration. Field type mapping follows standard transformations: date fields to Date, numeric fields to Number, pick-list values to Choice fields. Long-text custom fields map to Nutshell's long-text custom field type.

FactBox

FactBox Owner / Assignee

maps to

Nutshell

Nutshell User (matched by email)

1:1
Fully supported

FactBox user assignments resolve to Nutshell Users by email address match. Unmatched owners are flagged before migration — your team either creates the Nutshell user first or assigns their records to a fallback user. No record migrates without a resolved owner.

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.

FactBox logo

FactBox gotchas

Medium

Annual subscription does not auto-renew

High

Limited public API documentation

Medium

File attachment handling requires separate migration

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

  • FactBox case matters have no native Nutshell equivalent — custom Cases object required

    FactBox organizes all data around case matters: parties, documents, billable hours, and chronology entries are all case-scoped. Nutshell has no built-in case or matter object. FlitStack AI creates a custom Cases object in Nutshell with lookup relationships to Person and Company, and custom fields for case_number, case_type, case_status, filing_date, and court. The case-party role (Lead Attorney, Client, Witness) is stored as a custom Party_Role__c field on the Person record. This design enables you to view all matters tied to a client from the Person record, but it requires Nutshell Enterprise-tier access for custom object creation.

  • Nutshell API uses JSON-RPC over HTTPS with Basic auth — different from REST-based platforms

    Nutshell's API is JSON-RPC rather than REST. Authentication uses HTTP Basic with your Nutshell domain and an API token as the password, formatted as domain:api_token. Rate limits apply per API key and are tracked by Nutshell's infrastructure. Large FactBox exports (especially documents and attachment binary data) require chunked API calls with retry logic. We use Nutshell's bulk export endpoints where available and paginated JSON-RPC requests for record sets to stay within operational rate limits.

  • Document version history consolidates to single-file attachments in Nutshell

    FactBox tracks document versions — each version is a distinct record linked to specific case facts. Nutshell Files are single-version attachments with no native version history model. We extract the most-recent document version from FactBox for migration as a Nutshell File attachment on the relevant Person, Company, or Cases record. Version metadata (version number, date, author) is preserved as a custom Version_Metadata__c text field on the attachment record. Prior versions are optionally migrated as additional File records if your Nutshell plan supports multi-file attachment workflows.

  • Automation rules and case-stage workflows do not migrate to Nutshell

    FactBox workflows tied to case-stage transitions (e.g., automatically create a task when case status moves to Discovery, or send a notification when a court date is filed) have no equivalent in Nutshell's automation model. Nutshell Pro and Enterprise support stage-entry email sequences and task triggers, but these are scoped to deal pipeline stages, not legal case stages. FlitStack AI exports your FactBox workflow definitions as a structured reference document for your team to rebuild in Nutshell. Any automation that requires legal-domain logic (e.g., deadline calculations based on filing dates) requires manual configuration in Nutshell.

Migration approach

Six steps for a successful FactBox to Nutshell data migration

  1. Export all FactBox data via API

    FlitStack AI authenticates to FactBox using your API credentials and extracts all People, Companies, Cases, Documents, Billable Hours, Chronology entries, Activities, and custom field data. We use FactBox's export endpoints with pagination to handle large datasets. The full export produces a structured JSON dataset organized by object type, with relationship IDs preserved for later linking. We also export FactBox workflow and automation definitions as a JSON reference file for your team to use during the Nutshell rebuild phase.

  2. Design Nutshell custom schema for legal data

    Before any records move, we create the custom Cases object in Nutshell with all required custom fields (Case_Number__c, Case_Type__c, Case_Status__c, Filing_Date__c, Court__c, Party_Role__c on Person, Billing fields on Activities, Event_Date__c on Activity). We establish lookup relationships from Cases to Person and Company. We validate that your Nutshell plan supports custom objects and custom fields at the required count. The schema design document is delivered for your admin's review and approval before data migration begins.

  3. Map and migrate all object types in dependency order

    We migrate in the correct foreign-key sequence: Companies first (so Person.company_id resolves), then People (with owner email matching to Nutshell Users), then the custom Cases object linked to the primary Person and Company per case. Activities (tasks, calls, chronology events, billable hours) are migrated last, linked to the appropriate Person, Company, or Cases record. Document attachments are extracted from FactBox, consolidated to the most-recent version, and uploaded as Nutshell Files. All custom fields are populated during migration.

  4. Run sample migration with field-level diff

    A representative slice of records (typically 100–300 covering a mix of People, Companies, a case or two, activities, and a document or two) migrates first. We generate a field-level diff between the source FactBox record and the destination Nutshell record so you can verify that party role mapping, case linking, document attachment, and custom field population all look correct. You approve the sample before the full migration commits.

  5. Full cutover with delta-pickup window

    The full migration runs against Nutshell's API. A delta-pickup window (typically 24–48 hours) captures any records created or modified in FactBox during the cutover period so the final Nutshell state reflects FactBox's last working state at go-live. Our audit log records every migrated record with its source ID for traceability. One-click rollback is available if reconciliation identifies missing records or mapping errors.

Platform deep dives

Context on both ends of the pair

FactBox logo

FactBox

Source

Strengths

  • Fact-centric data model directly supports litigation workflow from document intake to trial preparation.
  • Automatic fact extraction from uploaded documents speeds up case organization significantly.
  • Physical data security with biometric readers, 2-factor access, and armed guards protects sensitive case data.
  • Immediate productivity—attorneys report being productive on day one without training or technical support.

Weaknesses

  • Minimal public API documentation limits integration options and custom automation capabilities.
  • Collaboration features may be insufficient for large litigation teams handling complex, multi-party cases.
  • The platform appears optimized for smaller matters; enterprise-scale case management features may be limited.
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. 2 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 FactBox and Nutshell.

  • Object compatibility

    B

    2 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

    FactBox: Not applicable — no public API endpoints are published..

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Most FactBox-to-Nutshell migrations complete in 3–5 business days of clock time for setups with fewer than 5,000 records and a single case type. Larger FactBox instances with over 20,000 records, multiple case types, or significant document attachment volumes extend to 2–3 weeks. The custom Cases object setup and Nutshell Enterprise-tier provisioning (if needed for custom objects) are the longest planning steps before migration begins.

Adjacent paths

Related migrations to explore

Ready when you are

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