Migrate from Case.one to Nutshell

Case.one people map directly to Nutshell Person records. The primary email, phone, address, and custom properties transfer to Nutshell's standard and custom Person fields. A Company must exist in Nutshell before a Person with a primary company can be linked.

Case.one companies map 1:1 to Nutshell Company records. Company name, website, industry, address, employee count, and revenue transfer to Nutshell's standard fields. The full address is concatenated into a single address string. Custom properties from Case.one move to Nutshell custom fields on the Company record. A CaseOne_ID__c field preserves the source system identifier for reconciliation.

Nutshell has no native case or matter object. Each Case.one case becomes a set of custom fields on the primary Person record (case number, status, priority, description, type). If multiple parties exist for one case, each party Person record references the same case number via a shared custom field.

Case.one supports multiple parties per case (attorney, client, opposing counsel). Nutshell Person-to-Company is 1:N per Person. We create a separate Person record for each case party and use a Party_Role__c custom field to store the role label. Role-to-role reporting requires a custom filter or export.

Case.one links companies to cases. In Nutshell, the Person record's primary Company lookup links the party to its organization. If a person represents multiple companies in Case.one, we set the most-recently-used as the primary and surface others in a custom notes field.

Case.one time entries are structured records with date, duration, description, and billable flag, nested inside cases. Nutshell has no time-entry object. We serialize all time entries per Person as a JSON array in a Time_Entries_JSON__c custom text area field. Each entry is individually readable but not queryable in Nutshell's standard reports.

Case.one documents attach to cases. In Nutshell, Files attach to Person or Company records. We re-upload each document to the primary Person record and use a file naming convention (e.g., [Case-2024-001] Contract Draft.pdf) to preserve case context in the absence of case folders.

Case.one generates invoices tied to cases and time entries. Nutshell has no native billing object. Bills and line items are not migrated. Clients who need billing post-migration must use a dedicated accounting tool. We can export bill records as a CSV reference file for import into QuickBooks, Clio, or another billing platform.

Case.one allows custom properties on people. Each custom property in Case.one maps to a Nutshell custom field on the Person record. Nutshell's per-account limit is 100 custom fields total across all entities — we check the count during scoping and consolidate low-value fields into a text block if needed.

Case.one custom properties on companies transfer to Nutshell Company custom fields. The same 100-field account ceiling applies across all entity types. Custom fields that store large text blobs (e.g., case notes or lengthy descriptions) are consolidated into a single long-text area field rather than individual fields to conserve the field allotment.

Case.one users (attorneys, paralegals, admins) may appear as Person records. Nutshell user accounts are separate from Person records. We match Case.one users by email to existing or new Nutshell user accounts and link the corresponding Person record. Unmatched users are flagged before migration.

Case.one activity logs and notes are stored per person or per case. Nutshell has no universal activity log per Person equivalent to Case.one's log. We concatenate all notes chronologically into a single Notes_Audit_Log__c text area on the Person record. Individual note timestamps are preserved in the text.