Moving Practice Management Systems? Eight Data Migration Mistakes to Avoid
Most failed system switches trace back to data decisions made in the first two weeks. Here are eight costly migration mistakes, what to do instead, and what a clean cutover typically costs.
Mistake one: moving every closed matter wholesale
You've signed with a new platform, and the vendor wants your data export. The next few decisions will determine whether the project works. A practice management software migration rarely fails because the new system is bad. It fails because the firm moves fifteen years of inconsistent, half-closed and duplicated records into a clean system, then spends a year working around them.
The usual culprit is the instruction to "just bring everything across." It feels safe. It isn't. Every closed matter you migrate has to be field-mapped, validated and paid for, since many migration services price by record volume or complexity. Old matters also carry stale conflict entries, contacts with three spellings and matter types nobody uses anymore.
What to do instead: split your matters into three tiers before anyone touches an export file.
- Active and recently closed (often closed within the last two to three years): migrate in full, including notes, tasks, time and documents.
- Older closed matters still inside a retention period: migrate a light record (client, matter number, parties for conflict checks, open and close dates, responsible lawyer) and archive the full file in a searchable, read-only store.
- Matters past every retention obligation: review them for destruction under your records policy rather than migrating them.
Conflict data is the exception. Parties and adverse parties from old matters usually belong in the new system's conflict search even when the matter itself doesn't.
Mistakes two and three: unreconciled client-account ledgers and orphaned unbilled time
Money data is where a messy cutover becomes a regulatory problem. Client money rules differ by country: trust accounting in the US and Canada, the SRA Accounts Rules in England and Wales, and law society or bar rules in Australia, Singapore, South Africa and elsewhere. Nearly all expect per-client balances that tie back to the bank at any point in time.
Mistake two is cutting over without a full reconciliation. Migrate an unreconciled ledger and you import the discrepancy, with no clean way to show where it came from. What to do instead: perform a three-way reconciliation (bank statement, client-account cash book, individual client ledgers) as at the cutover date. Resolve or document every difference, have the responsible partner or compliance officer sign it off, and migrate opening balances only. Keep the old system's full transaction history read-only for audit.
Mistake three is ignoring work in progress. Unbilled time, disbursements and part-paid invoices often fail to map cleanly between systems. What to do instead: run a billing push before cutover so as much WIP as possible is invoiced in the old system. Migrate only the remaining unbilled entries and open invoices, and check them line by line against an aged-debtor and WIP report from the legacy platform.
Mistake four: breaking document-to-matter links
Firms often treat document migration as a separate, later project. That's how you end up with hundreds of thousands of files in the new system and no reliable way to tell which matter they belong to. Folder names drift, matter numbers get reformatted (2019-0042 becomes 19/42), and email filed through Outlook add-ins may sit in a separate store entirely.
The links break in predictable places: matter number format changes, documents filed against clients rather than matters, version histories that flatten into separate files, and metadata such as author and date that gets overwritten with the migration date.
What to do instead:
- Fix the matter numbering scheme first and build a crosswalk table (old ID to new ID) that both the matter migration and the document migration use.
- Decide early whether documents live in the practice management platform or in a dedicated DMS such as NetDocuments or iManage. If they stay in a DMS, the integration mapping matters more than the file transfer.
- Preserve original created and modified dates and authors. Firms often rely on them in disputes.
- Sample-test: pick 50 matters across practice areas and check that every document, email and version arrived attached to the right matter.
Mistakes five and six: one-size retention rules and overlooked data residency
Mistake five is applying a single retention period to everything. Obligations vary by jurisdiction, record type and sometimes practice area. Client-account records often carry a specific minimum, commonly in the five-to-seven-year range in many common-law jurisdictions, but check your own rules. Matter files may be governed by limitation periods, which differ by country and claim type. Wills, deeds, matters involving minors and some real estate records may need to be kept far longer. Data-protection laws such as the GDPR, UK GDPR, India's Digital Personal Data Protection Act and Brazil's LGPD push the other way: don't keep personal data longer than you need it.
What to do instead: build a retention schedule by record type and jurisdiction before migration, then tag each matter with its destruction or review date in the new system. Multi-office firms need one schedule per jurisdiction, not a lowest-common-denominator rule. Have professional-responsibility counsel or your regulator's guidance confirm the periods. Don't infer them from a vendor's default settings.
Mistake six is assuming that where the data lives doesn't matter. Moving to a cloud platform hosted in another region can trigger cross-border transfer rules or client contractual restrictions. Check which hosting regions the vendor offers. Clio, Actionstep and LEAP, for example, each serve several regions, but availability varies and changes. Also check whether your largest institutional clients' outside-counsel guidelines restrict data location.
Mistakes seven and eight: mapping fields without cleanup and skipping the trial run
Mistake seven is mapping old fields one-to-one into the new system. Cleanup is tedious, so firms skip it, and the new system inherits 60 matter types where 15 would do, custom fields nobody fills in, and duplicate contacts that break conflict searches. What to do instead: run a cleanup sprint in the old system. Merge duplicate contacts, collapse matter types, retire unused custom fields and standardize responsible-lawyer and office codes. Clean data is cheaper to migrate and easier to validate.
Mistake eight is going live on the first full load. What to do instead: insist on at least one trial migration into a sandbox, ideally two. Give named fee earners and accounts staff a checklist: open their ten busiest matters and confirm contacts, key dates, documents, balances and unbilled time. Sign off only when sampled records show near-zero errors and every known gap has a documented workaround.
Hypothetical example: say a 30-lawyer firm finds in its first trial load that a meaningful share of matters show the wrong responsible lawyer because two legacy office codes were merged years ago. Catching that in a sandbox costs a remapping day. Catching it after go-live corrupts reporting, billing routing and possibly conflict checks.
What a clean cutover typically costs and how long it takes
Cost depends far more on data complexity than on headcount. The main drivers are the number of source systems, whether accounting and client-account data is in scope, document volume, how much cleanup you do in-house, and whether you use the vendor's migration team or a specialist consultancy. The ranges below are indicative 2026 market figures for law firm data migration. They vary widely by contract and region, so confirm with vendors.
| Firm profile | Typical scope | Indicative migration cost (USD) | Typical timeline |
|---|---|---|---|
| Small firm, 2–10 lawyers | Matters, contacts, time; documents in cloud storage | $0–$5,000 (often bundled with subscription) | 3–6 weeks |
| Mid-size, 10–50 lawyers | Plus client-account ledgers, billing history, DMS links | $5,000–$40,000 | 2–4 months |
| Larger or multi-jurisdiction, 50+ lawyers | Multiple source systems, several retention schedules, enterprise DMS | $40,000–$150,000+ | 4–9 months |
Be wary of proposals with a fixed quote but no data assessment, no sandbox load, no reconciliation step, or a vague answer about documents. Check your old vendor's exit terms too. Export fees, proprietary formats and notice periods can add weeks.
Next step: before you sign a migration statement of work, produce three documents internally: a tiered matter inventory, a client-account reconciliation plan, and a retention schedule by jurisdiction. If a vendor can't price against those three, keep looking.
Frequently asked questions
Should we migrate all historical matters into the new practice management system?
Usually not. Most firms migrate active and recently closed matters in full and move a lightweight record of older matters for conflict checking. Full historical files go into a read-only archive. This cuts cost and keeps the new system clean while preserving what you need for conflicts and retention.
How long should we keep the old system running after cutover?
Plan for read-only access through at least one full audit or reconciliation cycle, often a year or more. You'll need it to answer questions about pre-migration transactions and documents. If the vendor won't offer an affordable read-only license, take a complete export in an open format such as CSV, PDF or native files, and confirm you can search it before the contract ends.
Who should own the migration inside the firm?
Give it to one accountable lead, typically the practice manager, COO or legal operations lead. Back that person with a partner sponsor and the finance or compliance officer for client-account data. IT and the vendor run the mechanics, but scope, cleanup, retention and sign-off are business decisions. For questions about retention or client money, consult your regulator's guidance or a qualified professional.
Written by the Lexstack Cloud editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.