CRM migration
Field-level mapping, validation, and rollback between Lexis Affinity and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Lexis Affinity
Source
Nutshell
Destination
Compatibility
11 of 11
objects map 1:1 between Lexis Affinity and Nutshell.
Complexity
BStandard
Timeline
7–14 days
Overview
Lexis Affinity is a legal practice-management platform — its core objects are Persons, Organizations, Matters (cases), Time Entries, Invoices, and Trust Accounts. Nutshell is a conventional CRM with People, Companies, Leads, Deals, and Activities as its primary objects, plus custom fields for Company, Person, and Lead records. The two platforms share a contact model (Person/People ≈ Contact/Lead), an organization model (Organization/Company ≈ Account), and basic activity tracking — but Lexis Affinity's legal-specific layers (matters, billing arrangements, trust-ledger entries, conflict checks, document DataForms) have no native Nutshell equivalent and require custom fields, custom entities, or manual re-creation. FlitStack AI extracts Lexis Affinity data via the platform's available export paths (CSV, API where supported), maps Persons to Nutshell People, Organizations to Nutshell Companies, and Matters into a hybrid of Leads/Deals plus custom fields keyed to Matter Number and Responsible Attorney. Time entries and billing histories migrate as custom fields on the related Person or Lead record. Trust-account data — a high-sensitivity legal construct — is preserved as a reference custom field since Nutshell has no native trust-ledger module. Workflows, conflict-check rules, and document-automation logic do not migrate. These must be rebuilt in Nutshell's Triggers and Automations or documented via a FlitStack workflow-export deliverable for your Nutshell admin to reference during rebuild.
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 Lexis Affinity 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.
Lexis Affinity
Person
Nutshell
People
1:1Lexis Affinity Persons map 1:1 to Nutshell People records. Name, email, phone, address, and title fields transfer directly without transformation. Any custom properties stored on a Person record in Lexis Affinity — such as bar number, practice group, or licensing jurisdiction — become Nutshell custom fields on the corresponding Person record. Primary and secondary contact roles are preserved via Nutshell's contact-type designations.
Lexis Affinity
Organization
Nutshell
Company
1:1Lexis Affinity Organizations map directly to Nutshell Companies. Organization name, website, address, phone, and industry classification fields carry over without transformation. Parent-child organization hierarchies defined in Lexis Affinity become Nutshell Company parent-link relationships, which must resolve in the correct migration order to maintain referential integrity between related organizational entities.
Lexis Affinity
Matter
Nutshell
Lead + Custom Fields
1:1Matters are a legal construct with no native Nutshell equivalent. We map Matter data to a hybrid: the matter name and client link create a Nutshell Lead record, and matter-specific fields (Matter Number, Responsible Attorney, Billing Arrangement, Open Date, Close Date, Status) become custom fields on that Lead so the full matter context is preserved.
Lexis Affinity
Matter Contact Role
Nutshell
Lead Contact Association
1:1When a Lexis Affinity Person has a role on a Matter (e.g., Opposing Counsel, Expert Witness), that role is captured as a custom field or note on the Lead record in Nutshell. The primary client Person links directly to the Lead via Nutshell's person association.
Lexis Affinity
DataForm (matter metadata)
Nutshell
Custom Fields on Lead / Person
1:1Lexis Affinity DataForms capture structured matter metadata (court jurisdiction, case type, statutory basis, etc.). Each DataForm field becomes a Nutshell custom field on the Lead or Person record depending on whether the field is matter-level or client-level. Nutshell supports text, numeric, date, and choice field types.
Lexis Affinity
Time Entry
Nutshell
Task / Activity + Custom Fields
1:1Time entries (date, hours, description, billed status) transfer as Nutshell Tasks with the description in the task notes field and hours stored in a custom numeric field. Billed-status flags become a choice custom field so teams can filter unbilled entries without an external billing module.
Lexis Affinity
Invoice
Nutshell
Custom Fields on Lead / Person
1:1Nutshell has no native invoicing. Invoice Number, Invoice Amount, Invoice Date, and Invoice Status are stored as custom fields on the related Lead or Person record for reference. Firms needing full invoice history may need to export invoices as a separate CSV and attach it to the relevant record.
Lexis Affinity
Trust Account
Nutshell
Custom Fields on Company / Person
1:1Trust-account balances and account identifiers are preserved as reference custom fields on the Company or Person record. Nutshell has no trust-ledger module — for firms with active trust accounts, we recommend documenting the final trust balance separately and flagging the record with a trust-account-status custom field.
Lexis Affinity
Document / Attachment
Nutshell
Files on related record
1:1Documents attached to Persons, Organizations, or Matters in Lexis Affinity are downloaded and re-uploaded to the corresponding People, Company, or Lead record in Nutshell as Files. Nutshell's file storage architecture attaches documents to the relevant record type (Person, Company, or Lead) based on the source entity relationship. Nutshell's 25MB per-file limit applies to uploads; larger files are flagged for manual review and alternative handling during the migration process.
Lexis Affinity
Workflow / Automation
Nutshell
Not Migrated
1:1Lexis Affinity Workflow Builder automations encompass legal-specific triggers including conflict-check sequencing, matter-open notifications, document-filing rules, and court-deadline alerts. These workflow constructs have no Nutshell equivalent since Nutshell Triggers operate on stage-change and field-change events rather than legal-process logic. FlitStack AI exports all workflow definitions as a structured JSON reference document for your Nutshell administrator to use when rebuilding equivalent automations in Nutshell Triggers.
Lexis Affinity
Conflict Check Record
Nutshell
Note on Person / Company
1:1Conflict-check records and their outcomes are text data — we preserve the conflict-check result as a Note on the relevant Person or Company record in Nutshell. Nutshell has no native conflict-check module; firms with strict conflict requirements should evaluate Nutshell integrations with dedicated conflict-check tools post-migration.
| Lexis Affinity | Nutshell | Compatibility | |
|---|---|---|---|
| Person | People1:1 | Fully supported | |
| Organization | Company1:1 | Fully supported | |
| Matter | Lead + Custom Fields1:1 | Fully supported | |
| Matter Contact Role | Lead Contact Association1:1 | Fully supported | |
| DataForm (matter metadata) | Custom Fields on Lead / Person1:1 | Fully supported | |
| Time Entry | Task / Activity + Custom Fields1:1 | Fully supported | |
| Invoice | Custom Fields on Lead / Person1:1 | Fully supported | |
| Trust Account | Custom Fields on Company / Person1:1 | Fully supported | |
| Document / Attachment | Files on related record1:1 | Fully supported | |
| Workflow / Automation | Not Migrated1:1 | Fully supported | |
| Conflict Check Record | Note on Person / Company1: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.
Lexis Affinity gotchas
Records and Safe Custody module creates migration lock-in
DataForm custom field schemas are per-firm and must be reverse-engineered
Trust account sub-account types map differently to destination ledgers
Workflow automations do not export and must be rebuilt manually
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
Inventory Lexis Affinity export paths and validate record completeness
Before mapping begins, FlitStack AI inventories every data export path available in the Lexis Affinity instance — CSV exports for Persons and Organizations, SourceData API responses for structured matter fields, EzeScan output for documents, and manual exports for trust-account ledgers and invoices. We run row-count validation against the Lexis Affinity UI counts for each object to confirm export completeness. Any gaps are flagged and resolved with the firm's Lexis Affinity admin before field mapping starts.
Create Nutshell custom fields for legal-specific data
FlitStack AI provisions all required Nutshell custom fields before data loads begin. This includes Matter_Number__c, Billing_Arrangement__c, Matter_Open_Date__c, Matter_Close_Date__c, and Trust_Balance__c on the Lead object; Bar_Number__c and Practice_Group__c on the People object; and Trust_Account_Name__c on the Company object. We also configure value mappings for matter-status values (Open, Closed, Pending, On Hold) into Nutshell's Lead status pick-list so the migration maps cleanly without manual post-import cleanup.
Migrate People and Organizations before Matters
Nutshell requires Companies to exist before linking People to them, and People to exist before linking them to Leads. FlitStack AI sequences the migration: Organizations → Companies first, then Persons → People, then Matters → Leads with the People/Company links resolved via email matching and foreign-key lookups. This sequencing ensures every Lead has a populated ownerId and a linked Person record at the point of import.
Run sample migration with field-level diff across all object types
A representative sample — typically 100–300 records spanning People, Companies, Leads, and a sample of matter-specific custom fields — migrates first. We generate a field-level diff between the Lexis Affinity source and the Nutshell destination so you can verify that Matter_Number__c values transferred correctly, that responsible attorney email resolution produced a valid ownerId on each Lead, and that trust-account balance fields populated without truncation. The diff report is reviewed with you before the full migration commits.
Execute full migration with delta-pickup window
The full migration loads all validated records into Nutshell. A delta-pickup window (typically 24–48 hours) runs alongside the migration to capture any new Persons, updated matter statuses, or new time entries created in Lexis Affinity during the cutover window. All operations are logged in an audit trail, and one-click rollback is available if reconciliation numbers do not match within the tolerance threshold agreed upon before migration day.
Platform deep dives
Lexis Affinity
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 Lexis Affinity 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
Lexis Affinity: Not publicly documented for the practice management module; enterprise customers should confirm limits during onboarding.
Data volume sensitivity
Lexis Affinity 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 Lexis Affinity to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Lexis Affinity 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 Lexis Affinity
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.