CRM migration
Field-level mapping, validation, and rollback between Legal Workspace and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Legal Workspace
Source
Nutshell
Destination
Compatibility
11 of 11
objects map 1:1 between Legal Workspace and Nutshell.
Complexity
BStandard
Timeline
24–72 hours
Overview
Legal Workspace organizes legal practice data around matters, clients, contacts, and billing — a structure optimized for law firm workflow tracking. Nutshell is a CRM built around people, companies, leads, and deals with pipeline stages tied to sales cycles. FlitStack AI migrates Legal Workspace client records as Nutshell Companies, individual contacts as Nutshell People, and matters as Nutshell Deals with a custom matter-type field preserving the original matter classification. Time entries map to Nutshell Tasks; document file content cannot transfer but file name, type, and URL references migrate as custom fields. We do not migrate Legal Workspace workflows, document templates, billing templates, or matter-type automation rules — those must be rebuilt in Nutshell's automation tools. We extract from Legal Workspace via its REST export endpoints and load into Nutshell via the JSON-RPC API using Nutshell's field-type schema so custom fields land as the correct data type on the correct entity.
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 Legal Workspace 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.
Legal Workspace
Client
Nutshell
Company
1:1Legal Workspace client records map 1:1 to Nutshell Company records. Client name becomes Company name, and client address fields map to Nutshell's corresponding address fields. Parent-client hierarchies in Legal Workspace are preserved using Nutshell's parent-company reference field, maintaining organizational structure across the migration.
Legal Workspace
Contact
Nutshell
Person
1:1Individual contacts in Legal Workspace map directly to Nutshell Person records. Email, phone, title, and address fields carry over without transformation. Nutshell associates each Person with the corresponding Company record automatically by matching email domain or through explicit company assignment during migration.
Legal Workspace
Matter
Nutshell
Deal
1:1Legal Workspace matters map to Nutshell Deals. The matter name becomes the deal name. The linked client becomes the deal's associated Company. Matter type, status, responsible attorney, and billing rate are stored as Nutshell custom fields on the deal. Nutshell deal stage maps to a custom matter-status picklist so the original workflow state is preserved.
Legal Workspace
Time Entry
Nutshell
Task
1:1Nutshell has no native billing or time-tracking object, so Legal Workspace time entries migrate as Nutshell Tasks with a custom duration field (hours), a custom billing rate field, and a flag for billable or non-billable. Each Task is linked to the corresponding Deal (mattery) and the Person (attorney or staff) who logged the time.
Legal Workspace
Document metadata
Nutshell
Custom field (Deal)
1:1Legal Workspace document attachments include file name, MIME type, upload date, and uploader. The file binary cannot be stored in Nutshell. We migrate the document metadata as a custom text field on the deal (Matter_Documents__c) containing a newline-separated list of file names and upload timestamps. The source URLs are preserved for manual re-upload if needed.
Legal Workspace
User / Attorney
Nutshell
User
1:1Legal Workspace users (attorneys, paralegals, billing staff) are matched to Nutshell Users by email address. Nutshell's single-owner model means each matter-role (responsible attorney, lead attorney, billing attorney, paralegal) is stored in a separate custom field on the deal rather than as a native role assignment.
Legal Workspace
Matter Custom Fields
Nutshell
Custom fields on Deal
1:1Legal Workspace allows custom fields on matters. We create matching custom fields in Nutshell per the field type — picklist values become Nutshell picklist options, date fields become Nutshell date fields, and text fields become Nutshell text fields. The field label and help text are preserved.
Legal Workspace
Client Custom Fields
Nutshell
Custom fields on Company
1:1Client-level custom fields in Legal Workspace, such as client tier, intake source, or billing arrangement, are translated to Nutshell Company custom fields. The field type from Legal Workspace determines the target field type in Nutshell, with picklist values migrated verbatim to preserve data integrity across all client records.
Legal Workspace
Contact Custom Fields
Nutshell
Custom fields on Person
1:1Contact-level custom fields in Legal Workspace, such as bar number, practice area, or LinkedIn URL, are mapped to Nutshell Person custom fields. The field type from Legal Workspace determines the target field type in Nutshell, ensuring accurate data representation across the migrated contact records.
Legal Workspace
Workflow / Automation
Nutshell
None
1:1Legal Workspace workflows, matter automation rules, and notification triggers have no Nutshell equivalent. These must be rebuilt using Nutshell's automation features, including Tasks, email sequences, and platform integrations. We export workflow definitions as a structured reference document to support your rebuild, including rule names and trigger conditions.
Legal Workspace
Billing Templates / Rates
Nutshell
Custom fields on Deal
1:1Legal Workspace billing rate schedules and matter-specific rate overrides are stored as custom fields on the deal. Nutshell has no native billing engine, so these financial values are preserved as reference fields for your finance team to reconcile billing data outside Nutshell as needed.
| Legal Workspace | Nutshell | Compatibility | |
|---|---|---|---|
| Client | Company1:1 | Fully supported | |
| Contact | Person1:1 | Fully supported | |
| Matter | Deal1:1 | Fully supported | |
| Time Entry | Task1:1 | Fully supported | |
| Document metadata | Custom field (Deal)1:1 | Fully supported | |
| User / Attorney | User1:1 | Fully supported | |
| Matter Custom Fields | Custom fields on Deal1:1 | Fully supported | |
| Client Custom Fields | Custom fields on Company1:1 | Fully supported | |
| Contact Custom Fields | Custom fields on Person1:1 | Fully supported | |
| Workflow / Automation | None1:1 | Fully supported | |
| Billing Templates / Rates | Custom fields on Deal1: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.
Legal Workspace gotchas
Document templates and custom fields are configuration data, not matter data
Integrated timer entries and manual time records use different storage paths
No public API or developer portal
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
Extract Legal Workspace data via admin export
FlitStack AI authenticates against your Legal Workspace admin account using scoped read access to export all clients, contacts, matters, time entries, and document metadata. We pull the full schema first to capture custom field names, data types, and picklist values before the data extraction. The export runs in batches to avoid timeout errors and produces a structured JSON dataset organized by entity type. Your Legal Workspace account remains fully operational during this step — we use read-only endpoints only.
Map schema and create Nutshell custom fields
FlitStack AI analyzes the Legal Workspace export schema and maps each field to the appropriate Nutshell entity and field type. Custom fields that do not exist in Nutshell (matter_type, responsible_attorney, billing_rate, and others) are pre-created via the Nutshell API before the migration load begins. We configure picklist options, field labels, and help text to match Legal Workspace exactly. At this stage we also define the value-mapping table for matter status to Nutshell deal stage.
Resolve users and establish attorney-role fields
Legal Workspace user records are matched to Nutshell Users by email address. Any Legal Workspace user without a corresponding Nutshell account is flagged before migration so your team can provision accounts or assign a fallback owner. Multi-role attorney assignments are written to the custom fields on each deal (Responsible_Attorney__c, Billing_Attorney__c, Paralegal__c) rather than the Nutshell native owner field, which holds only one value per record.
Run sample migration with field-level diff
A representative sample — typically 100–500 records spanning clients, contacts, matters, and time entries — migrates into Nutshell first. FlitStack AI generates a field-level diff comparing source and destination values for every mapped field so you can verify that matter types, billing rates, and attorney assignments landed correctly before the full run. You review the sample in Nutshell and approve or request adjustments to the field mapping.
Execute full migration with delta-pickup and rollback
The full Legal Workspace dataset loads into Nutshell via the JSON-RPC API, sequenced so companies create before contacts, and contacts before matters. A delta-pickup window (24–48 hours) captures any new or modified records in Legal Workspace during cutover so Nutshell reflects your final state at go-live. FlitStack AI provides an audit log of every record operation and a one-click rollback that removes all migrated records if reconciliation fails. Document file metadata and workflow export are delivered as separate reference packages alongside the CRM migration.
Platform deep dives
Legal Workspace
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 Legal Workspace 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
Legal Workspace: Not publicly documented — typical SaaS limits assumed and confirmed during scoping.
Data volume sensitivity
Legal Workspace 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 Legal Workspace to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Legal Workspace 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 Legal Workspace
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.