Migrate your Lexis Affinity data
LexisNexis-backed practice management software for mid-tier law firms with deep financial compliance, trust accounting, and records management modules built for firms in the Pacific region.
In its favor
Why people choose Lexis Affinity
The signal that keeps Lexis Affinity on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Comprehensive financial compliance modules including dedicated Bank Reconciliation, Trust Accounting, and Investment/Controlled Money Accounts for firms with complex regulatory requirements.
Records Management module with Safe Custody vault functionality that many Pacific-region law firms rely on for document retention and escrow workflows.
Deep integration with commercial bank portals for automated reconciliation, reducing manual GL matching for accounting staff.
Built on the LexisNexis data infrastructure, giving firms access to legal research content linked directly from a Matter record.
Workflow automation capabilities that span document management, billing triggers, and conflict checking across the firm.
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.
Reasons to switch
Why people leave Lexis Affinity
The recurring reasons buyers give for replacing Lexis Affinity. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Lexis Affinity fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Lexis Affinity pricing overview
Lexis Affinity uses opaque custom pricing with per-seat licensing and annual contract commitments. There are no public price lists; firms must engage a LexisNexis sales representative. The platform is positioned for mid-to-large law firms (50+ attorneys) and the Pacific region market, which contributes to regional pricing expectations.
Standard
Tier 1 of 3
Custom (per-seat, annual contract)
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Lexis Affinity's schedule — see our quote-based pricing →
What gets migrated
Lexis Affinity object support
Object-by-object support for Lexis Affinity migrations. Per-pair details surface during scoping.
Matters
Fully supportedMatters are the primary case object in Lexis Affinity. They carry standard fields (status, responsible attorney, client link, matter number) plus firm-defined DataForm fields. We extract matter records with their full DataForm schema and map them to the destination's equivalent case or matter object.
Clients
Fully supportedClient records in Lexis Affinity link to one or more Matters and carry contact details, billing information, and conflict check history. We migrate client records 1:1 and preserve the matter-client associations in a junction mapping table for post-migration validation.
Documents
Mapping requiredLexis Affinity stores documents in a folder hierarchy tied to Matters and Clients. We extract documents with their metadata (author, date, version, classification) but folder structure preservation depends on the destination platform's taxonomy model. We reconstruct folder hierarchies as tags or custom fields where a 1:1 mapping is not available.
Time Entries
Fully supportedTime entries are linked to Matters and include billing rate, duration, description, and user attribution. We migrate time entries as standalone records with their Matter linkage preserved. Time entries that have been billed are flagged separately from unbilled entries.
Billing Records and Invoices
Mapping requiredBilling in Lexis Affinity ties directly to the firm's accounting ledger. We export invoice records, line items, and payment history. Pre-billed time entries are migrated as drafts. The challenge is that Lexis Affinity's invoice numbering scheme may conflict with the destination's numbering conventions; we handle prefix mapping at import time.
Trust Accounts
Mapping requiredTrust accounts in Lexis Affinity are governed by legal accounting rules (IOLTA, controlled money, investment accounts). Each trust sub-account has its own ledger and reconciliation cycle. We migrate trust account balances and transaction history but flag that the destination must also support multi-ledger trust accounting — not all practice management platforms do.
DataForms (Custom Matter Fields)
Mapping requiredDataForms are Lexis Affinity's mechanism for firm-specific custom fields on Matters and other objects. Every firm's DataForm schema is unique. We extract the full DataForm definition alongside each record so we can map custom fields to the destination's equivalent custom field mechanism. Unmapped DataForms are stored as JSON blobs for manual post-migration cleanup.
Workflows
Not in this platformLexis Affinity's workflow automation rules are tightly coupled to the platform's internal event model and are not exportable via API or standard data export. We document the active workflows during discovery so the firm can manually rebuild them on the destination platform. No automated workflow migration is available.
Calendar and Tasks
Mapping requiredLexis Affinity stores calendar events and tasks linked to Matters or standalone. We export events with dates, assignees, and Matter associations. Task status and priority mapping depends on the destination's status taxonomy.
Communication History
Mapping requiredEmail integration logs and communication notes are stored per Matter. We extract linked communications as notes or attachments depending on volume and the destination's handling of conversation threads.
Bank Reconciliation Data
Mapping requiredBank reconciliation records export from Lexis Affinity's accounting module with GL account mappings. We preserve reconciliation status (reconciled, pending, cleared) and bank statement references. Note that some reconciliation data ties to the portal integration which does not transfer.
| Object | Support | Notes |
|---|---|---|
| Matters | Fully supported | Matters are the primary case object in Lexis Affinity. They carry standard fields (status, responsible attorney, client link, matter number) plus firm-defined DataForm fields. We extract matter records with their full DataForm schema and map them to the destination's equivalent case or matter object. |
| Clients | Fully supported | Client records in Lexis Affinity link to one or more Matters and carry contact details, billing information, and conflict check history. We migrate client records 1:1 and preserve the matter-client associations in a junction mapping table for post-migration validation. |
| Documents | Mapping required | Lexis Affinity stores documents in a folder hierarchy tied to Matters and Clients. We extract documents with their metadata (author, date, version, classification) but folder structure preservation depends on the destination platform's taxonomy model. We reconstruct folder hierarchies as tags or custom fields where a 1:1 mapping is not available. |
| Time Entries | Fully supported | Time entries are linked to Matters and include billing rate, duration, description, and user attribution. We migrate time entries as standalone records with their Matter linkage preserved. Time entries that have been billed are flagged separately from unbilled entries. |
| Billing Records and Invoices | Mapping required | Billing in Lexis Affinity ties directly to the firm's accounting ledger. We export invoice records, line items, and payment history. Pre-billed time entries are migrated as drafts. The challenge is that Lexis Affinity's invoice numbering scheme may conflict with the destination's numbering conventions; we handle prefix mapping at import time. |
| Trust Accounts | Mapping required | Trust accounts in Lexis Affinity are governed by legal accounting rules (IOLTA, controlled money, investment accounts). Each trust sub-account has its own ledger and reconciliation cycle. We migrate trust account balances and transaction history but flag that the destination must also support multi-ledger trust accounting — not all practice management platforms do. |
| DataForms (Custom Matter Fields) | Mapping required | DataForms are Lexis Affinity's mechanism for firm-specific custom fields on Matters and other objects. Every firm's DataForm schema is unique. We extract the full DataForm definition alongside each record so we can map custom fields to the destination's equivalent custom field mechanism. Unmapped DataForms are stored as JSON blobs for manual post-migration cleanup. |
| Workflows | Not in this platform | Lexis Affinity's workflow automation rules are tightly coupled to the platform's internal event model and are not exportable via API or standard data export. We document the active workflows during discovery so the firm can manually rebuild them on the destination platform. No automated workflow migration is available. |
| Calendar and Tasks | Mapping required | Lexis Affinity stores calendar events and tasks linked to Matters or standalone. We export events with dates, assignees, and Matter associations. Task status and priority mapping depends on the destination's status taxonomy. |
| Communication History | Mapping required | Email integration logs and communication notes are stored per Matter. We extract linked communications as notes or attachments depending on volume and the destination's handling of conversation threads. |
| Bank Reconciliation Data | Mapping required | Bank reconciliation records export from Lexis Affinity's accounting module with GL account mappings. We preserve reconciliation status (reconciled, pending, cleared) and bank statement references. Note that some reconciliation data ties to the portal integration which does not transfer. |
Gotchas
What to watch for in Lexis Affinity migrations
Issues we've hit on past Lexis Affinity migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
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
| Severity | Issue |
|---|---|
| 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 |
Leaving Lexis Affinity?
Where Lexis Affinity customers move next
12 destinations Lexis Affinity can migrate to.
How a Lexis Affinity migration works
Four steps, Lexis Affinity-specific
Connect
OAuth 2.0 and API key (platform-wide and per-user keys) into Lexis Affinity. Scopes limited to read-only on the data we move.
Map
We translate Lexis Affinity-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Lexis Affinity quirks before production.
Migrate
Full migration with Lexis Affinity rate-limit handling. Rollback available throughout.
FAQ
Lexis Affinity migration FAQ
Answers to the questions buyers ask most during Lexis Affinity migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Lexis Affinity migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Lexis Affinity.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Lexis Affinity setup and destination — written quote back within a business day.