CRM migration
Field-level mapping, validation, and rollback between Clarra and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Clarra
Source
Nutshell
Destination
Compatibility
11 of 11
objects map 1:1 between Clarra and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
Clarra and Nutshell occupy different corners of the business-software stack: Clarra is a matter-centric litigation platform with parties, docket events, and legal-document workflows; Nutshell is a sales-pipeline CRM with people, companies, leads, and deal tracking. The migration maps Clarra parties (attorneys, opposing counsel, clients) to Nutshell people, Clarra company records to Nutshell companies, and Clarra matters to Nutshell deals — with a custom field capturing the original matter number for reference. Tasks, events, and notes carry over as Nutshell tasks and activities with original create dates preserved. Document attachments are downloaded and re-uploaded to Nutshell Files. FlitStack AI sequences the migration so foreign-key relationships resolve correctly: companies first, then people, then deals. Workflows, automation rules, and template logic built in Clarra do not have equivalents in Nutshell and must be rebuilt manually after cutover. We deliver a field-level diff against a sample slice before committing the full run, and a 24–48 hour delta-pickup window captures in-flight changes 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 Clarra 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.
Clarra
Party
Nutshell
Person
1:1Clarra parties (attorneys, opposing counsel, clients, witnesses) map to Nutshell people. The party's primary organization links to a Nutshell company record. If a party has no associated organization, a placeholder company is created. Primary email, phone, and address fields carry over directly.
Clarra
Party Role
Nutshell
Person — Custom Field
1:1Clarra party roles (Plaintiff, Defense Attorney, Opposing Counsel, etc.) do not have a direct Nutshell equivalent. We migrate the role label as a custom pick-list field on the Nutshell Person record. Teams that need role-based filtering can use this custom field to segment their Nutshell people list.
Clarra
Organization
Nutshell
Company
1:1Clarent organizations linked to parties map to Nutshell companies. Company name, domain, industry, and address fields transfer directly. If multiple Clarra organizations share the same domain, we link the primary record and surface secondary organizations as related companies on the primary company page.
Clarra
Matter
Nutshell
Deal
1:1Clarra matters have no direct CRM analogue. We map them to Nutshell deals: the matter name becomes the deal name, and a custom field (Original_Matter_Number__c) preserves the Clarra matter ID for audit and reconciliation. Matter status (Open, Closed, Pending) maps to a Nutshell deal status custom field since Nutshell natively archives closed deals by removing them from the active pipeline.
Clarra
Matter Custom Properties
Nutshell
Deal — Custom Fields
1:1Clarra custom properties (case type, court venue, opposing party details, etc.) become Nutshell custom fields on the deal. Each custom property in Clarra requires a corresponding custom field to be created in Nutshell before migration runs. We deliver a custom-field creation plan as part of the pre-migration schema setup.
Clarra
Task
Nutshell
Task
1:1Clarent tasks attached to matters migrate to Nutshell tasks linked to the corresponding deal. Original create date, due date, assigned user (resolved by email match to Nutshell users), and task description are preserved. Completed status maps directly. Unresolved user assignments are flagged for manual routing after migration completes.
Clarra
Docket Event
Nutshell
Activity (Event)
1:1Clarent docket events (hearing dates, filing deadlines, deposition schedules) map to Nutshell activities of type 'Event'. The event subject carries the docket description, and the original event datetime is preserved. Nutshell's activity feed displays these alongside sales calls and meetings, giving the litigation team a complete calendar view within the CRM.
Clarra
Note
Nutshell
Note
1:1Clarent notes attached to matters, parties, or organizations migrate as Nutshell notes linked to the corresponding deal, person, or company record. Rich-text formatting is preserved where Clarra supports it. Original author is resolved by email match to a Nutshell user, and any unmatched authors are attributed to the migration owner account.
Clarra
Document
Nutshell
File
1:1Clarent file attachments (pleadings, contracts, correspondence PDFs) are downloaded from Clarra storage and re-uploaded to Nutshell Files, linked to the appropriate deal, person, or company record. Files over 25MB are flagged before migration so your team can split them manually or use an alternative storage solution.
Clarra
User / Owner
Nutshell
User
1:1Clarent users are matched to Nutshell users by email address. Unmatched users are flagged before migration — teams either invite them to Nutshell first or assign their records to a fallback owner. No record lands in Nutshell without an assigned user.
Clarra
Workflow / Automation
Nutshell
No Equivalent
1:1Clarent workflow rules, matter-lifecycle triggers, and docketing automation have no Nutshell equivalent. These must be rebuilt manually in Nutshell using sequences (Pro+), task rules, or third-party automation tools like Zapier. We export Clarra workflow definitions as a structured reference document for your admin to use during the rebuild phase.
| Clarra | Nutshell | Compatibility | |
|---|---|---|---|
| Party | Person1:1 | Fully supported | |
| Party Role | Person — Custom Field1:1 | Fully supported | |
| Organization | Company1:1 | Fully supported | |
| Matter | Deal1:1 | Fully supported | |
| Matter Custom Properties | Deal — Custom Fields1:1 | Fully supported | |
| Task | Task1:1 | Fully supported | |
| Docket Event | Activity (Event)1:1 | Fully supported | |
| Note | Note1:1 | Fully supported | |
| Document | File1:1 | Fully supported | |
| User / Owner | User1:1 | Fully supported | |
| Workflow / Automation | No Equivalent1: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.
Clarra gotchas
No publicly documented API rate limits
Report configurations do not migrate
Custom field schema varies by firm
Document binary storage handled separately from metadata
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 Clarra schema and Nutshell target configuration
Before extracting any data, FlitStack AI inventories Clarra's custom properties, matter types, party roles, and document volumes. We cross-reference these against Nutshell's current field configuration to identify gaps — specifically which custom fields need to be created in Nutshell, which Nutshell plan is required for custom field limits, and whether any Clarra field types (multi-select pick-lists, date ranges, etc.) require transformation logic. This audit generates a Nutshell field creation checklist your admin completes before migration runs.
Resolve users and owners by email match
Clarent users (attorneys, paralegals, admins) are matched against Nutshell users by email address. We generate an owner-resolution report showing matched users, unmatched users, and the number of records each unmatched user owns. Your team either invites unmatched users to Nutshell before migration or assigns their records to a fallback Nutshell user. No record is written without a valid owner assignment.
Migrate companies, then people, then deals
Clarent organizations migrate first to populate Nutshell companies. Clarent parties migrate next, linked to their resolved Nutshell company records. Clarent matters migrate last, linked to their responsible attorney (now a Nutshell user) and associated with the relevant Nutshell company. This sequence respects Nutshell's foreign-key requirements: companies must exist before people can reference them, and people must exist before deals can link to them via Contact Roles.
Run a sample migration with field-level diff
A representative slice — typically 100–300 records covering 5–10 matters, 20–50 parties, 10–20 companies, and a mix of tasks and docket events — migrates against the live Nutshell instance. We generate a field-level diff showing every source field, its mapped destination field, the value in Clarra, and the value written to Nutshell. You verify matter-to-deal mapping, custom field population, owner resolution, and document attachment integrity before the full run commits.
Execute full migration with delta-pickup window
The full dataset migrates in sequenced batches following the companies-people-deals order established in planning. A delta-pickup window opens immediately after the bulk write completes — typically 24–48 hours — during which any Clarra records modified or created during the migration window are captured and written to Nutshell. Audit logs record every create, update, and link operation. If reconciliation reveals discrepancies or the cutover fails, one-click rollback reverts the Nutshell instance to its pre-migration state without manual data cleanup.
Platform deep dives
Clarra
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 Clarra 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
Clarra: Not publicly documented.
Data volume sensitivity
Clarra 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 Clarra to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Clarra 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 Clarra
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.