CRM migration

Migrate from LegalServer to Nutshell

Field-level mapping, validation, and rollback between LegalServer and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.

LegalServer logo

LegalServer

Source

Nutshell

Destination

Nutshell logo

Compatibility

92%

11 of 12

objects map 1:1 between LegalServer and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

LegalServer logo

LegalServer

What's pushing teams away

  • Users consistently describe the interface as visually outdated and clunky — reviewers on Capterra note heavy reliance on dropdown triangles, a dated calendar system, and a layout that does not feel like a modern program.
  • The contact creation workflow has a documented pitfall where using the wrong button to add contacts to a case creates a static contact record instead of a dynamic one, requiring manual cleanup and support intervention.
  • The v2 Core API caps results at 100 records per request with no cursor or offset pagination, which creates slow extraction cycles for organizations with large case histories and limits bulk migration efficiency.

Choosing

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How LegalServer objects map to Nutshell

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)

maps to

Nutshell

People

1:1
Fully supported

LegalServer'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

maps to

Nutshell

Company

1:1
Fully supported

LegalServer 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

maps to

Nutshell

Deal

1:1
Fully supported

LegalServer 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

maps to

Nutshell

Custom Fields on Deal

1:1
Fully supported

LegalServer 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

maps to

Nutshell

People + Custom Fields

1:1
Fully supported

LegalServer 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

maps to

Nutshell

Activity + Custom Fields on Deal

1:1
Fully supported

LegalServer 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

maps to

Nutshell

Activity (Task)

1:1
Mapping required

LegalServer 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

maps to

Nutshell

Lead + Custom Fields

1:many
Fully supported

LegalServer 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

maps to

Nutshell

User (Owner)

1:1
Fully supported

LegalServer 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

maps to

Nutshell

File Attachments on Record

1:1
Fully supported

LegalServer 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

maps to

Nutshell

Custom Dropdown Fields

1:1
Fully supported

LegalServer 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

maps to

Nutshell

Not Migrated

1:1
Fully supported

LegalServer 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.

Gotchas + challenges

What specifically takes care here

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 logo

LegalServer gotchas

High

Dynamic vs static contact record split

High

v2 API 100-record hard cap on all result sets

Medium

Custom fields on versioned subtables require exact path mapping

Medium

Grant billing types require pre-migration decision on deduction logic

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Pair-specific challenges

  • LegalServer's API pagination cap forces multi-request extraction for large datasets

    LegalServer v2 APIs return a maximum of 100 results per request to prevent timeouts and standardize server load. Any object with more than 100 records requires paginated extraction using a continuation token or offset mechanism across multiple API calls. This affects Contacts, Organizations, Cases, and any custom module records. Our extraction layer handles this automatically by iterating through pages until all records are retrieved, but the source system's API behavior means large datasets take longer to extract than a simple bulk export would.

  • Grant management billing logic does not translate to Nutshell — only snapshots migrate

    LegalServer's Grant Management module tracks grant balances in real time, deducting amounts as timeslips are recorded against the grant. Nutshell has no equivalent grant tracking module. When migrating, we capture the grant balance snapshot and billing type as static custom fields on the associated Deal record, but ongoing grant balance updates cannot occur automatically in Nutshell. Organizations must rebuild grant balance tracking in Nutshell's reporting tools or a separate financial system after migration — grant billing logic cannot be carried over as automation.

  • Formula fields in LegalServer cannot migrate as calculated fields

    LegalServer supports formula fields that automatically calculate values based on other field inputs (e.g., poverty level percentage based on household income and family size). Nutshell does not have a native formula field type. We migrate the formula's calculated value as a static custom field at migration time, but the calculation logic is lost. Any fields that rely on LegalServer formula behavior must be identified during discovery and discussed — either the calculated value is preserved as-is or the formula must be rebuilt outside Nutshell.

  • Custom lookup lists require explicit value-by-value mapping to Nutshell dropdowns

    LegalServer lookup lists (funding codes, case types, office assignments, outcome codes) are defined per-site and can contain dozens or hundreds of values. Nutshell custom dropdown fields must enumerate all allowed values explicitly in the field configuration. During migration, we map each LegalServer lookup value to the corresponding Nutshell dropdown option. Values that do not have a matching Nutshell option are flagged as exceptions — organizations must decide whether to add missing values to Nutshell before migration or consolidate similar values during the mapping phase.

  • Multiple source databases must be merged before migration begins

    LegalServer requires that all source databases be consolidated into a single database before data can be exported for migration. Multiple databases may have conflicting records and undefined relationships that cause migration failures or produce duplicate data. Organizations running LegalServer across multiple offices or with separate databases must perform a pre-migration data merge. This is not handled by FlitStack AI — your team or a consultant must consolidate databases before our extraction phase begins.

Migration approach

Six steps for a successful LegalServer to Nutshell data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Context on both ends of the pair

LegalServer logo

LegalServer

Source

Strengths

  • Built-in grant management tools with billing type deduction logic for funder compliance reporting
  • Highly configurable dynamic processes, forms, and profiles without requiring technical skills
  • Online client intake and prescreen forms with rules-based triage and poverty level assessment
  • Active community support via site administrator listserv and free weekly trainings
  • No licensing fees or third-party app dependencies — fully hosted SaaS model

Weaknesses

  • Interface described as visually outdated with a clunky dropdown-heavy navigation pattern
  • v2 API caps all multi-record results at 100 with no cursor pagination, slowing bulk extraction
  • Dynamic Contact records require a two-step add-to-case workflow that creates friction for intake staff
  • Document templates must be manually recreated on each environment transition (demo to live)
  • No public pricing page — subscription tiers and per-user costs are opaque without a sales conversation
Nutshell logo

Nutshell

Destination

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Standard CRM migration. 3 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across LegalServer and Nutshell.

  • Object compatibility

    B

    3 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    LegalServer: Not publicly documented; v2 APIs enforce a 100-result hard cap per request regardless of page size.

  • Data volume sensitivity

    B

    LegalServer doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your LegalServer to Nutshell migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about LegalServer to Nutshell data migrations

Answers to the questions buyers ask most during LegalServer to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your LegalServer to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most LegalServer-to-Nutshell migrations complete within 48–72 hours of migration time for setups under 50,000 records. Larger organizations with 200,000+ records, multiple LegalServer modules (Grant Management, Contractor Module, custom case types), or extensive custom lookup lists extend to 5–10 days. The longest planning step is mapping LegalServer lookup lists and custom fields to Nutshell custom field configurations — this happens during scoping before extraction begins.

Adjacent paths

Related migrations to explore

Ready when you are

Move from LegalServer.
Land in Nutshell, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day