CRM migration

Migrate from AgileCase to Nutshell

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

AgileCase logo

AgileCase

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

11 of 11

objects map 1:1 between AgileCase and Nutshell.

Complexity

BStandard

Timeline

3–7 days

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

AgileCase organizes data around Cases with capture workflows, custom fields, and audit trails. Nutshell is a sales CRM that structures data around People (contacts), Companies, Leads, and Deals with pipeline views. The fundamental model difference is that AgileCase treats 'Case' as the primary work unit; Nutshell has no native Case object — cases map to Deals or become Nutshell Activities, depending on whether they represent billable work or internal tracking. FlitStack AI extracts AgileCase records via REST API or CSV export, maps Case fields to Nutshell Deal fields and custom fields on People/Companies, and resolves AgileCase assignees to Nutshell users by email. Automations, case plans, and workflow scripts do not migrate — FlitStack exports those definitions as a rebuild reference for Nutshell automation or manual setup. The migration sequence runs Companies first (foreign key for People), then People, then Cases-as-Deals, with a 24–48-hour delta-pickup window to capture in-flight records at 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

AgileCase logo

AgileCase

What's pushing teams away

  • User limits of 15 on Professional and 30 on Business force growing firms to migrate when they exceed these thresholds, often mid-workflow.
  • Limited automation and report counts on Professional tier become restrictive as case volume increases, pushing teams toward platforms with fewer structural caps.
  • Enterprise pricing requires custom quotes with no public range, making budget planning difficult and prompting firms to evaluate alternatives with transparent pricing.
  • Workflow automation logic and custom reports do not transfer between platforms, creating significant rebuild effort that makes switching costly and slow.

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

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

AgileCase

Case

maps to

Nutshell

Deal

1:1
Fully supported

AgileCase Case is the primary work unit and may represent billable work or internal support. In Nutshell, revenue‑bearing Cases map to Deal records, where the case name becomes the Deal name and the case stage maps to a Nutshell pipeline stage. Cases without monetary value are converted to Nutshell Activity notes linked to the corresponding Deal or People record.

AgileCase

Contact / Person

maps to

Nutshell

People

1:1
Fully supported

AgileCase contact records, including name, email address, phone number, and physical address, map directly to Nutshell People objects. The email field serves as the primary identifier for duplicate detection and for linking to Nutshell Companies. When multiple contacts are associated with a single Case in AgileCase, each contact becomes a separate Nutshell People record, preserving all contact details.

AgileCase

Company

maps to

Nutshell

Company

1:1
Fully supported

AgileCase Company records map one‑to‑one to Nutshell Company objects. Standard fields such as company name, website domain, industry classification, and employee count transfer directly to Nutshell's matching fields. Because Nutshell Companies serve as the parent entity for People records, each Company must be migrated before any People records that reference it through the 'company' link to maintain referential integrity.

AgileCase

Case Assignee / Owner

maps to

Nutshell

People (owner field) / User

1:1
Fully supported

AgileCase assigns cases to users by internal ID. FlitStack resolves each assignee email against Nutshell users by email match. Unmatched assignees are flagged before migration; your team either invites them to Nutshell or assigns their records to a fallback user.

AgileCase

Case Status / Priority

maps to

Nutshell

Deal Stage / Custom Field

1:1
Fully supported

AgileCase case status values — Open, In Progress, Resolved, and Closed — translate into corresponding Nutshell Deal stage names using explicit value‑mapping rules. Similarly, AgileCase priority levels (Low, Medium, High, Critical) are represented as a custom pick‑list field on the Nutshell Deal, ensuring that urgency information is retained and visible within the deal record.

AgileCase

Case Custom Fields

maps to

Nutshell

Deal Custom Fields / People Custom Fields

1:1
Fully supported

AgileCase Business and Enterprise plans allow custom fields per case type. Each custom field requires a matching Nutshell custom field. Text, number, date, and pick-list field types are supported; Nutshell custom fields are created per entity (Deal or People) before migration.

AgileCase

Case Attachments / Files

maps to

Nutshell

Activity (File attachment)

1:1
Fully supported

AgileCase file attachments such as documents, images, and PDFs are downloaded from the source environment and re‑uploaded to Nutshell as Activity records attached to the corresponding Deal or People object. The original upload timestamp, the name of the uploader, and the file type are preserved as metadata on the Activity record, maintaining the original context for future reference.

