Migrate from Lawcus to Nutshell

Lawcus contacts map directly to Nutshell People. Lawcus stores name, email, phone, address, company association, and custom properties. All standard fields move 1:1. Lawcus contact type (client vs. lead) maps via a value-mapping table to Nutshell Lead status or a custom field on the Person record.

Lawcus leads map to Nutshell Leads with direct field translation on status, source, rating, and owner. The Lawcus lead status pick-list values map to Nutshell Lead status values via a value-mapping table. Unmatched lead owners resolve by email to Nutshell user accounts before migration commits.

Lawcus companies map to Nutshell Organizations. Standard fields (name, address, phone, website, industry) translate directly. Lawcus parent-child company relationships map to Nutshell Organization.parent_id where the destination supports it. Organizations are migrated before People so that the organization lookup resolves correctly on person records.

Lawcus matters are the primary structural mismatch in this migration. A matter carries legal-case metadata (practice area, matter type, open/close dates, responsible attorney, billing arrangement) that does not have a direct Nutshell equivalent. We map matter.name → Deal.name, matter.number → Deal.reference_number, and matter.amount → Deal.value. Practice area, matter type, and custom legal fields become Nutshell custom fields on the Deal record.

Nutshell has no native concept of legal practice areas. Lawcus practice areas (e.g., Family Law, Corporate, Litigation) are preserved as a custom pick-list field on Nutshell Deals called Practice_Area__c. Your migration plan includes the value-mapping from Lawcus practice area values to the Nutshell custom field options.

Lawcus tasks, interactions, and activity history map to Nutshell Activities with original timestamps and assigned owners preserved. Activity type (call, email, meeting, note) maps to the corresponding Nutshell activity type. Activity.subject and activity.description carry over intact. Notes migrate as Nutshell Notes linked to the respective person or deal record.

Lawcus workflow rules (triggers, conditions, multi-step actions across tasks, emails, documents, and billing events) are stored in Lawcus's own automation engine and have no equivalent in Nutshell. FlitStack exports the workflow definitions as a structured reference document so your Nutshell admin or integration consultant can rebuild the logic in Nutshell's automation tools or a connected platform like Zapier.

Lawcus custom fields on contacts, matters, leads, and other objects are mapped to Nutshell custom fields on the corresponding Nutshell entity. Nutshell supports custom fields on People, Organizations, and Leads. We create each destination custom field before the migration run and apply the source field values via the Nutshell API during import.

Lawcus file attachments associated with matters or contacts are downloaded and re-uploaded as attachments to the corresponding Nutshell Deal or Person record. File size limits and attachment behavior follow Nutshell's standard file handling. Inline images in Lawcus notes are extracted and rehosted as Nutshell note attachments.

Lawcus user records (attorneys, staff, matter owners) are resolved to Nutshell user accounts by email address match. Any Lawcus owner whose email does not correspond to a Nutshell user is flagged before migration so your team can either invite them to Nutshell or reassign their records to an existing user before the full run.

Lawcus invoices, trust accounting entries, and billing records are legal-specific financial objects with no equivalent in Nutshell's data model. Nutshell has no native billing or accounting capability. We export a full financial record backup from Lawcus for import into your accounting platform of choice (such as QuickBooks, which Nutshell integrates with natively).