CRM migration
Field-level mapping, validation, and rollback between AgileCase and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
AgileCase
Source
Nutshell
Destination
Compatibility
11 of 11
objects map 1:1 between AgileCase and Nutshell.
Complexity
BStandard
Timeline
3–7 days
Overview
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.
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 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
Nutshell
Deal
1:1AgileCase 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
Nutshell
People
1:1AgileCase 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
Nutshell
Company
1:1AgileCase 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
Nutshell
People (owner field) / User
1:1AgileCase 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
Nutshell
Deal Stage / Custom Field
1:1AgileCase 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
Nutshell
Deal Custom Fields / People Custom Fields
1:1AgileCase 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
Nutshell
Activity (File attachment)
1:1AgileCase 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
Nutshell
Activity (Note)
1:1AgileCase 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
Nutshell
No Equivalent
1:1AgileCase 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
Nutshell
Custom Datetime Fields
1:1AgileCase 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)
Nutshell
Lead
1:1AgileCase 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.
| AgileCase | Nutshell | Compatibility | |
|---|---|---|---|
| Case | Deal1:1 | Fully supported | |
| Contact / Person | People1:1 | Fully supported | |
| Company | Company1:1 | Fully supported | |
| Case Assignee / Owner | People (owner field) / User1:1 | Fully supported | |
| Case Status / Priority | Deal Stage / Custom Field1:1 | Fully supported | |
| Case Custom Fields | Deal Custom Fields / People Custom Fields1:1 | Fully supported | |
| Case Attachments / Files | Activity (File attachment)1:1 | Fully supported | |
| Case Comments / Notes | Activity (Note)1:1 | Fully supported | |
| Case Plan / Workflow | No Equivalent1:1 | Fully supported | |
| Audit Trail / Field History | Custom Datetime Fields1:1 | Fully supported | |
| Lead (incoming prospect) | Lead1: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.
AgileCase gotchas
Audit trail retention is tier-dependent
Post-termination 30-day export window in DPA
Blob storage document extraction requires flattening
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
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.
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.
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.
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.
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.
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
AgileCase
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 AgileCase 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
AgileCase: Not publicly documented.
Data volume sensitivity
AgileCase exposes a bulk API — large-volume migrations stream efficiently.
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 AgileCase to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your AgileCase 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 AgileCase
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.