AgileCase

Case Comments / Notes

maps to

Nutshell

Activity (Note)

1:1
Fully supported

AgileCase case notes and threaded comment histories are migrated as Nutshell Activity records of type 'note' linked to the relevant Deal or People entry. Each migrated note retains the original author name and the exact timestamp from AgileCase, allowing teams to review the full conversation timeline within Nutshell after migration.

AgileCase

Case Plan / Workflow

maps to

Nutshell

No Equivalent

1:1
Fully supported

AgileCase case plans, task templates, and custom workflow scripts have no direct equivalent in Nutshell's feature set. FlitStack extracts these workflow definitions and exports them as a structured JSON document that your Nutshell administrator can use as a reference to rebuild equivalent automation using Nutshell Sequences, manual task creation, or third‑party workflow tools.

AgileCase

Audit Trail / Field History

maps to

Nutshell

Custom Datetime Fields

1:1
Fully supported

AgileCase maintains a 180‑day audit trail that logs every field change on a case, capturing the before‑and‑after values, the user who made the change, and the exact timestamp. Nutshell does not provide a native change‑history log, so FlitStack surfaces the original case creation date, last‑modified date, and key audit events as custom datetime and user fields on the Deal record, enabling reporting continuity without a native audit feature.

AgileCase

Lead (incoming prospect)

maps to

Nutshell

Lead

1:1
Fully supported

AgileCase leads that exist before a case is opened are routed to Nutshell Leads, preserving source‑tracking information such as UTM parameters and referrer data as custom fields on the Lead. When a Lead in AgileCase converts to a Case, FlitStack creates a corresponding Deal in Nutshell, linking the new opportunity to the originating Lead record to maintain the full conversion history.

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.

AgileCase logo

AgileCase gotchas

Medium

Audit trail retention is tier-dependent

High

Post-termination 30-day export window in DPA

Medium

Blob storage document extraction requires flattening

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

  • AgileCase Case maps to Nutshell Deal — not a native case object

    Nutshell has no Case object. Every AgileCase Case that represents billable or trackable work migrates to a Nutshell Deal, and cases that are internal support items (with no revenue) become Nutshell Activity notes. If your team relies on AgileCase's case-type taxonomy to segment reporting, you must pre-configure Nutshell pipeline stages and a Case_Type__c custom field so the migration maps cleanly. The stage-to-pipeline routing is the single most consequential schema decision before data lands.

  • AgileCase automations and case plans have no Nutshell equivalent

    AgileCase Business and Enterprise plans include case plans, task templates, and workflow scripts that route work through stages automatically. Nutshell Sequences and Sales Automation run on People/Lead events, not on Deals, and there is no case-plan concept. We export your AgileCase workflow definitions as a structured JSON document with step names, conditions, and actions. Your Nutshell admin uses this as a rebuild reference — FlitStack does not auto-convert logic between fundamentally different automation models.

  • Per-pipeline custom fields in Nutshell require pre-configuration

    Nutshell introduced per-pipeline custom fields, which means a field that exists on Cases in one AgileCase case type may need a separate Nutshell custom field for each pipeline where it applies. AgileCase custom fields are global per case type; Nutshell custom fields are entity-scoped but pipeline-specific when used in pipeline views. We deliver a pipeline-to-custom-field mapping plan before migration so your Nutshell admin creates the right fields on the right entities before records insert.

  • Nutshell audit trail is not native — field history is a custom-field migration

    AgileCase Business and Enterprise plans include a 180-day audit trail that logs every field change on every Case with timestamps and user attribution. Nutshell has no native change-history log — there is no equivalent 'last modified by' or field-level revision trail. We surface create date, last modified date, and assignee history as custom datetime and user fields on the Deal record, but the granular before/after per-field history cannot be preserved without a custom Nutshell audit object that your admin would need to build separately.

  • AgileCase file attachments re-uploaded as Nutshell Activity records

    AgileCase stores files with audit metadata (uploader, upload date, file type) in its document management layer. Nutshell does not have a native document management object — files attach to Activity records (notes, tasks, emails). We download each AgileCase file and re-upload it to the corresponding Nutshell Deal or People record as an Activity attachment. Large file batches (above 500 attachments per migration) require staged upload scheduling to respect Nutshell API rate limits and are priced in the upper range.

