CRM migration
Field-level mapping, validation, and rollback between ArkCase and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
ArkCase
Source
Nutshell
Destination
Compatibility
10 of 10
objects map 1:1 between ArkCase and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
ArkCase is a modular case-management platform built for legal, FOIA, and government workflows — it tracks complaints, case files, people, organizations, documents, and tasks across configurable BPMN workflows. Nutshell is a sales-focused CRM that structures around People, Companies, Leads, and Deals with built-in pipeline stages and activity logging. These platforms share contact and company models but diverge sharply on case management semantics and workflow architecture. FlitStack AI extracts ArkCase People and Organizations for direct mapping to Nutshell contacts and companies. ArkCase complaints and cases map to Nutshell leads and deals — your team decides during planning whether closed cases become deals or historical leads. Tasks migrate as Nutshell activities (calls, emails, meetings) with original timestamps. Document attachments download and re-upload to Nutshell Files, linked to the corresponding contact or company record. ArkCase BPMN workflows, automations, and case-specific configurations do not migrate — they require rebuild in Nutshell or third-party tools. We export workflow definitions as reference documentation for your admin. ArkCase custom fields and lookup configurations surface as Nutshell custom fields during the mapping phase, so nothing is silently dropped.
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 ArkCase 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.
ArkCase
People
Nutshell
Person (Contact)
1:1ArkCase People map 1:1 to Nutshell People. First name, last name, email, phone, address, and title fields carry over directly. Owner assignment resolves by email match to Nutshell users. Primary organization link maps to Nutshell's Company association, maintaining the relationship between contacts and their employer.
ArkCase
Organization
Nutshell
Company
1:1ArkCase Organizations map to Nutshell Companies. Name, website, industry, employee count, and address fields translate directly. Parent-child organization hierarchies in ArkCase collapse to a single Parent Company link in Nutshell, preserving the primary hierarchy. This ensures that the organizational structure is maintained at the top level while simplifying the data model.
ArkCase
Complaint
Nutshell
Lead
1:1ArkCase Complaints map to Nutshell Leads. The complaint type, status, and description fields become Lead source, status, and notes respectively. Filing date preserves as original create date in a custom field since Nutshell Leads do not retain separate creation timestamps by default.
ArkCase
Case File
Nutshell
Deal
1:1ArkCase Case Files map to Nutshell Deals. Case number becomes deal name, case status maps to deal stage (with value mapping per your configured stages), and case value maps to deal amount. Open cases become open deals; closed cases become closed-won or closed-lost deals based on disposition.
ArkCase
Task
Nutshell
Activity (Call / Email / Meeting)
1:1ArkCase Tasks migrate as Nutshell activities. Task type (call, email, meeting) determines the Nutshell activity type. Original timestamps, assignees, and descriptions carry over. Completed tasks preserve completion status and notes. All activity records maintain their original creation dates to ensure historical accuracy in your sales reporting and compliance documentation.
ArkCase
Document / File Attachment
Nutshell
Nutshell File
1:1ArkCase documents download from source storage, re-upload to Nutshell Files, and link to the corresponding Person or Company record. Version history collapses to the current revision. ArkCase's check-in/check-out metadata stores as a custom note field in Nutshell, preserving file locking information for audit purposes even though the locking mechanism itself does not transfer.
ArkCase
ArkCase Custom Object
Nutshell
Nutshell Custom Field
1:1ArkCase custom objects that are simple key-value pairs map to Nutshell custom fields on the relevant Person, Company, or Lead object. N:N custom object relationships require custom field or note-based representation since Nutshell does not support junction objects for custom objects.
ArkCase
Tag
Nutshell
Nutshell Tag
1:1ArkCase Tags migrate as Nutshell Tags applied to the corresponding Person, Company, Lead, or Deal record. Tag names preserve exactly; no value transformation occurs. This direct tag mapping ensures that your categorization and segmentation logic remains intact after migration, allowing your sales and marketing teams to continue using existing tag-based workflows without any manual re-tagging efforts.
ArkCase
Cost Tracking / Time Entry
Nutshell
Custom Field on Deal
1:1ArkCase time entries and cost tracking records have no direct Nutshell equivalent. We preserve them as custom fields on the mapped Deal record — your team decides whether to use Nutshell's built-in billing integration or export to a separate time-tracking tool.
ArkCase
ArkCase User / Owner
Nutshell
Nutshell User
1:1ArkCase user accounts resolve to Nutshell users by email address match. Unmatched ArkCase owners flag before migration — either invite them to Nutshell first or reassign their records to a fallback user. This resolution process ensures that every migrated record maintains proper ownership attribution and audit trails, preventing orphaned records in your new Nutshell CRM environment.
| ArkCase | Nutshell | Compatibility | |
|---|---|---|---|
| People | Person (Contact)1:1 | Fully supported | |
| Organization | Company1:1 | Fully supported | |
| Complaint | Lead1:1 | Fully supported | |
| Case File | Deal1:1 | Fully supported | |
| Task | Activity (Call / Email / Meeting)1:1 | Fully supported | |
| Document / File Attachment | Nutshell File1:1 | Fully supported | |
| ArkCase Custom Object | Nutshell Custom Field1:1 | Fully supported | |
| Tag | Nutshell Tag1:1 | Fully supported | |
| Cost Tracking / Time Entry | Custom Field on Deal1:1 | Fully supported | |
| ArkCase User / Owner | Nutshell User1: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.
ArkCase gotchas
Custom BPMN workflows do not auto-migrate between instances
Time entries with inactive user references will fail import
FOIA request stage names vary by jurisdiction and require explicit mapping
Open-source tier lacks a documented bulk API
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
Discover ArkCase data model and custom configurations
FlitStack connects to your ArkCase instance via API (cloud) or read-only database (on-premise). We extract all People, Organizations, Complaints, Case Files, Tasks, and Document metadata. We catalog custom object definitions, lookup relationships, and workflow configurations. A data profiling report identifies gaps — duplicate records, missing required fields, and N:N relationship patterns. This report shapes the mapping plan before any transformation logic is written.
Map ArkCase modules to Nutshell objects with stakeholder sign-off
Based on the discovery report, FlitStack produces a mapping plan that routes each ArkCase module (People → Person, Organization → Company, Complaint → Lead, Case File → Deal, Task → Activity). Your team reviews the plan and decides how case files split between Leads and Deals, which custom fields create in Nutshell, and which ArkCase fields discard. No data moves until you approve the mapping plan.
Create Nutshell custom fields and resolve owner mappings
FlitStack creates custom fields in Nutshell for all ArkCase fields that have no native equivalent (Original_Create_Date__c, Deal_Type__c, etc.) via the Nutshell API. We match ArkCase owners to Nutshell users by email. Unmatched owners flag in a resolution report — your team either invites them to Nutshell or assigns fallback owners before migration runs. No record migrates without a valid owner.
Run a sample migration with field-level diff
A representative slice — typically 100–500 records spanning People, Organizations, Complaints, Case Files, and Tasks — migrates to Nutshell in a staging pass. FlitStack generates a field-level diff comparing source values to destination values so you can verify date preservation, owner resolution, case-to-deal routing, and custom field population. You approve the sample results before the full migration is scheduled, ensuring confidence in the data transformation logic.
Execute full migration with delta-pickup and rollback readiness
The full migration runs against Nutshell. A delta-pickup window (24–48 hours) captures records modified in ArkCase during cutover so Nutshell reflects the final state at go-live. All operations log to an audit trail. If reconciliation fails, one-click rollback reverts Nutshell to the pre-migration state. Your team continues working in ArkCase throughout cutover — FlitStack uses scoped read access only and does not lock or modify your ArkCase instance.
Platform deep dives
ArkCase
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 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 ArkCase and Nutshell.
Object compatibility
1 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
ArkCase: Not publicly documented for any tier.
Data volume sensitivity
ArkCase 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 ArkCase to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your ArkCase 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 ArkCase
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.