New report2026 State of AI at Enterprise RIAs2026 State of AI at RIAsRead it freeOn demandOther eventsNext: AI for Mid-Sized Law, Nov 5
CRM migration · Law firms

Actionstep to CosmoLex migration. Let agents do the data entry.

The import moves the easy records. The rest is your team copying matters, notes and documents from Actionstep into CosmoLex by hand. Caddi AI Agents do that part, then check both sides record by record.

  • Built on your field map
  • Every mismatch listed
  • Keeps working after cutover

Actionstep to CosmoLex: the short answers

How long it takes6 to 12 weeks

For a clean mid-size move. Years of history in Actionstep add weeks of cleanup first.

What it costs$8k to $75k

For audit, cleanup and execution, on published 2026 ranges. Not counted: licenses and your own staff's time.

The hard partThe grouping layer

Actionstep: matter type and step-based workflow. CosmoLex: client and contact links.

Who runs CosmoLex afterYour ops team

No dedicated administrator needed.

The export is the easy part. The hours are in what the import skips.

Loading CosmoLex is the part any vendor can do. What takes the time is every record that lands wrong or not at all: remapped fields, activity history, documents, and proving the result matches Actionstep.

The field map

What carries over, and what your firm has to decide

Six things decide how clean this move is. Three need a decision from your firm before any data moves. Write down who made each one.

Primary recordCarries overMatterMatterSame record on both sides. Mostly a straight load.
GroupingNeeds a decisionMatter type and step-based workflowClient and contact linksCosmoLex groups records differently, so groups are rebuilt rather than copied.
Activity historyPartialSteps, tasks and notes tied to the workflowNotes, tasks and calendarDates, authors and types usually survive. Threads and structure often do not.
DocumentsSeparate passDocuments on the matter with template linksDocuments on the matterMoves separately from the records, so plan it as its own job.
Owner and assignmentNeeds a decisionAssigned user or advisor fieldsAssigned user or team fieldsMap departed staff explicitly. Records assigned to nobody disappear from every view.
Custom fieldsNeeds a decisionFirm-specific fields added over timeCreated to match, or consciously droppedGo through them one by one. The usual surprise is an undocumented field a report still depends on.

What no export carries across

  1. 01

    Automations, reports, dashboards and permissions. They are rebuilt in CosmoLex, not moved, so budget them as build work.

  2. 02

    Connections to other tools. The DMS, billing, e-signature and the shared inbox each have to be reconnected to CosmoLex and retested.

Where Caddi fits

You make the decisions. Caddi AI Agents do the data entry.

Show an agent the task on a screenshare or describe it in chat, and change it in plain English as the mapping changes. AI builds it, verified code runs it, and every run is logged and reviewable.

1

Move the records

Agents read Actionstep, apply your field map and load CosmoLex. The mapping decisions stay yours. The typing does not.

2

File the documents

Agents file each document to the right CosmoLex record with the right metadata, instead of a folder dump someone sorts later.

3

Cover the overlap

While both systems are live, agents copy new matters and updates from Actionstep into CosmoLex, so nobody enters everything twice.

4

Prove it matches

Agents compare CosmoLex to Actionstep record by record and list everything that does not match, so you fix the gaps before anyone trips over them.

Then the agents stay

A migration tool leaves on cutover day. The work it ignored does not: intake email, signed documents and billing still have to reach CosmoLex. The same agents keep doing that data entry across your tools, so the clean matters you just paid for stay clean.

Scope it

How much hand entry is in your move?

Nobody quotes you for staff time. Put in your own numbers and see what the import leaves on your team.

Hand entry on your numbers267 hours4,000 records touched by hand. About 6.7 weeks of one person doing nothing else.
Hand those hours to Caddi AI Agents.
The plan

Five phases, and who does each one

Spend your first two weeks on Actionstep and your last two checking the result. Migrations that go wrong almost always shortened one of the two ends.

  1. 1

    Audit Actionstep

    Count what is in there, find duplicates and records attached to nothing, and decide what stays behind. Get that signed off before mapping.

    You decide
  2. 2

    Map against real records

    Start from the field map above, then walk fifty live records field by field, including the messy ones.

    You decide
  3. 3

    Dry run the full load

    Load everything into a test copy of CosmoLex, not a sample. Samples hide the failures that only show up at volume.

    Caddi runs it
  4. 4

    Cut over on a quiet window

    Freeze Actionstep, load CosmoLex, reconnect every tool that talked to Actionstep, then go live. Keep Actionstep read-only for at least a quarter.

    Together
  5. 5

    Reconcile

    Compare CosmoLex to Actionstep record by record and list everything that does not match. Keep that list with your records.

    Caddi runs it

The longer version, with the evidence behind it, is in the CRM migration playbook.

The fine print

The cost breakdown and the known quirks

Cost breakdown

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

Published 2026 ranges. CosmoLex pricing: Custom quoted.

Actionstep quirks to plan for

  • The step-based workflow is the system's value and has no direct equivalent elsewhere.
  • Matter state lives partly in the workflow position rather than in fields.
  • Multi-jurisdiction configurations multiply the number of matter types to map.

Getting data out: CSV export and the Actionstep API.

CosmoLex quirks to plan for

  • The general ledger and trust accounting are the reason firms chose it, and most targets do not replace them.
  • Accounting and matter data have to reconcile after the move or the books do not tie.
  • Historic trust transactions carry retention obligations of their own.

Who runs it: No dedicated administrator needed.

Actionstep to CosmoLex migration questions

How do you migrate from Actionstep to CosmoLex?

Five steps. Audit the Actionstep data, map fields against fifty real records, dry run the full set into a test copy of CosmoLex, cut over on a quiet window with Actionstep frozen, then compare the two systems record by record. Getting data out of Actionstep: CSV export and the Actionstep API. Documents move as a separate pass.

What does not transfer from Actionstep to CosmoLex?

Both systems work in matter records, but they group them differently: Actionstep uses matter type and step-based workflow, while CosmoLex uses client and contact links. Activity history carries only in part: dates, authors and types usually survive, threads and structure often do not. And no export carries automations, reports, dashboards and permissions; connections to other tools.

How long does a Actionstep to CosmoLex migration take?

Six to twelve weeks for a clean mid-size move. Firms with years of history in Actionstep should add several weeks of cleanup before any data moves.

Will CosmoLex migrate my data from Actionstep for me?

Ask CosmoLex's onboarding team exactly what their import covers, and get it in writing. Vendor imports usually handle the standard records. The usual gaps are activity history, documents, custom fields, anything connected to Actionstep, and the reconciliation that proves the result matches. Those gaps are where the hand entry comes from.

Can Caddi do the Actionstep to CosmoLex migration work?

Caddi AI Agents do the mechanical work of the move: they read Actionstep, apply your field map, load CosmoLex, file documents to the right record, and compare both sides record by record so you get a list of everything that does not match. Someone at your firm still makes the mapping decisions and signs them off. After cutover the same agents keep doing the data entry between CosmoLex and the tools around it.

Who administers CosmoLex afterwards?

No dedicated administrator needed. 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 list of mismatches and the sign-offs with the records.

Need help with this migration?

Let Caddi AI Agents do the data entry across Actionstep, CosmoLex and the tools around them.

Thirty minutes. Bring your field map or nothing at all, and leave with a plan for the records, the documents, the overlap and the reconciliation.

Moving Actionstep to CosmoLex?Get a migration plan