CRM migration
Field-level mapping, validation, and rollback between FactBox and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
FactBox
Source
Nutshell
Destination
Compatibility
12 of 12
objects map 1:1 between FactBox and Nutshell.
Complexity
BStandard
Timeline
3–5 days
Overview
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.
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 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
Nutshell
Nutshell Person
1:1FactBox 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)
Nutshell
Nutshell Company
1:1FactBox 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
Nutshell
Nutshell Custom Object: Cases
1:1FactBox 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
Nutshell
Nutshell Person custom field: Party_Role__c
1:1FactBox 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
Nutshell
Nutshell File (attached to Person, Company, or Cases)
1:1FactBox 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
Nutshell
Nutshell Activity (Task) with custom fields
1:1FactBox 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
Nutshell
Nutshell Activity (Task) linked to custom Cases
1:1FactBox 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)
Nutshell
Nutshell Activity (Task)
1:1Case-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)
Nutshell
Nutshell Activity (Event)
1:1FactBox 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
Nutshell
Nutshell Note
1:1Free-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)
Nutshell
Nutshell Custom Field
1:1Any 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
Nutshell
Nutshell User (matched by email)
1:1FactBox 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.
| FactBox | Nutshell | Compatibility | |
|---|---|---|---|
| FactBox People | Nutshell Person1:1 | Fully supported | |
| FactBox Company (law firm or client organization) | Nutshell Company1:1 | Fully supported | |
| FactBox Case / Matter | Nutshell Custom Object: Cases1:1 | Fully supported | |
| FactBox Case Party Role | Nutshell Person custom field: Party_Role__c1:1 | Fully supported | |
| FactBox Document | Nutshell File (attached to Person, Company, or Cases)1:1 | Fully supported | |
| FactBox Billable Hours | Nutshell Activity (Task) with custom fields1:1 | Fully supported | |
| FactBox Chronology Event | Nutshell Activity (Task) linked to custom Cases1:1 | Fully supported | |
| FactBox Task (case-specific) | Nutshell Activity (Task)1:1 | Fully supported | |
| FactBox Calendar Event (court dates, deadlines) | Nutshell Activity (Event)1:1 | Fully supported | |
| FactBox Note | Nutshell Note1:1 | Fully supported | |
| FactBox Custom Field (any type) | Nutshell Custom Field1:1 | Fully supported | |
| FactBox Owner / Assignee | Nutshell User (matched by email)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.
FactBox gotchas
Annual subscription does not auto-renew
Limited public API documentation
File attachment handling requires separate migration
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
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.
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.
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.
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.
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
FactBox
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 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 FactBox and Nutshell.
Object compatibility
2 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
FactBox: Not applicable — no public API endpoints are published..
Data volume sensitivity
FactBox 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 FactBox to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your FactBox 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 FactBox
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.