CRM migration
Field-level mapping, validation, and rollback between Lawmatics and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Lawmatics
Source
Nutshell
Destination
Compatibility
10 of 12
objects map 1:1 between Lawmatics and Nutshell.
Complexity
CModerate
Timeline
48–72 hours
Overview
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.
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 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
Nutshell
Person
1:1Lawmatics 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)
Nutshell
Lead
1:manyLawmatics 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)
Nutshell
Person + Opportunity
many:1Lawmatics 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)
Nutshell
Lead (Closed Won/Lost stage)
1:1Closed 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
Nutshell
Company
1:1Lawmatics 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)
Nutshell
Event
1:1Lawmatics 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
Nutshell
Note
1:1Lawmatics 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
Nutshell
Task
1:1Lawmatics 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)
Nutshell
Custom Field (Person type)
1:1Every 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)
Nutshell
Custom Field (Lead type) + Custom Field (Person type)
1:1Lawmatics 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
Nutshell
File (URL reference or re-upload)
1:1Lawmatics 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
Nutshell
None (no equivalent)
1:1Lawmatics 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.
| Lawmatics | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | Person1:1 | Fully supported | |
| Matter (status = Active Prospect / Lead) | Lead1:many | Fully supported | |
| Matter (status = Client) | Person + Opportunitymany:1 | Fully supported | |
| Matter (status = Closed Won / Closed Lost) | Lead (Closed Won/Lost stage)1:1 | Fully supported | |
| Company | Company1:1 | Fully supported | |
| Event (Appointment) | Event1:1 | Fully supported | |
| Note | Note1:1 | Fully supported | |
| Task | Task1:1 | Fully supported | |
| Custom Field (Contact-scoped) | Custom Field (Person type)1:1 | Fully supported | |
| Custom Field (Matter-scoped) | Custom Field (Lead type) + Custom Field (Person type)1:1 | Fully supported | |
| File / Attachment | File (URL reference or re-upload)1:1 | Fully supported | |
| Workflow Automation | None (no equivalent)1: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.
Lawmatics gotchas
Matter vs. Contact export schema isolation
Time and billing add-on gating
Contact tier limits affect migration scoping
Automations are not data objects
API rate limits not publicly documented
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
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.
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.
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.
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.
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
Lawmatics
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Moderate CRM migration. 4 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Moderate migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Lawmatics and Nutshell.
Object compatibility
4 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
Lawmatics: Not publicly documented.
Data volume sensitivity
Lawmatics 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 Lawmatics to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Lawmatics 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 Lawmatics
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.