The hard part of this move is not the export. It is the difference in how the two systems think. LexisNexis InterAction works in contact records; MyCase works in case records. Get that mapping wrong and every report built on it afterwards is wrong too. This page covers the field map, what does not survive, what it costs, and the reconciliation step that decides whether anyone trusts MyCase in month two.
The two systems, side by side
| LexisNexis InterAction | MyCase | |
|---|---|---|
| Primary record | Contact | Case |
| Grouping | Company, relationship and folder structures | Client and contact links on the case |
| Activity history | Relationship activity, mailing lists and event history | Notes, tasks, calendar and client-portal messages |
| Documents | Largely external; the system tracks relationships, not files | Documents on the case, shared through the portal |
| Getting data out | Vendor-assisted extract; relationship intelligence is hard to represent in flat files. | CSV export per module and a vendor-assisted extract. |
| Who administers it | Marketing or BD technology staff. | None. Anyone on staff can run it. |
| Pricing | Custom quoted. | $50 to $130 per user per month billed annually. |
What breaks
- LexisNexis InterAction works in contact records and MyCase works in case records. That is a re-modelling exercise, and it is the first decision, not a mapping detail.
- Grouping changes: Company, relationship and folder structures becomes Client and contact links on the case. Somebody has to define what a group means in the target before load.
- Activity history moves with partial fidelity. LexisNexis InterAction stores it as relationship activity, mailing lists and event history; MyCase expects notes, tasks, calendar and client-portal messages.
- Automations, reports, dashboards and permissions never transfer. Budget them as build work.
- Every connected system has to be repointed and retested: the DMS, billing, e-signature and the shared inbox.
Known hazards on each side
Leaving LexisNexis InterAction:
- Relationship strength and who-knows-whom data is derived, not entered, so it cannot simply be exported and reloaded.
- Mailing lists and event history are often the most-used data and the least considered in scoping.
- Partner-level data ownership rules have to be reproduced in the target or the firm will not adopt it.
Arriving in MyCase:
- Client-portal messages are client communications, and dropping them can create a records gap.
- Billing, trust and time data reconcile separately from the case data.
- Custom fields are lightweight, so richer target systems will need decisions rather than mappings.
The field map
| Concept | In LexisNexis InterAction | In MyCase | What to watch |
|---|---|---|---|
| Primary record | Contact | Case | Different shape. Decide the mapping before any data moves. |
| Grouping | Company, relationship and folder structures | Client and contact links on the case | The target groups records differently, so grouping is created rather than copied. |
| Activity history | Relationship activity, mailing lists and event history | Notes, tasks, calendar and client-portal messages | Expect partial fidelity. Types, timestamps and authorship survive; structure often does not. |
| Documents | Largely external; the system tracks relationships, not files | Documents on the case, shared through the portal | Usually a separate extract and load from the record data. |
| Owner and assignment | Assigned user or advisor fields | Assigned user or team fields | Map departed staff explicitly. Records assigned to nobody disappear from every view. |
| Custom fields | Firm-specific fields added over time | Created to match, or consciously dropped | The audit here is the work. Undocumented fields that reports depend on are the usual surprise. |
Cost and timeline
| Phase | Typical range |
|---|---|
| Data audit and cleanup | $3,000 to $25,000 |
| Migration execution | $5,000 to $50,000 |
| Target configuration | Two to six weeks |
| Ongoing administration | Absorbed by existing operations staff |
The five phases
- Audit LexisNexis InterAction. Count records per object, find duplicates and orphans, and decide what does not come with you. Get that decision signed off before mapping.
- Map against real records. Use the table above as the starting point, then walk fifty live records field by field.
- Dry run into a MyCase sandbox. Load the full set, not a sample. Sample loads hide the failures that only appear at volume.
- Cut over on a quiet window. Freeze writes in LexisNexis InterAction, load, repoint every integration, unfreeze. Keep LexisNexis InterAction read-only for at least a quarter.
- Reconcile. Compare MyCase to LexisNexis InterAction record by record and field by field, and produce a variance report.
The full version of this plan, with the failure evidence behind it, is in the CRM migration playbook.
The compliance clause
State retention rules and the firm's duties over the client file survive the migration. A matter that lands in the target without its history is a records gap, not a cosmetic issue. Keep the field map, the variance report and the mapping sign-offs with the records, because the decisions you made in phase two are part of the record too.
Where Caddi fits
Caddi does the mechanical half and then keeps doing it. Show it the task once and it reads LexisNexis InterAction, applies your field map, loads MyCase, and then compares both sides record by record and hands back a variance report you can act on. Because it runs over APIs across your stack, the same agent covers the parts a migration tool ignores: documents filed to the right case with the right metadata, and the post-cutover hygiene that otherwise becomes someone's Monday.
Caddi automation for these systems: LexisNexis InterAction and MyCase.
Related migrations
- Clio Grow to LexisNexis InterAction
- Clio Grow to MyCase
- Clio Manage to LexisNexis InterAction
- Clio Manage to MyCase
- Filevine to LexisNexis InterAction
- Filevine to MyCase
Migration without the manual pass
Move and reconcile LexisNexis InterAction into MyCase
Caddi reads LexisNexis InterAction, applies your field map, loads MyCase, then compares both sides record by record and reports the variances.
Frequently asked questions
How do you migrate from LexisNexis InterAction to MyCase?
Audit the LexisNexis InterAction data first, then map fields against fifty real records rather than against the schema, dry run the full set into a MyCase sandbox, cut over on a quiet window with writes frozen, and reconcile record by record afterwards. Vendor-assisted extract; relationship intelligence is hard to represent in flat files. MyCase then needs the records loaded in dependency order, with documents as a separate pass.
What does not transfer from LexisNexis InterAction to MyCase?
LexisNexis InterAction works in contact records and MyCase works in case records. That is a re-modelling exercise, and it is the first decision, not a mapping detail. Grouping changes: Company, relationship and folder structures becomes Client and contact links on the case. Somebody has to define what a group means in the target before load. Activity history moves with partial fidelity. LexisNexis InterAction stores it as relationship activity, mailing lists and event history; MyCase expects notes, tasks, calendar and client-portal messages.
How long does a LexisNexis InterAction to MyCase migration take?
Six to twelve weeks is realistic for a clean mid-size move, and three to six months where MyCase is being implemented at the same time. Firms with years of history in LexisNexis InterAction should budget several weeks of cleanup before any data moves.
Who administers MyCase afterwards?
None. Anyone on staff can run it. That is one of the reasons this move is lighter than a platform migration.
What are the compliance implications for law firms?
State retention rules and duties over the client file survive the migration. A gap in matter history is a finding, not a cosmetic issue, so keep the field map, the variance report and the sign-offs with the records.