CRM migration

Migrate from CaseManager to Nutshell

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

CaseManager logo

CaseManager

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

12 of 12

objects map 1:1 between CaseManager and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

CaseManager organizes work around cases, contacts, companies, and time-stamped activity logs — a case-centric model that serves support and service workflows well. Nutshell inverts this orientation, structuring data around People, Companies, Deals, and pipeline stages, with cases treated as either custom fields on leads or deal properties depending on whether your CaseManager cases represent sales opportunities or service records. FlitStack AI extracts your CaseManager data via its API, transforms case fields into Nutshell custom fields, maps owner IDs by email match against Nutshell users, preserves all activity history as Tasks and Events, and re-uploads attachments from CaseManager storage to Nutshell Files. We sequence the migration so parent records (Companies) resolve before child records (People) and Activities reference valid owners — preventing foreign-key failures. Workflows, automations, and assignment rules in CaseManager have no equivalent in Nutshell and must be rebuilt; we export definitions as a rebuild reference. The migration uses scoped read access on CaseManager — your team keeps working throughout — with a delta-pickup window capturing any records modified during the cutover window before we flip the go-live switch.

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

CaseManager logo

CaseManager

What's pushing teams away

  • Pricing is opaque and perceived as unfavorable by customers who want cost transparency before committing to a multi-year subscription.
  • Glitches in progress tracking cause data integrity concerns, with reviewers reporting that logged time sometimes fails to persist correctly.
  • The platform lacks modern automation and integration capabilities, pushing growing law firms toward more connected legal tech stacks.
  • No mobile app or real-time sync means attorneys working remotely cannot access or update case files without desktop access.
  • Support responsiveness and feature roadmap are not clearly communicated, leading long-term users to feel the product is stagnant.

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

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

CaseManager

Case

maps to

Nutshell

People (custom fields) or Deal (custom fields)

1:1
Fully supported

Nutshell has no native case object. If your CaseManager cases represent sales opportunities, they map to Nutshell Deals with case metadata (status, priority, case type) stored as custom fields on the Deal. If cases are service records, they map to People with case fields as custom fields on the People record. We determine the correct routing during the discovery phase before the migration plan is finalized.

CaseManager

Contact

maps to

Nutshell

People

1:1
Fully supported

CaseManager contacts map 1:1 to Nutshell People. The contact's name, email, phone, job title, and address fields map to their Nutshell equivalents. Each People record receives a Source_System_ID__c custom field storing the original CaseManager contact ID for traceability and delta-run de-duplication.

CaseManager

Company

maps to

Nutshell

Company

1:1
Fully supported

CaseManager company records map directly to Nutshell Company records. Company name, domain, industry, employee count, and annual revenue map to their Nutshell equivalents. Nutshell Company stores a primary address; if CaseManager stores multiple addresses per company, the primary address migrates and secondary addresses are preserved as a custom text field.

CaseManager

Case Contact (N:N association)

maps to

Nutshell

People linked to Company (primary) + Account Contact Relationship

1:1
Fully supported

CaseManager allows multiple contacts to be associated with a single case. Nutshell links a People record to one primary Company. We migrate the primary contact-company link directly and surface any additional company associations as Nutshell Account Contact Relationship records, which your admin can review and activate post-migration.

CaseManager

Activity: Email

maps to

Nutshell

Task (type = Email)

1:1
Fully supported

CaseManager email activities map to Nutshell Tasks with type = Email. The task subject, body, timestamp, and owning user are preserved. The task is linked to the corresponding People or Deal record in Nutshell based on the CaseManager case it was attached to.

CaseManager

Activity: Call Log

maps to

Nutshell

Task (type = Call)

1:1
Fully supported

CaseManager call logs migrate as Nutshell Tasks with type = Call. Call duration, direction (inbound/outbound), and outcome stored in the task body or as custom task fields. Original timestamps and call owners (resolved by email match) are preserved on each Task record.

CaseManager

Activity: Meeting

maps to

Nutshell

