Migrate from RunSensible to Nutshell

RunSensible People map directly to Nutshell People. Fields like first name, last name, email, phone, and address transfer 1:1. Conflict-check metadata, client-portal access flags, and intake form responses are preserved as Nutshell custom fields since Nutshell has no native conflict-check or portal-access equivalent.

RunSensible People records flagged as prospective clients or intake leads route to Nutshell Leads. Active client People records route to Nutshell People. The split is determined by RunSensible's Person type or status field — we read the source value and assign the Nutshell record type accordingly during migration.

RunSensible Companies map 1:1 to Nutshell Companies. Company name, domain, industry, employee count, and annual revenue transfer as-is. Multi-contact associations (RunSensible allows N:N person-to-company links) are preserved by linking the primary contact to the Company record and surfacing additional associations in a custom field for manual cleanup.

RunSensible Matters are the core case container — they map to Nutshell Deals but require a schema transform. RunSensible's legal-stage values (Intake, Filed, Discovery, Trial, Closed) have no direct Nutshell equivalent, so they become a custom 'Matter_Stage__c' pick-list field on the Nutshell Deal. Amount, close date, owner, and associated contacts transfer to standard Nutshell Deal fields.

RunSensible legal-stage values (Intake, Filed, Discovery, Trial, Closed, etc.) require a custom pick-list field in Nutshell. We create Matter_Stage__c on the Deal object and map every source value by name. Stage-transition timestamps are preserved as Matter_Stage_Updated__c datetime fields for reporting continuity.

RunSensible Activities (calls, emails, meetings, notes) with original timestamps and owner assignments map to Nutshell Activities. The activity type field determines the Nutshell activity category. Note body content transfers as-is; rich-text formatting is preserved where RunSensible stores it. Activity attachments are re-linked to their parent records, and any inline images embedded in notes are extracted and rehosted as separate file attachments to maintain compatibility with Nutshell's storage model.

RunSensible conflict-check results (cleared, conflict found, review required) have no Nutshell equivalent. We migrate the result as a custom pick-list field (Conflict_Check_Status__c) on Nutshell Person so the data is available for reference even though Nutshell's workflow engine cannot trigger on it.

RunSensible tracks statute-of-limitations deadlines per matter. Nutshell has no native deadline-tracking for legal deadlines, so we migrate the date as a custom datetime field (Statute_of_Limitations__c) on the Nutshell Deal. Nutshell's task feature can be used manually to create reminders tied to this date.

RunSensible IOLTA trust-account balances have no Nutshell equivalent — Nutshell has no billing or accounting module. We preserve the balance as a custom currency field (IOLTA_Balance__c) on the Deal for reference, but the firm must use a dedicated legal accounting tool (Clio, Quickbooks, or similar) for live trust-account management post-migration.

RunSensible document templates and automated assembly configs cannot migrate to Nutshell because Nutshell has no document-assembly or e-signature template engine. We export the template structure and field mappings as a reference PDF for manual rebuild in a document automation tool post-migration.

RunSensible user records are matched to Nutshell users by email address. Active RunSensible users who do not have Nutshell accounts are flagged before migration — the team either provisions Nutshell seats or assigns those users' records to a fallback owner during the migration run.

RunSensible file attachments on Matters, People, or Companies are re-uploaded to Nutshell and linked to the corresponding record. File size limits per Nutshell apply (Nutshell supports standard attachment sizes via its API). Inline images in notes are extracted and rehosted as separate file attachments.