CRM migration

Migrate from Lawmatics to Nutshell

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

Lawmatics logo

Lawmatics

Source

Nutshell

Destination

Nutshell logo

Compatibility

83%

10 of 12

objects map 1:1 between Lawmatics and Nutshell.

Complexity

CModerate

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Lawmatics organizes data around Contacts, Companies, and Matters (prospects, clients, and closed cases), with legal-specific automations for intake, e-signature, SMS, and marketing that go well beyond standard CRM territory. Nutshell targets SMB sales teams with People, Companies, Leads, and a sales pipeline — its native pipeline stages are built for deal progression, not legal case lifecycles. The migration carries every Contact, Company, and Matter into Nutshell's equivalent objects using Lawmatics' REST API, with the Matter type field routing records into Nutshell Leads or Contacts depending on the matter status at migration time. Custom fields on every object type are exported in bulk and recreated as Nutshell custom fields (Company, Person, or Lead type) before data lands. Legal automations — intake forms, SMS triggers, engagement workflows, e-signature sequences — do not have a Nutshell equivalent; we export the automation definitions as JSON so your team can rebuild the logic in Nutshell's automation builder or an external tool. The API-based migration runs in read-only scope on Lawmatics, so your team keeps working during cutover, and a 24–48 hour delta window captures any records modified between the bulk extract and go-live.

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

Lawmatics logo

Lawmatics

What's pushing teams away

  • Frequent UI changes alter automation node placement and workflow builder navigation, creating friction for users who have built muscle memory.
  • SMS feature lacks message history and filtering options, forcing staff to manage conversations outside the platform.
  • Time and billing is a separate paid add-on at $29 per user per month, so firms expecting it included feel a billing surprise.
  • Clunky interface compared to more modern CRMs, especially when managing large contact lists or building complex automations.
  • Contact export isolates contact-type fields from matter-type fields, so pulling a complete client picture requires two separate exports.

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 Lawmatics objects map to Nutshell

Each row shows how a Lawmatics 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.

Lawmatics

Contact

maps to

Nutshell

Person

1:1
Fully supported

Lawmatics Contacts map 1:1 to Nutshell People using a direct field-to-field translation for all standard properties. Name fields, email addresses, phone numbers, physical address components, job title, and any custom contact properties transfer completely. The migration preserves the original Lawmatics contact ID as a custom field on the Nutshell Person for reconciliation purposes, and each Nutshell Person can be associated with a Company record via the 'Works for' link.

Lawmatics

Matter (status = Active Prospect / Lead)

maps to

Nutshell

Lead

1:many
Fully supported

Lawmatics Matters with status values indicating a prospect (not yet a client) route to Nutshell Leads. The Matter title becomes the Lead name, and the primary contact links to the corresponding Person record. Practice area and intake source map to Nutshell custom Lead fields. Legal-specific metadata like referral source and originating campaign are preserved as custom fields on the Lead.

Lawmatics

Matter (status = Client)

maps to

Nutshell

Person + Opportunity

many:1
Fully supported

Lawmatics Matters marked as 'Client' migrate the contact data to a Nutshell Person, and the matter itself becomes a Nutshell Opportunity representing the active case or project. The Opportunity name uses the Matter title, and the original matter type field is preserved as a custom field. Billing rate, practice area, and client-specific matter properties map to custom fields on the Opportunity.

Lawmatics

Matter (status = Closed Won / Closed Lost)

maps to

Nutshell

Lead (Closed Won/Lost stage)

1:1
Fully supported

Closed Matters from Lawmatics migrate to Nutshell Leads with the stage set to 'Closed Won' or 'Closed Lost' based on the Matter's outcome status. The original matter-closed date and closure reason are stored in Nutshell custom fields on the Lead record for historical reporting continuity. Settlement amounts or case values map to a custom currency field if present.

Lawmatics

Company

maps to

Nutshell

Company

1:1
Fully supported

Lawmatics Companies map directly to Nutshell Companies with a field-by-field transfer for all standard properties. Domain and website URL, industry classification, physical address, and employee count all transfer. Companies that have multiple associated Contacts in Lawmatics create one Nutshell Company record, with all related contacts linked via the 'Works for' association in Nutshell.

Lawmatics

Event (Appointment)

maps to

Nutshell

Event

1:1
Fully supported

Lawmatics Events representing appointments migrate as Nutshell Events with all standard fields preserved. Event type (consultation, signing, court date, intake call) is mapped to a custom Event field in Nutshell if the standard type does not capture the distinction. The event owner is resolved by matching the Lawmatics owner email to a Nutshell user account before migration.

Lawmatics

Note

maps to

Nutshell

Note

1:1
Fully supported

Lawmatics Notes attach to the source record (Contact, Company, or Matter) and migrate as Nutshell Notes with the same body text and creation timestamps preserved. Rich-text formatting in Lawmatics notes (bold, bullets, links) is preserved as HTML in Nutshell, maintaining readability. Author attribution is resolved by email match to Nutshell users.