Event

1:1
Fully supported

CaseManager meeting records migrate to Nutshell Events. Start time, end time, location, attendees, and meeting notes are preserved on the Event. The Event is linked to the corresponding People or Deal record in Nutshell. Nutshell's calendar integration (Google Workspace, Office 365) allows Events to surface in users' native calendars post-migration.

CaseManager

Note / Comment

maps to

Nutshell

People Note / Deal Note

1:1
Fully supported

CaseManager notes attached to cases or contacts migrate as Nutshell Notes. The note body, author (resolved by email match), and create timestamp are preserved. Nutshell Notes attach to the corresponding People or Deal record. Rich-text formatting in CaseManager notes is flattened to plain text to ensure compatibility with Nutshell's note display.

CaseManager

Attachment / File

maps to

Nutshell

Nutshell Files

1:1
Fully supported

CaseManager file attachments on cases or contacts are downloaded from CaseManager storage and re-uploaded to Nutshell Files. Each file is linked to the corresponding People, Company, or Deal record. Nutshell enforces a 25MB per-file size limit; files exceeding this are flagged for manual chunking or alternative delivery.

CaseManager

Custom Field (object-level)

maps to

Nutshell

Nutshell Custom Field

1:1
Fully supported

Each CaseManager custom field on Cases, Contacts, or Companies requires a corresponding custom field in Nutshell. We create the custom field on the correct Nutshell object (People, Company, or Deal) with a matching data type (text, number, date, pick-list, or checkbox) before the migration run. Pick-list value mappings are built value-by-value where the source and destination pick-list options differ.

CaseManager

Case Owner

maps to

Nutshell

People owner (resolved by email)

1:1
Fully supported

CaseManager stores owner as a user ID. We resolve each owner ID to a Nutshell user account by matching the CaseManager owner's email against Nutshell user emails. Unresolved owners — those with no matching Nutshell account — are flagged before the migration runs, and their records are assigned to a designated fallback owner until accounts are provisioned.

CaseManager

Workflow / Assignment Rule

maps to

Nutshell

No equivalent

1:1
Fully supported

CaseManager workflow rules and auto-assignment logic have no direct equivalent in Nutshell. Nutshell's automation model applies to Deals, not cases. We export the CaseManager workflow definitions as a structured reference document your Nutshell admin can use to rebuild equivalent routing logic in Nutshell's automation tools.

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.

CaseManager logo

CaseManager gotchas

High

No documented public API for bulk data extraction

High

Progress-tracking timestamps fail to persist in some records

Medium

Custom fields vary by firm configuration with no schema registry

Medium

Attachments and document blobs are not included in CSV exports

Low

Pricing is opaque and not available on the vendor website

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

  • Nutshell has no native case object — routing decision is migration-critical

    CaseManager's core record type is a Case, but Nutshell does not have a case object. Cases must route to either Nutshell Deals (if they represent sales opportunities with amounts and close dates) or People records with custom fields (if they represent service or support records). This routing decision is made during discovery and determines the entire schema setup on the Nutshell side — the wrong choice means case metadata lands in the wrong place and reports break. We present a routing recommendation based on your CaseManager case fields before the migration plan is finalized.

  • CaseManager API rate limits throttle bulk extraction and extend timelines

    CaseManager's API enforces per-endpoint rate limits that govern how many records we can extract per minute during the bulk read phase. For large datasets (50,000+ records), these limits can extend the extraction window from hours to days. We monitor API response headers and distribute extraction requests across off-peak windows to stay within limits without triggering throttling errors. The timeline estimate accounts for rate-limit pacing; we surface any timeline risk before the migration begins.

  • Case priority and type pick-lists require value-by-value mapping

    CaseManager's custom priority and type pick-lists are defined per-account and may include values that do not map directly to Nutshell's default option sets. We build a value-mapping table during discovery that pairs each CaseManager pick-list value to its Nutshell equivalent, flagging any values with no natural mapping for your admin to decide. Unmapped values are preserved in a custom text fallback field to prevent data loss if a value has no clean Nutshell counterpart.

  • Owner resolution by email fails for inactive CaseManager users

    CaseManager stores owner as a user ID linked to an email address. When we resolve owner IDs to Nutshell user accounts by email match, inactive or deleted CaseManager users have no email to match against. Their case records receive a fallback owner assignment (designated during setup) and the original owner ID is preserved in a Source_Owner_ID__c custom field so you can audit the original assignment post-migration and re-assign records manually.

