CRM migration

Migrate from Lexis Affinity to Nutshell

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

Lexis Affinity logo

Lexis Affinity

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

11 of 11

objects map 1:1 between Lexis Affinity and Nutshell.

Complexity

BStandard

Timeline

7–14 days

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

Lexis Affinity logo

Lexis Affinity

What's pushing teams away

  • High barriers to exit — particularly the Records/Safe Custody module creates significant data lock-in and migration complexity for departing firms.
  • Hourly consulting fees charged by LexisNexis for even minor data model questions or configuration requests, creating cost uncertainty during evaluation.
  • Perpetual license or long-term commitment expectations from LexisNexis make firms feel locked into the platform before fully evaluating fit.
  • Complex multi-module architecture means firms often pay for features they do not use, with pricing not transparent at the module level.
  • Steep learning curve and bespoke training requirements create friction during onboarding and slow time-to-value.

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

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

maps to

Nutshell

People

1:1
Fully supported

Lexis 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

maps to

Nutshell

Company

1:1
Fully supported

Lexis 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

maps to

Nutshell

Lead + Custom Fields

1:1
Fully supported

Matters 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

maps to

Nutshell

Lead Contact Association

1:1
Fully supported

When 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)

maps to

Nutshell

Custom Fields on Lead / Person

1:1
Fully supported

Lexis 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

maps to

Nutshell

Task / Activity + Custom Fields

1:1
Fully supported

Time 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

maps to

Nutshell

Custom Fields on Lead / Person

1:1
Fully supported

Nutshell 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

maps to

Nutshell

Custom Fields on Company / Person

1:1
Fully supported

Trust-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

maps to

Nutshell

Files on related record

1:1
Fully supported

Documents 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

maps to

Nutshell

Not Migrated

1:1
Fully supported

Lexis 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

maps to

Nutshell

Note on Person / Company

1:1
Fully supported

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

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.

Lexis Affinity logo

Lexis Affinity gotchas

High

Records and Safe Custody module creates migration lock-in

High

DataForm custom field schemas are per-firm and must be reverse-engineered

Medium

Trust account sub-account types map differently to destination ledgers

Medium

Workflow automations do not export and must be rebuilt manually

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

  • Lexis Affinity has no documented public bulk-export API

    Unlike HubSpot or Salesforce, Lexis Affinity does not expose a documented REST or GraphQL API for bulk record extraction. Export paths include CSV downloads from the UI for some record types, EzeScan integration for document capture, and the Nexis SourceData API for specific data modules. This means the extraction phase of the migration may require multiple export formats (CSV, JSON from SourceData, and manual pulls for documents) stitched together before field mapping begins. We validate each export format's row completeness before mapping to avoid silent data gaps in Nutshell.

  • Matters require a hybrid mapping strategy with no native Nutshell equivalent

    Lexis Affinity Matters are the legal equivalent of a combined Lead and Project — they have status, responsible attorney, billing arrangement, open/close dates, and arbitrary DataForm metadata. Nutshell has no native matter entity. FlitStack AI maps each Matter to a Nutshell Lead record with the matter name as the Lead name, the primary client Person linked to it, and all matter-specific fields (Matter Number, Billing Arrangement, Open Date, etc.) stored as custom fields on the Lead. The limitation is that Nutshell's native Lead status pick-list (New, Working, Nurturing, Dead) does not map cleanly to legal matter statuses (Open, Closed, Pending, On Hold) — value mapping must be configured explicitly in Nutshell's Lead settings before migration runs.

  • Trust-account balances and ledger history have no Nutshell home

    Lexis Affinity's trust-account module tracks IOLTA-compliant ledger entries with running balances per client matter. Nutshell has no trust-account, IOLTA, or trust-ledger construct. FlitStack AI preserves trust-account identifiers and most-recent balance as custom fields on the related Company or Person record. However, the full transaction ledger (deposits, withdrawals, reconcile entries) cannot be represented natively in Nutshell and is delivered as a separate CSV export attached to the relevant record. Firms with active trust accounts should coordinate with their accounting team to determine the appropriate post-migration trust-account management strategy.

  • Workflow Builder automations do not transfer and require a rebuild plan

    Lexis Affinity's Workflow Builder supports legal-specific automation triggers — for example, auto-creating conflict-check requests when a new matter opens, or filing documents to a matter folder when a specific DataForm field is saved. Nutshell's Triggers and Automations support stage-change, field-change, and date-based triggers but not legal-workflow logic like conflict-check sequencing or document-filing rules. We export Lexis Affinity workflow definitions as a structured JSON document so your Nutshell admin can reference the original logic when rebuilding in Nutshell Triggers. This is disclosed upfront so expectations are set before the migration date.

  • Conflict-check records are text-only in Nutshell

    Lexis Affinity runs conflict checks against the organization's client list and surfaces conflict flags, reviewer notes, and clearance status per matter. Nutshell has no conflict-check module. FlitStack AI maps conflict-check results to a Note attached to the relevant Person or Company record, preserving the outcome text (e.g., 'No conflict — cleared by J. Smith on 2025-11-15'). Firms with strict conflict-management requirements should evaluate a dedicated conflict-check integration for Nutshell post-migration, as the conflict-check workflow itself cannot be replicated in Nutshell's native automation tools.

Migration approach

Six steps for a successful Lexis Affinity to Nutshell data migration

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

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

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

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

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

Context on both ends of the pair

Lexis Affinity logo

Lexis Affinity

Source

Strengths

  • Comprehensive trust accounting with IOLTA, controlled money, and investment sub-account support for regulatory compliance.
  • Deep bank reconciliation integration with major commercial bank portals for automated GL matching.
  • Records Management and Safe Custody modules purpose-built for legal document retention and escrow obligations.
  • Built-in conflict checking that runs against the full client and contact database before new Matter creation.
  • LexisNexis research content linkable directly from a Matter record for legal research workflows.

Weaknesses

  • High exit barriers due to Records/Safe Custody module — extracting historical documents and vault data requires specialist consulting.
  • Pricing is opaque and requires direct sales engagement with no public per-module breakdown.
  • API access is not widely documented for practice management data — migration work relies on data export rather than programmatic extraction.
  • Workflows and automations are not exportable and must be manually rebuilt on the destination platform.
  • Hourly consulting fees for configuration questions create cost uncertainty during both migration and ongoing use.
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. 1 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 Lexis Affinity and Nutshell.

  • Object compatibility

    B

    1 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

    Lexis Affinity: Not publicly documented for the practice management module; enterprise customers should confirm limits during onboarding.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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 consultation

Most Lexis Affinity-to-Nutshell migrations complete in 7–14 days of clock time for under 25,000 records. The longest planning step is inventorying Lexis Affinity export paths and configuring Nutshell custom fields for matter metadata, trust-account data, and billing histories. Larger setups with 100,000+ records or multiple DataForm field sets extend to 3–5 weeks. Nutshell's shallow data model (no native matter or trust-account objects) actually reduces mapping complexity compared to enterprise CRM migrations.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Lexis Affinity.
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