Lawmatics

Task

maps to

Nutshell

Task

1:1
Fully supported

Lawmatics Tasks map to Nutshell Tasks with subject line, full description text, due date, and completion status all preserved during migration. Task status values in Lawmatics (Open, Completed, Cancelled) map directly to Nutshell's task status values. Tasks without a due date in Lawmatics migrate as open tasks in Nutshell.

Lawmatics

Custom Field (Contact-scoped)

maps to

Nutshell

Custom Field (Person type)

1:1
Fully supported

Every custom field defined on Lawmatics Contacts requires a corresponding custom field created in Nutshell's Person settings before migration begins. The Nutshell custom field type is matched to the Lawmatics field type (text, number, date, or picklist) at creation time. Picklist values from Lawmatics are recreated as choices in the Nutshell field configuration, and values are mapped row-by-row during the data load.

Lawmatics

Custom Field (Matter-scoped)

maps to

Nutshell

Custom Field (Lead type) + Custom Field (Person type)

1:1
Fully supported

Lawmatics Matter custom fields are split between Nutshell Lead custom fields (for prospect metadata and open case properties) and Person custom fields (for client-specific data on closed matters). Fields that apply to both record types are created in both Nutshell scopes to ensure complete data preservation. The migration script maps each Matter custom field to the appropriate Nutshell custom field based on the field name and the target object.

Lawmatics

File / Attachment

maps to

Nutshell

File (URL reference or re-upload)

1:1
Fully supported

Lawmatics files and attachments associated with Contacts, Companies, and Matters are downloaded from Lawmatics storage and re-uploaded to Nutshell's file storage during migration. Files under 25MB migrate automatically. Files exceeding Nutshell's size threshold are flagged before the migration run and require manual re-upload after go-live, with the original Lawmatics file URLs preserved in a custom field for reference.

Lawmatics

Workflow Automation

maps to

Nutshell

None (no equivalent)

1:1
Fully supported

Lawmatics automations including intake form triggers, SMS sequences, email drip campaigns, e-signature workflows, and round-robin assignment rules have no direct Nutshell equivalent. The migration exports all automation definitions as a structured JSON file documenting each automation's triggers, conditions, and actions in detail. This file serves as a rebuild guide for your team to reconstruct the logic in Nutshell Pro's automation builder or a third-party integration tool.

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.

Lawmatics logo

Lawmatics gotchas

High

Matter vs. Contact export schema isolation

High

Time and billing add-on gating

Medium

Contact tier limits affect migration scoping

Medium

Automations are not data objects

Low

API rate limits not publicly documented

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

  • Matter status routing requires a value-by-value map before data can land in Nutshell Leads

    Lawmatics Matter records carry a status field with legal-case values (New, In Progress, On Hold, Client, Closed Won, Closed Lost) that don't map automatically to Nutshell's Lead object. Nutshell Leads use a simpler status model (New, Working, Closed Won, Closed Lost) with optional custom stage pipelines on Pro+ plans. We build a value-mapping table during the planning phase so each Lawmatics Matter status routes to the correct Nutshell Lead status or Opportunity stage. The practice_area and matter_type fields that define legal workflow logic have no Nutshell equivalent — they become custom Lead fields and your team will need to configure filters or reporting views that reference them after go-live.

  • Lawmatics intake automations and e-signature workflows have no Nutshell counterpart

    Lawmatics Premium and Enterprise tiers include intake form triggers, SMS follow-up sequences, e-signature workflows, and engagement automations that are deeply embedded in the Matter lifecycle. Nutshell Pro offers lead-stage email sequences and task triggers, but it has no native intake form builder, no DocuSign/RightSignature integration embedded in the object lifecycle, and no SMS automation. The automation definitions in Lawmatics (triggers, conditions, actions) are exported as a structured JSON document so your team has a reference guide when rebuilding workflows in Nutshell Pro's automation builder or a third-party tool like Zapier. This is always a manual rebuild step.

  • Lawmatics' contact-based custom fields require per-object recreation in Nutshell

    Lawmatics custom fields on Contacts, Companies, and Matters are managed globally in Settings and can be assigned to any form or object context. Nutshell separates custom field definitions by object type — a custom field for 'Date of Incident' must be created separately under the Person, Company, and Lead scopes if you want it available on all three. We create the Nutshell custom fields before data loads, but Nutshell's field creation UI requires manual definition of the field type and picklist values per scope. Firms with 30+ custom fields should expect a 2–3 hour setup session per Nutshell scope (Person, Company, Lead) before migration validation can run.

  • Nutshell's API requires impersonation permissions for user-owned records

    The Nutshell JSON-RPC API supports impersonation — an API key can act on behalf of any Nutshell user by passing their email as the username. However, if impersonation is disabled on your Nutshell account (a setting controlled by the account administrator), API writes are attributed to the API key itself rather than the individual user, and Nutshell's activity log records the key name instead of the owner's name. We require impersonation to be enabled and verified before the migration run so that Lawmatics owner assignments resolve correctly to Nutshell users and the activity history reflects the right team members.

  • Files and attachments larger than Nutshell's size limit require manual re-upload

    Lawmatics stores files and attachments on Contacts, Companies, and Matters, including intake documents, signed engagement agreements, and evidence uploads. Nutshell stores files as attachments on records, and large file uploads may be subject to storage limits depending on your Nutshell plan tier. Files over 25MB in Lawmatics are flagged before migration and require manual re-upload to Nutshell after go-live, with the original file URLs preserved in a custom field for reference. Firms with heavy document archives should budget for a manual document migration step post cutover.