Migration approach

Six steps for a successful CaseManager to Nutshell data migration

  1. Connect both platforms and audit the CaseManager data model

    We authenticate to the CaseManager API using your API credentials and pull a schema export of all objects, custom fields, and pick-list values. Simultaneously, we inspect the Nutshell account to confirm available custom field slots and verify user account emails for owner resolution. This step produces the field-mapping spreadsheet that forms the migration plan and surfaces any missing Nutshell custom fields that need to be created before data lands.

  2. Extract full CaseManager dataset with rate-limit pacing

    We run a full export of all Cases, Contacts, Companies, Activities (emails, calls, meetings), Notes, and Attachments from CaseManager. Extraction is distributed across time windows to stay within the API's rate limits. Activities and Notes are pulled with their parent-case references so they can be linked correctly to the migrated records in Nutshell. Attachments are downloaded to temporary storage for re-upload in the load phase.

  3. Run a sample migration with field-level diff

    A representative slice — typically 100–300 records spanning cases, contacts, companies, and activities — migrates to Nutshell first. We generate a field-level diff comparing source values to destination field values so you can verify that case-status value mappings, custom field routing, and owner resolution are correct before the full run commits. Any mapping errors are corrected and the sample re-runs until the diff passes.

  4. Execute full migration with delta-pickup cutover

    The full dataset loads into Nutshell using Nutshell's import API, with parent records (Companies) migrated first, then People, then Deals or case-bearing People records, then Activities and Notes. Files are re-uploaded from CaseManager storage to Nutshell Files and linked to their parent records. After the initial load completes, a delta-pickup window (typically 24–48 hours) captures any CaseManager records created or modified during the cutover before the go-live switch.

  5. Validate, audit, and hand off rebuild reference

    We run a reconciliation report comparing record counts and key field values between CaseManager and Nutshell to confirm the migration landed cleanly. Owner resolution coverage is reported; any unresolved owners are flagged for manual re-assignment. We deliver the exported CaseManager workflow definitions as a rebuild reference for your Nutshell admin, along with a custom-field setup checklist so Nutshell-side schema is documented and ready for ongoing use.

Platform deep dives

Context on both ends of the pair

CaseManager logo

CaseManager

Source

Strengths

  • Per-case CSV export provides a manual but accessible data extraction path for attorneys.
  • Time-stamped work logging satisfies basic billing justification requirements for small law practices.
  • Document digitization converts physical case files into searchable electronic records.
  • Simple per-case interface reduces training time for paralegal and administrative staff.

Weaknesses

  • No public API means all migration work requires custom engineering against undocumented export formats.
  • Progress-tracking glitches reported in G2 reviews indicate potential data integrity issues in source records.
  • Pricing model is not publicly documented, complicating renewal and migration cost planning.
  • No bulk export capability means each case must be manually triggered for export in the UI.
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. 3 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 CaseManager and Nutshell.

  • Object compatibility

    B

    3 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

    CaseManager: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Most CaseManager-to-Nutshell migrations complete within 48–72 hours of clock time for datasets under 50,000 records. Larger setups exceeding 200,000 records or those with extensive custom-field schemas extend to 3–7 days. The longest planning step is the case-routing decision — whether cases should land as Nutshell Deals or as People with custom fields — because it determines the schema setup on the Nutshell side before validation can run. API rate-limit pacing on the CaseManager export side can add 12–24 hours for very large datasets.

Adjacent paths

Related migrations to explore

Ready when you are

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