Key takeaways
- Decide what to migrate, what to archive and what to leave behind before any data moves; closed matters rarely need full migration.
- Cut accounts over at a clean reconciliation point and reconcile again on the new system before posting anything new.
- The migration supplier is a processor under UK GDPR; the contract should cover security, deletion of test copies and return of data.
- Run at least two trial migrations, keep the old system read-only and plan the first 30 days of support.
Why migrations go wrong
Most failed migrations do not fail on go-live day. They fail months earlier, when a firm agrees a date before it knows what its data looks like, or assumes the vendor will sort out the mapping. Duplicate client records, matters with no fee earner, ledgers that never quite balanced and documents saved in personal folders all surface during migration. The time to find them is in a trial run, not on the first Monday after cut-over.
Mergers are a common trigger. Of 514 law firm closures in England and Wales in the year to June 2026, 95 (18.5%) were mergers or amalgamations, while 319 (62.1%) were firms that ceased practising[1]. Every merger raises the question of whose system survives and how the other firm's data is brought across.
- Ceased practising 319 62%
- Merged or amalgamated 95 18%
- Other reasons 100 19%
Source: Solicitors Regulation Authority, 2026[1]
Show the data
| Item | Value |
|---|---|
| Ceased practising | 319 |
| Merged or amalgamated | 95 |
| Other reasons | 100 |
The phases of a migration
Inventory
List every system, spreadsheet and shared folder that holds matter, client or accounts data, and who owns each one.
Decide scope
Choose what migrates in full, what becomes a searchable archive and what stays behind in a read-only copy of the old system.
Clean the data
Merge duplicate clients, close finished matters, assign every live matter to a fee earner and clear old ledger balances properly.
Map fields
Match each field in the old system to the new one, and record what happens to fields with no equivalent.
First trial migration
Move a full copy into a test environment and check sample matters, ledgers and documents against the old system.
Fix and repeat
Correct the mapping and run a second trial. Do not fix the go-live date until a trial passes.
Train
Train every user on the trial data, so they practise on their own matters.
Cut over
Freeze the old system, run the final migration, reconcile and open the new system for work.
Support
Provide floor support and a daily issue review for the first two weeks.
Close the project
After 30 days, confirm open issues, archive the old system and record lessons learned.
What to migrate, archive or leave
| Data | Usual approach | Checks after migration |
|---|---|---|
| Live matters | Migrate in full: details, parties, key dates, tasks, documents | Sample by fee earner; check every key date and limitation reminder |
| Client and office ledgers | Migrate balances and history for live matters | Three-way reconciliation on the new system before new postings |
| Closed matters within retention period | Archive in a searchable format, or migrate summary only | Test that a closed file can be found and opened |
| Matters past retention | Review for destruction under your retention policy | Destruction log signed off |
| Time and work in progress | Migrate unbilled entries for live matters | Totals match per matter |
| Templates and precedents | Rebuild in the new system rather than copy | Owner signs off each template |
| Enquiries and contacts | Migrate current contacts with consent records | No duplicate clients created |
Archiving closed matters rather than migrating them in full often halves the size of the project. The archive still needs to be secure, searchable and covered by your retention policy, but it does not need to work inside the new system's workflows.
Who should be on the project team
Small firms cannot spare a full-time project manager, but a migration still needs clear roles. A partner sponsor makes scope and date decisions and has authority to delay go-live. A project lead, often the practice manager, runs the plan, the issue log and the vendor. The COFA or cashier owns accounts mapping and reconciliation. One fee earner from each practice area checks that workflows, key dates and templates make sense for real files. The IT provider handles access, devices and integrations.
Agree how much time each person will give the project each week, and reduce their other work to match. Migrations stall most often because the people who understand the data are also the busiest fee earners, and the checking is squeezed into evenings. Book the trial-migration check days in diaries as soon as the vendor confirms them.
Accounts cut-over
Accounts are where migration risk is highest. The SRA Accounts Rules require reconciliations for all client accounts at least every five weeks and accurate, contemporaneous and chronological records[2]. Plan the cut-over so that the last reconciliation on the old system is completed and signed off, balances are migrated, and a fresh three-way reconciliation is completed on the new system before anyone posts a new entry.
Choose a cut-over date shortly after a reconciliation rather than just before a deadline, and avoid month ends and busy completion days. Keep the old accounts system available read-only, so that historic entries remain accessible to the reporting accountant and to anyone answering a query about an old matter.
Data protection during migration
A migration usually means client data is copied by a third party, often more than once. That supplier is a processor, and UK GDPR requires a contract covering points including acting only on your documented instructions, security, sub-processors and the deletion or return of personal data when the services end[3]. Ask specifically what happens to the test copies made during trial migrations, and get written confirmation that they have been deleted.
If something goes wrong, such as an export sent to the wrong place or a test environment left open, the normal breach rules apply: notifiable breaches must be reported to the regulator without undue delay and, where feasible, within 72 hours of becoming aware[4]. Agree in advance how the supplier will tell you about an incident.
The cut-over weekend
- Friday afternoon: freeze the old system for new entries; complete the final reconciliation; take a full backup.
- Friday evening: run the final migration into the live environment.
- Saturday: check sample matters per fee earner, key dates, ledgers and documents against the old system; log every discrepancy.
- Sunday: fix discrepancies, complete the three-way reconciliation on the new system and sign off go-live, or decide to roll back.
- Monday: floor support in each team, a morning issue review and a named person for urgent accounts queries.
Write down the rollback decision in advance: what would make you stay on the old system for another week, and who makes that call. A clear rollback point is what makes it safe to go ahead.
Keeping clients informed
Clients rarely notice a successful migration, but they notice delays and confusion. Poor communication and delay were the two most common complaint types brought to the Legal Ombudsman in 2025/26, at 24% and 22%[5]. If a portal, email address or document link is changing, tell clients beforehand. Brief reception on what to say if callers ask why a reply is slower in the first week, and avoid scheduling go-live during a known peak such as the run-up to a stamp duty deadline.
Training that sticks
Train on your own data from the trial migration, not on the vendor's demo database. People learn faster when they see their own matters. Train by role: fee earners on matters, tasks and documents; cashiers on accounts; supervisors on reports. Keep a short internal guide with screenshots of your own workflows, and appoint a super-user in each team who gets extra training and protected time during the first month.
Example: a twelve-person firm's migration
Example (fictional): a twelve-person firm moving from a server-based system to a cloud suite decides to migrate only live matters and the last two years of closed files, and archives everything older in a searchable read-only store. The first trial migration finds over 300 duplicate client records and 40 matters with no fee earner. After cleaning, the second trial passes. The firm cuts over the weekend after a reconciliation, keeps the old system read-only for a year, and holds a daily 15-minute issue review for two weeks.
The first 30 days
- Review the issue log daily for two weeks, then weekly.
- Run a full reconciliation on the new system at the first normal cycle date.
- Ask each fee earner to confirm their key dates and limitation reminders are correct.
- Check that new matters are opening with the right templates and workflows.
- Confirm deletion of test copies by the migration supplier in writing.
Before you choose a system, see legal CRM: does a small firm need one? and conveyancing technology for features worth bringing across. After go-live, review your Microsoft 365 security settings, since new integrations often change permissions.
Frequently asked questions
How long does a case management migration take?
For a small firm, typically several months from inventory to go-live, depending on data quality. Plan for at least two trial migrations and do not fix the go-live date until a trial passes.
Should we migrate closed matters?
Often not in full. Many firms migrate live matters and recent closed files, and keep older matters in a searchable, secure archive covered by their retention policy.
How do we migrate client account balances safely?
Complete and sign off a reconciliation on the old system, migrate the balances, then complete a three-way reconciliation on the new system before posting new entries.
Does our migration supplier need a data processing agreement?
Yes. They process personal data on your behalf, so UK GDPR requires a contract covering instructions, security, sub-processors and deletion or return of data, including test copies.
References
Solicitors Regulation Authority (2026). Breakdown of firm closures by reason (opens in a new tab) ↑
Solicitors Regulation Authority (2019). SRA Accounts Rules (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2016). UK GDPR Article 28: Processor (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2016). UK GDPR Article 33: Notification of a personal data breach to the supervisory authority (opens in a new tab) ↑
Legal Ombudsman (2026). Legal Ombudsman 2025/26 annual complaints data and insight (opens in a new tab) ↑