Migration approach

Six steps for a successful Lawmatics to Nutshell data migration

  1. Audit Lawmatics data and build the migration schema

    We extract a full data snapshot from Lawmatics via the REST API, pulling all Contacts, Companies, Matters, Events, Notes, Tasks, and custom field definitions in parallel. Our team reviews the Matter status distribution, counts distinct custom field names across all scopes, and identifies any inactive or duplicate records. The output is a migration schema document that maps every Lawmatics field to its Nutshell target, including the Matter-status value-mapping table and a list of Nutshell custom fields to create before data lands. This step typically takes 1–2 business days.

  2. Create Nutshell custom fields per object scope

    Before any data loads, we create every required Nutshell custom field under the correct object scope (Person, Company, Lead, or Event). For picklist fields, the choices are recreated from Lawmatics' field configuration. For date and number fields, the type is matched exactly. We verify each field appears in the Nutshell UI under the right record type before proceeding. This step requires a Nutshell admin login and typically takes 2–4 hours per scope depending on field count.

  3. Run a sample migration with field-level diff

    A representative slice — typically 100–300 records across Contacts, Companies, and Matters — migrates first into your live Nutshell account. We generate a field-level diff comparing the Lawmatics source values against the Nutshell target values for every mapped field, flagging any truncation (e.g., text fields exceeding Nutshell character limits), missing picklist values, and failed lookups. You review the diff and approve the mapping before the full run commits. This step validates the entire field mapping and value-mapping table.

  4. Execute the full migration with delta-pickup window

    The full record set migrates in API batches, starting with Companies (since Nutshell People can link to Companies), then Contacts, then Matters routing to Leads or Person+Opportunity based on the status map. Events, Notes, and Tasks attach to their parent records. After the bulk load completes, a delta-pickup window of 24–48 hours captures any records created or modified in Lawmatics during the cutover. An audit log records every operation, and a reconciliation report compares record counts and field-population rates against the source snapshot.

  5. Deliver automation export and post-migration handoff

    We export all Lawmatics automation definitions as a structured JSON file documenting each automation's triggers, conditions, and actions. This file is handed off with a rebuild guide that maps Lawmatics automation concepts to Nutshell Pro's automation builder. If reconciliation identifies any records that failed to migrate or have missing fields, we correct and re-load those records. One-click rollback is available within 48 hours of the full run if critical data integrity issues surface during your team's post-migration review.

Platform deep dives

Context on both ends of the pair

Lawmatics logo

Lawmatics

Source

Strengths

  • Specialized legal automation covering lead scoring, follow-up sequencing, and appointment scheduling out of the box.
  • All-in-one platform combining CRM, intake, marketing, SMS, and time tracking in a single vendor relationship.
  • Generous contact limits on Premium (10,000) compared to the Essential tier (500), supporting mid-size firm growth.
  • Structured onboarding program with dedicated build calls and a guided checklist reduces time-to-value.
  • Live Zoom support hours every weekday provide direct access to Lawmatics staff for troubleshooting.

Weaknesses

  • Frequent UI changes disrupt established workflows, particularly in the automation builder node interface.
  • Contact export isolates contact fields from matter fields, requiring manual reconciliation for a complete client picture.
  • SMS feature lacks message history and basic filtering, limiting its usefulness for ongoing client conversations.
  • Time and billing is a separate paid add-on, not included in any core tier.
  • Interface feels dated compared to more modern CRM platforms, especially when managing large contact databases.
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?

Moderate CRM migration. 4 of 8 objects need a mapping; the rest are 1:1.

C

Overall complexity

Moderate migration

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

  • Object compatibility

    C

    4 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

    Lawmatics: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

Estimate your Lawmatics 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 Lawmatics to Nutshell data migrations

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

Can't find your answer?

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

Book a free 30 minute consultation

Most Lawmatics-to-Nutshell migrations complete in 48–72 hours for under 50,000 records. The longest step is the planning phase — building the Matter-status value map and creating Nutshell custom fields per scope can take 1–3 days before any data moves. Larger setups with 500,000+ records or extensive custom field sets extend to 5–7 days. Nutshell's flat object model (People, Companies, Leads) keeps the actual data load faster than migrations to platforms with record types or complex hierarchies.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Lawmatics.
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