CRM migration

Migrate from Clarra to Nutshell

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

Clarra logo

Clarra

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

11 of 11

objects map 1:1 between Clarra and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

Clarra logo

Clarra

What's pushing teams away

  • Limited public pricing transparency makes it difficult to predict costs as the firm scales, prompting firms to evaluate alternatives before committing.
  • Small company footprint (1-10 employees) raises concerns about long-term support and product roadmap stability for firms with large matter volumes.
  • Absence of a documented public rate limit or bulk API endpoint makes high-volume data operations (e.g., importing large document sets) unpredictable without direct vendor confirmation.
  • Competitors like Clio and Smokeball have deeper market penetration and more third-party integrations, which attracts firms with complex existing toolchains.

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

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

maps to

Nutshell

Person

1:1
Fully supported

Clarra 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

maps to

Nutshell

Person — Custom Field

1:1
Fully supported

Clarra 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

maps to

Nutshell

Company

1:1
Fully supported

Clarent 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

maps to

Nutshell

Deal

1:1
Fully supported

Clarra 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

maps to

Nutshell

Deal — Custom Fields

1:1
Fully supported

Clarra 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

maps to

Nutshell

Task

1:1
Fully supported

Clarent 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

maps to

Nutshell

Activity (Event)

1:1
Fully supported

Clarent 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

maps to

Nutshell

Note

1:1
Fully supported

Clarent 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

maps to

Nutshell

File

1:1
Fully supported

Clarent 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

maps to

Nutshell

User

1:1
Fully supported

Clarent 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

maps to

Nutshell

No Equivalent

1:1
Fully supported

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

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.

Clarra logo

Clarra gotchas

High

No publicly documented API rate limits

Low

Report configurations do not migrate

Medium

Custom field schema varies by firm

Medium

Document binary storage handled separately from metadata

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

  • Matter-to-deal semantic gap requires custom field reconstruction

    Clarra matters have no native equivalent in Nutshell's data model — Nutshell deals are tied to sales pipeline stages and revenue tracking, not litigation lifecycle phases. We map matters to Nutshell deals and create custom fields (Original_Matter_Number__c, Matter_Type__c, Court_Venue__c, Opposing_Party__c) to preserve the full matter context. If your team needs to filter deals by matter type or court venue, those custom fields must be created in Nutshell Settings before migration. Without them, the matter-specific context collapses into a single deal name, which degrades reporting for litigation-heavy teams.

  • Nutshell's 25-field default limit per object may require plan upgrades

    Nutshell Foundation and Starter plans impose field-count limits per object. Clarra setups with 10+ custom properties per matter plus 5+ custom properties per party can exceed those limits after migration, especially when matter status, matter type, court venue, and opposing party all require custom fields on the deal. We audit field counts during the pre-migration assessment and flag whether a Nutshell Pro or Enterprise plan is required for custom field creation beyond the default limit. Upgrading after migration requires a support ticket to Nutshell; planning ahead avoids post-migration data reshuffling and ensures your custom fields are in place before the first record writes.

  • Document re-hosting is not a live link migration

    Clarra stores documents with version history and access controls tied to matter permissions. When we re-upload documents to Nutshell Files, they land as new files with no version history and no link back to the original Clarra document. The files are linked to the corresponding deal, person, or company, but Nutshell's file viewer does not surface versioned document chains. For teams that rely on document version history for litigation hold or compliance, we recommend exporting a Clarra document archive separately and linking it via Nutshell's external URL field.

  • Closed-loop docketing automation does not migrate to Nutshell sequences

    Clarra's docketing automation enforces deadlines and escalates missed filings automatically. Nutshell sequences (available on Pro+ plans) handle email follow-up cadences but have no docketing or deadline-enforcement logic. Teams that relied on Clarra's automated deadline reminders must rebuild that logic in Nutshell using task due dates, reminder rules, or a third-party docketing integration. We export Clarra workflow definitions as a structured reference, but the automation logic itself cannot be transferred programmatically.

  • Multi-party matter associations collapse to deal-linked people

    Clarra allows a single matter to have N parties of varying roles (multiple attorneys, opposing counsel, expert witnesses, clients). Nutshell deals link to people via Opportunity Contact Roles — a 1:N model where each person can have one role per deal. We map the primary attorney to the primary Contact Role and surface other parties as additional person records linked to the same deal. Role differentiation beyond the built-in Contact Role types requires a custom field on the person record.

Migration approach

Six steps for a successful Clarra to Nutshell data migration

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

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

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

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

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

Context on both ends of the pair

Clarra logo

Clarra

Source

Strengths

  • Free unlimited-user tier reduces upfront cost for small and mid-size law firms evaluating the platform.
  • Zapier integration provides no-code connectivity to 6,000+ external applications out of the box.
  • REST API with sandbox environment enables custom integrations and programmatic data operations for technical teams.
  • Multi-format export (CSV, XLSX, DOCX, PDF) gives flexibility in how data is extracted and reviewed before migration.

Weaknesses

  • Small company size and limited public funding history may concern firms requiring enterprise-grade vendor stability assurances.
  • No publicly documented rate limits for the API make it difficult to plan large-scale import or export operations upfront.
  • Limited public information about pricing tiers and feature-gating between plans creates friction during the buying and migration evaluation process.
  • Niche focus on entertainment and production company clients may limit appeal and out-of-the-box workflows for general litigation or corporate law firms.
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 Clarra 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

    Clarra: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Most Clarra-to-Nutshell migrations complete in 48–72 hours of clock time for under 25,000 records. The longest planning step is custom field creation in Nutshell (your admin must create the custom properties that map to Clarra's matter-type and party-role fields). Larger setups with 250,000+ records, complex matter hierarchies, or multiple custom property groups extend to 5–7 days. The delta-pickup window (24–48 hours) adds to the overall timeline but does not interrupt your team's use of Clarra.

Adjacent paths

Related migrations to explore

Ready when you are

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