Key takeaways
- Every software switch means a data migration, and not everything always moves cleanly.
- What's most likely to get left behind is context: notes, communication history, custom fields, automations and AI history.
- A tool-agnostic data layer keeps your firm's history in one place, whichever tools you use.
In part 1, we looked at how siloed systems hide your firm's biggest problems. Silos cause a second problem that most firms only discover when it's expensive: your data lives inside your vendors, not inside your firm.
You feel it the day you decide to switch.
Why law firms switch legal software
Firms change practice management, intake and billing tools for good reasons:
- The firm has outgrown the tool, or the tool no longer fits a new practice area.
- Prices rise, or a competitor offers features the firm needs.
- A merger or new partner brings a different system with them.
- The team simply isn't using the tool, and a fresh start looks easier.
Whatever the reason, switching means moving years of the firm's history from one vendor's system into another's.
What usually moves, and what can get left behind
Migrations have improved, and vendors often help. But the core records tend to move more cleanly than the context around them:
| Usually moves | Can get left behind or arrive changed |
|---|---|
| Contacts and matters | Custom fields, and the way you organized them |
| Documents, in bulk | Folder structures, tags and document versions |
| Time entries and invoices | Notes, comments and internal messages |
| Calendar events and deadlines | Automations, workflows and templates |
| Basic client details | AI conversation history and context built inside the old tool |
The exact picture depends on the two systems and how the migration is done, so ask every vendor for a written list of what transfers and what doesn't. Even a good migration usually moves records, not context.
The hidden costs of a migration
- Staff time spent cleaning, mapping and checking data, often while still doing client work.
- Running two systems side by side during the changeover.
- Rebuilding automations, templates, intake workflows and reports from scratch.
- Retraining the team on new screens and new habits.
- Lost history: the notes and conversations that answered "why did we do that?" on a matter.
The migration takes six weeks. Intake automations are rebuilt by hand. Three years of internal notes arrive as a spreadsheet nobody opens. The AI assistant in the new tool starts with no memory of any matter.
Matters, documents, notes and AI history already live in the firm's own data layer. The new platform gets connected, and everything stays searchable. The switch becomes a reconnection, not a rebuild.
The AI lock-in nobody talks about
As every legal tech tool adds AI, a new kind of lock-in is appearing. Summaries, drafts and conversations created with a tool's built-in AI often live inside that tool. When the firm leaves, that work can stay behind.
The same thing happens with people. When an associate leaves and their AI conversations about a matter were in a personal ChatGPT account, that context walks out the door with them.
The associate's research, AI summaries and reasoning about the case lived in their own AI account and inbox. The new attorney starts from the file and a handoff memo.
The matter's documents, notes and AI conversations are stored with the matter. The new attorney picks up where the associate left off.
Your data needs a home of its own
The fix is to separate where your data lives from the tools you use. Think of it as a data fabric: a secure layer that connects to every system, brings in what matters, indexes it, and keeps it in one place your firm owns. Tools can plug in and out. Your firm's history stays put.
That's what we built Geistra Legal to do. It:
- Connects to practice management, CRM and intake, phone, billing and marketing systems.
- Indexes documents, photos, evidence, emails and financial reports, so they're searchable in plain English.
- Keeps AI conversation history with the matter, not with a person or a vendor.
- Works with the AI your team already uses: Claude, ChatGPT, Microsoft Copilot or Gemini.
Before you switch: a checklist
- Take inventory. List every type of data, custom field and automation in your current tools.
- Get it in writing. Ask the new vendor exactly what transfers, what doesn't and in what format.
- Export a full copy first, and store it somewhere your firm controls.
- Decide what context must survive, such as notes, email history and AI conversations.
- Set up your data layer before the move, so switching tools means reconnecting one system.
Coming up in part 3
Once your data has a home of its own, something bigger becomes possible. In part 3, we show how firms use Claude, Microsoft Copilot or ChatGPT on top of that data to run the whole firm, not just manage legal work.
Switching legal software: common questions
How long does a practice management migration take?
It varies with the size of the firm, the amount of data and the two systems involved. Small firms can move in a few weeks. Firms with years of documents, custom fields and automations should plan for longer, including time to check the data afterward.
Can we export all of our data from our current software?
Most platforms offer exports, but formats and completeness vary. Ask your vendor what a full export includes, especially notes, communications and custom fields, and test it before you need it.
What happens to our data if we cancel a legal software subscription?
Check your contract's data retention and export terms before you cancel. Access is often limited after a subscription ends, so export everything you need while you still have full access.