CRM migration
Field-level mapping, validation, and rollback between LegalServer and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
LegalServer
Source
Nutshell
Destination
Compatibility
11 of 12
objects map 1:1 between LegalServer and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
LegalServer organizes data around Cases, Matters, Grants, and Contractor relationships for legal aid and public defender organizations. Nutshell operates as a standard CRM with People, Companies, Leads, and Deals as its core objects. These models diverge significantly: LegalServer's hierarchical case-matters-grants structure has no direct Nutshell equivalent, and LegalServer's custom field system (Admin > Custom Field Management) allows unlimited field creation per module, while Nutshell supports custom fields on People, Companies, and Leads with type constraints. We map LegalServer contacts and organizations to Nutshell People and Companies with direct field correspondence where names align. LegalServer case records migrate as Nutshell Deals, with the case number, status, and key case-type metadata stored as custom fields. Grant balances and billing types from LegalServer's grant management module surface as custom numeric fields on the linked Deal record — preserving the financial snapshot without recreating LegalServer's billing logic. LegalServer's v2 API returns a maximum of 100 results per request, requiring pagination logic across all object types during extraction. We handle this automatically and preserve the original create and modify timestamps from LegalServer's UUID-tracked records. Automations, workflows, document templates, and process configurations in LegalServer do not migrate — we export your LegalServer process definitions as a rebuild reference for Nutshell's automation tools.
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 LegalServer 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.
LegalServer
Contact (Person)
Nutshell
People
1:1LegalServer's person-level contact records map directly to Nutshell People. Standard name fields including first name, last name, email address, phone numbers, and postal address components correspond one-to-one between platforms. The primary organization link stored in LegalServer maps to a Company lookup field in Nutshell, preserving the relationship between individuals and their affiliated organizations. Any additional contact metadata beyond the core fields migrates as custom fields on the People record.
LegalServer
Organization
Nutshell
Company
1:1LegalServer organizations transfer directly to Nutshell Companies with matching field names where possible. Organization name, physical address components, website URL, and industry classification align without transformation. Parent-child hierarchies from LegalServer can be preserved using Nutshell's company relationship fields or linked via custom fields, depending on hierarchy complexity. Multi-office organizations with distinct LegalServer accounts must be merged prior to migration.
LegalServer
Case / Matter
Nutshell
Deal
1:1LegalServer cases have no direct Nutshell equivalent. We map each case to a Nutshell Deal, storing the case number as a custom text field (Case_Number__c), case status as a custom dropdown, and case type as a custom field. The Deal name uses the case number plus primary client name for identification.
LegalServer
Grant / Grant Balance
Nutshell
Custom Fields on Deal
1:1LegalServer grant records contain funding source, billing type (Flat Hourly Rate or Variable Hourly Rate), and remaining balance. These migrate as custom numeric and dropdown fields on the associated Nutshell Deal record. We preserve the grant balance snapshot at migration time — ongoing grant tracking requires Nutshell's reporting tools post-migration.
LegalServer
Contractor
Nutshell
People + Custom Fields
1:1LegalServer contractors (individual or organization) map to Nutshell People or Companies depending on the contractor type. Contractor attributes (subject matter expertise, languages, fee structure) migrate as custom fields. Work orders and vouchers map to custom fields on the associated Deal.
LegalServer
Timekeeping / Timeslip
Nutshell
Activity + Custom Fields on Deal
1:1LegalServer time entries linked to cases migrate as Nutshell Activity records (Tasks) with the hours, date, and staff member preserved as custom fields. We attach activities to the corresponding Deal record so billable hours are visible in context. Duration converts from LegalServer hours to Nutshell minutes during the field-level mapping. The billable flag from LegalServer becomes a custom checkbox on the Task. Unlinked time entries are attached to the primary Deal identified during scoping.
LegalServer
Outreach
Nutshell
Activity (Task)
1:1LegalServer outreach records representing intake interactions, follow-up communications, and community outreach activities migrate as Nutshell Tasks. The outreach type, date, and outcome are preserved as fields on the Task. Each outreach record is associated with the relevant Person or Deal record in Nutshell based on the relationship stored in LegalServer.
LegalServer
Prescreen / Intake
Nutshell
Lead + Custom Fields
1:manyLegalServer prescreen records that did not result in an open case migrate as Nutshell Leads with status and outcome preserved as custom dropdown fields. Prescreen intake date, referral source, and eligibility determination migrate as custom fields on the Lead record. Cases that converted from prescreen to open case follow the Case-to-Deal mapping path instead, preserving the full case history from initial screening through closure.
LegalServer
User / Staff
Nutshell
User (Owner)
1:1LegalServer users are matched to Nutshell users by email address. Unmatched users are flagged before migration — organizations either invite them to Nutshell first or assign their records to a designated fallback owner. Role permissions do not migrate as Nutshell's permission model differs.
LegalServer
Document / Attachment
Nutshell
File Attachments on Record
1:1LegalServer documents attached to cases, contacts, or organizations are downloaded and re-uploaded to the corresponding Nutshell record (Person, Company, or Deal). File size limits and inline image handling follow Nutshell's attachment constraints. Documents not associated with a migrated record are linked to the primary case Deal.
LegalServer
Custom Lookup Lists
Nutshell
Custom Dropdown Fields
1:1LegalServer lookup lists (funding codes, case types, office assignments) map to Nutshell custom dropdown fields. Each unique lookup value requires explicit mapping. Values with no matching Nutshell dropdown option are flagged for admin review before the migration commits.
LegalServer
Formula Fields
Nutshell
Not Migrated
1:1LegalServer formula fields compute values automatically based on other field inputs, such as poverty level percentages calculated from household income and family size. Nutshell lacks a native formula field type, so calculated values migrate as static custom fields capturing the value at migration time. The underlying calculation logic does not transfer. Any fields relying on LegalServer formula behavior must be identified during discovery — organizations either accept static values or rebuild calculations using Nutshell reporting, integrations, or external tools after migration.
| LegalServer | Nutshell | Compatibility | |
|---|---|---|---|
| Contact (Person) | People1:1 | Fully supported | |
| Organization | Company1:1 | Fully supported | |
| Case / Matter | Deal1:1 | Fully supported | |
| Grant / Grant Balance | Custom Fields on Deal1:1 | Fully supported | |
| Contractor | People + Custom Fields1:1 | Fully supported | |
| Timekeeping / Timeslip | Activity + Custom Fields on Deal1:1 | Fully supported | |
| Outreach | Activity (Task)1:1 | Mapping required | |
| Prescreen / Intake | Lead + Custom Fields1:many | Fully supported | |
| User / Staff | User (Owner)1:1 | Fully supported | |
| Document / Attachment | File Attachments on Record1:1 | Fully supported | |
| Custom Lookup Lists | Custom Dropdown Fields1:1 | Fully supported | |
| Formula Fields | Not Migrated1: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.
LegalServer gotchas
Dynamic vs static contact record split
v2 API 100-record hard cap on all result sets
Custom fields on versioned subtables require exact path mapping
Grant billing types require pre-migration decision on deduction logic
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
Scope and map LegalServer objects to Nutshell counterparts
We extract a full schema inventory from LegalServer via the Core API — listing all custom fields, lookup lists, modules (Case Data, Outreach, Timekeeping, Contractor), and user accounts. We then produce an object-level mapping document that assigns each LegalServer module to its Nutshell equivalent (People, Company, Lead, Deal, or custom fields). Organizations review and approve the mapping, flag any lookup list consolidation needed, and confirm which historical cases to include versus archive.
Handle LegalServer multi-database merge and API pagination
If multiple LegalServer databases exist, we confirm that your team has merged them into a single source database before extraction begins. Our extraction layer then handles LegalServer's 100-result API pagination limit automatically — iterating through all pages for each object type, preserving original UUIDs and timestamps. For large organizations with hundreds of thousands of records, extraction runs in staged batches to avoid overloading the source API.
Resolve owner and user mappings by email
LegalServer user email addresses are matched against the Nutshell user list. Nutshell users must exist in the destination account before the migration runs — we flag any LegalServer users without a corresponding Nutshell account and ask your team to either create the Nutshell user or designate a fallback owner. Role-based permissions from LegalServer do not carry over; these are reconfigured in Nutshell's Roles and Teams settings post-migration.
Run a sample migration with field-level diff
A representative sample (typically 200–500 records spanning contacts, organizations, cases, and time entries) migrates into a Nutshell staging environment. We generate a field-level diff comparing source values against destination field values, highlighting any value-mapping gaps, truncated text fields, or missing dropdown options. Your team verifies the sample data in Nutshell before we commit to the full migration run. Any mapping adjustments are documented and applied before the production migration.
Execute full migration with delta-pickup window
The full migration runs against Nutshell's live environment using the validated mappings. A delta-pickup window (typically 24–48 hours after the initial load) captures any records created or modified in LegalServer during the cutover period. Audit logs record every record operation, and one-click rollback is available if reconciliation identifies unexpected gaps. After delta-pickup closes, LegalServer read access is revoked and the migration is considered complete.
Deliver export of LegalServer process definitions for Nutshell rebuild
LegalServer workflows, automations, dynamic processes, and document templates do not migrate as data. We export your LegalServer process definitions — including workflow rules, form logic trees, and HotDocs document template configurations — as a structured reference document. This gives your Nutshell admin or implementation partner a rebuild blueprint for Nutshell's automation tools, sequences, and template system. Post-migration, we provide 30 days of reconciliation support for data gaps identified in the first data review cycle.
Platform deep dives
LegalServer
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 3 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 LegalServer and Nutshell.
Object compatibility
3 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
LegalServer: Not publicly documented; v2 APIs enforce a 100-result hard cap per request regardless of page size.
Data volume sensitivity
LegalServer 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 LegalServer to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your LegalServer 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 LegalServer
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.