Migration approach

Six steps for a successful AgileCase to Nutshell data migration

  1. Scope AgileCase data and design Nutshell pipeline schema

    FlitStack AI extracts a full data inventory from AgileCase — case types, custom fields, contact counts, file attachment inventory, and assignee list. We deliver a migration plan that maps each AgileCase case type to a Nutshell pipeline, defines which cases become Deals vs. Activity notes, and lists every custom field that needs to be created in Nutshell before migration. Your Nutshell admin creates the pipelines, stages, and custom fields; we validate the schema before moving data.

  2. Export AgileCase records via REST API and validate record counts

    AgileCase exposes a REST API for exporting cases, contacts, companies, and file metadata. FlitStack pulls all records in scope and runs a data‑quality audit — flagging records with missing required fields (name, email, case status), duplicate contacts by email, and orphan cases with no associated contact. You review the audit report and approve record‑cleanup rules before the sample migration runs.

  3. Resolve AgileCase assignees to Nutshell users by email

    Resolve AgileCase assignees to Nutshell users by email. Every AgileCase assignee and contact owner is matched by email address against existing Nutshell user accounts. FlitStack produces an owner-resolution report that lists matched users, unmatched assignees, and suggested fallback assignments for each. Your team then either invites the missing Nutshell users or approves the fallback owner mapping. No Deal record migrates without a valid Nutshell owner ID, which prevents orphaned records and ensures proper accountability at go‑live.

  4. Run sample migration with field-level diff

    A representative slice of 100–300 records migrates first — spanning all case types, a range of case statuses, and records with and without file attachments. FlitStack generates a field‑level diff comparing source AgileCase values against the migrated Nutshell records. You verify that case status maps to the correct Nutshell stage, custom fields land on the right entity, and file attachments attach to the right Deal or People record. Mapping corrections are applied before the full run commits.

  5. Execute full migration with delta-pickup window

    The full migration runs against Nutshell's JSON-RPC API. A 24–48-hour delta‑pickup window runs in parallel, capturing any AgileCase records created or modified during the cutover window. Your team continues working in AgileCase throughout this period — FlitStack uses read‑only API access. An audit log records every operation (insert, update, skip) and a reconciliation count confirms all records arrived. One‑click rollback reverts Nutshell to its pre‑migration state if the count check fails.

  6. Deliver migration audit log and rebuild reference export

    FlitStack delivers a complete migration audit log (source ID, destination ID, operation, timestamp, operator) and a structured JSON export of AgileCase workflow definitions for your Nutshell admin to use as a rebuild reference. Post‑migration, your team verifies deal pipeline totals in Nutshell match the AgileCase case report and closes the AgileCase account at your discretion — FlitStack does not touch your source data or require account suspension.

Platform deep dives

Context on both ends of the pair

AgileCase logo

AgileCase

Source

Strengths

  • Tiered storage: 50GB on Professional, unlimited on Business with fair-use policy.
  • Audit trail tracking with 180-day minimum retention on Professional tier.
  • REST API, CSV, and Excel import options for data onboarding.
  • Workflow management with task sequences, case plans, and custom scripts.
  • Client-facing portal for status sharing and secure document exchange.

Weaknesses

  • User caps (15 Professional, 30 Business) limit scalability for larger legal departments.
  • Automation and report limits on lower tiers require upgrades as usage grows.
  • No public pricing for Enterprise tier, complicating cost comparisons during vendor evaluation.
  • Workflow definitions and automation rules are not portable between platforms, requiring manual rebuild.
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 AgileCase 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

    AgileCase: Not publicly documented.

  • Data volume sensitivity

    A

    AgileCase exposes a bulk API — large-volume migrations stream efficiently.

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Most AgileCase-to-Nutshell migrations complete within 3–7 calendar days for under 50,000 records. The longest phase is designing the Nutshell pipeline and custom field schema before data moves — that planning step typically takes 2–4 days. Larger migrations with 200,000+ records, multiple case types, or significant file attachment volume extend to 2–3 weeks. A 24–48-hour delta-pickup window at cutover is included in every migration and runs concurrently with your team's final AgileCase work session.

Adjacent paths

Related migrations to explore

Ready when you are

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