CRM migration

Migrate from ArkCase to Nutshell

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

ArkCase logo

ArkCase

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

10 of 10

objects map 1:1 between ArkCase and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

ArkCase logo

ArkCase

What's pushing teams away

  • Organisations report that the open-source tier ships with minimal support and no high-availability clustering, causing reliability concerns for production workloads that would require Enterprise pricing to resolve.
  • The learning curve for non-technical staff around BPMN workflow design is steeper than marketed — legal teams frequently need external consultants to build and maintain non-trivial routing logic.
  • Integration with third-party ECM repositories requires custom configuration that is not always well-documented, leading to support tickets and extended implementation timelines.
  • The analytics and reporting module on the open-source tier is described as limited, pushing growing organisations toward the paid tiers or an external BI tool, which adds cost and complexity.

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

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

maps to

Nutshell

Person (Contact)

1:1
Fully supported

ArkCase 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

maps to

Nutshell

Company

1:1
Fully supported

ArkCase 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

maps to

Nutshell

Lead

1:1
Fully supported

ArkCase 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

maps to

Nutshell

Deal

1:1
Fully supported

ArkCase 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

maps to

Nutshell

Activity (Call / Email / Meeting)

1:1
Fully supported

ArkCase 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

maps to

Nutshell

Nutshell File

1:1
Fully supported

ArkCase 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

maps to

Nutshell

Nutshell Custom Field

1:1
Fully supported

ArkCase 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

maps to

Nutshell

Nutshell Tag

1:1
Fully supported

ArkCase 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

maps to

Nutshell

Custom Field on Deal

1:1
Fully supported

ArkCase 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

maps to

Nutshell

Nutshell User

1:1
Fully supported

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

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.

ArkCase logo

ArkCase gotchas

High

Custom BPMN workflows do not auto-migrate between instances

Medium

Time entries with inactive user references will fail import

Medium

FOIA request stage names vary by jurisdiction and require explicit mapping

Low

Open-source tier lacks a documented bulk API

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

  • ArkCase BPMN workflows do not migrate and require complete rebuild

    ArkCase runs BPMN 2.0 workflows — FOIA processing flows, ROI request flows, Data Privacy workflows, and any custom drag-and-drop automations your organization built. Nutshell has no workflow engine; it offers email sequences and basic lead-routing rules only. Any ArkCase workflow that routes cases through approval steps, assigns tasks based on conditions, or triggers notifications must be rebuilt from scratch using Nutshell's sequence tools or a third-party automation platform. FlitStack exports your ArkCase workflow definitions as structured documentation your admin can use as a rebuild reference.

  • ArkCase complaint and case files need manual routing to Nutshell Leads or Deals

    ArkCase Complaints and Case Files have no direct Nutshell equivalent — they sit between a CRM Lead and an Opportunity in concept. During planning, your team decides which objects become Nutshell Leads and which become Deals. A single ArkCase Case File type may split across both: active cases map to open Deals, historical closed cases map to closed-won Deals, and rejected cases map to archived Leads. This decision requires business input before field mapping begins. FlitStack surfaces the segmentation logic in the mapping plan so stakeholders can confirm before migration runs.

  • ArkCase document management features collapse to flat file attachments

    ArkCase ECM includes version control, check-in/check-out locking, annotation, redaction, folder hierarchies, and correspondence templates. Nutshell Files supports version history and basic linking but lacks hierarchical folders, annotation, redaction, and check-out locking. Migrated documents lose their ArkCase ECM metadata (lock status, annotation layer, version diff history). Files with ArkCase locked status are migrated unlocked. Correspondence templates export as plain-text notes. If ECM preservation is critical, your team should evaluate a separate ECM migration or post-migration re-upload of the ECM layer.

  • ArkCase custom objects with N:N relationships need custom field representation

    ArkCase custom objects can define many-to-many relationships using lookup configurations. Nutshell custom fields do not support junction-object relationships — they store flat key-value data. N:N custom object relationships from ArkCase surface as a comma-separated list in a Nutshell custom text field, or your admin can create a custom object in Nutshell and link it manually post-migration. FlitStack documents every N:N relationship encountered during discovery and presents options (flat field vs. manual rebuild) before migration.

  • ArkCase on-premise deployments require read-only database access for migration

    ArkCase can be deployed on-premise or in a private cloud with database access behind your firewall. Nutshell is multi-tenant SaaS. If your ArkCase instance runs on-premise, FlitStack needs read-only database credentials (or API access with full export permissions) to extract People, Organizations, Cases, Complaints, Tasks, and attachments. Your IT team must provision this access before migration planning begins. Cloud-hosted ArkCase instances use the REST API with standard rate-limit handling and pagination.

Migration approach

Six steps for a successful ArkCase to Nutshell data migration

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

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

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

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

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

Context on both ends of the pair

ArkCase logo

ArkCase

Source

Strengths

  • Open-source core with no per-record licensing, removing artificial data-caps on the free tier.
  • FedRAMP, HIPAA, and HITECH compliance certifications are pre-built, not add-ons, reducing compliance overhead for government and healthcare customers.
  • RESTful API and SDK are available on all tiers, including open source, enabling programmatic data access and integration.
  • BPMN 2.0 workflow engine ships with out-of-the-box templates for FOIA, ROI, and data-privacy processes.
  • Multi-language localisation (English, French, Italian, German, Spanish) is included across all tiers.

Weaknesses

  • High-availability clustering and the full analytics module are gated behind Enterprise Gold pricing, not available on the open-source tier.
  • No native bulk-export or bulk-import UI — large-volume data movement requires API scripting or professional services engagement.
  • The open-source tier offers only online-documentation support, with no named support engineer or SLA on the free plan.
  • Medical OCR/NLP AI and audio/video transcription engines are Platinum-tier exclusives, not available on Enterprise Gold.
  • Pricing beyond named-user tiers involves custom quotes and volume discounts that are not publicly standardised, complicating budget forecasting.
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. 1 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 ArkCase and Nutshell.

  • Object compatibility

    B

    1 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

    ArkCase: Not publicly documented for any tier.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Most ArkCase-to-Nutshell migrations complete in 48–72 hours of clock time for under 50,000 records. The longest planning step is routing ArkCase complaints and cases to Nutshell Leads and Deals — that decision requires stakeholder input and can extend discovery by a few days. Larger setups with 500,000+ records or heavy custom-object schemas extend to 5–7 days. On-premise ArkCase deployments require IT provisioning for database access before discovery begins.

Adjacent paths

Related migrations to explore

Ready when you are

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