Legal Tech and AI

Switching Practice Management Software: Data Migration

A data migration checklist for switching practice management software: data map, trust records, test migrations, cutover weekend and post-move audit.

AssistCall research teamPublished Reviewed by Faruque Amin, VP of Sales and Marketing6 min read

On this page
  1. Plan the migration before you choose the vendor
  2. Questions for the new vendor
  3. Build a data map
  4. Trust accounting needs its own plan
  5. The migration timeline
  6. Protect the data while it moves
  7. Prepare people, not only data
  8. Example: a cutover weekend
  9. After go-live: audit and adopt
  10. Frequently asked questions
  11. References
Legal Tech and AI: Switching Practice Management Software: Data MigrationArticle coverLEGAL TECH AND AISwitching PracticeManagement Software:Data MigrationAva for LawyersInsightsLegal Tech and AI: Switching Practice Management Software: Data MigrationArticle coverLEGAL TECH AND AISwitching PracticeManagement Software:Data MigrationAva for Lawyers

Key takeaways

  • Map every data type before you sign: what moves, what is archived and how each will be checked.
  • Trust account records must stay complete and retrievable; the ABA Model Rule says five years after the representation ends[1].
  • Run at least one full test migration and reconcile counts and balances before the real cutover.
  • Treat export files as confidential client data and protect them accordingly[2].

Plan the migration before you choose the vendor

Switching practice management systems is mostly a data project. Learning the new software is the easy part. Moving years of matters, contacts, documents, deadlines, time entries, invoices and trust ledgers without losing anything is where firms get hurt. Ask every shortlisted vendor how they migrate from your current system, what they cannot bring across, how long it usually takes and who checks the result. Their answers should weigh as heavily in your decision as the feature list.

Most firms run this project without an IT department. In 2023, 71.8% of US law offices had fewer than five employees[3], so the migration team is usually an office manager, a bookkeeper, a partner and the vendor. Plan the timeline around their normal workload rather than assuming dedicated project staff.

Your duties do not pause during the move. ABA Model Rule 1.6(c) requires reasonable efforts to prevent the unauthorized disclosure of, or access to, client information[2]. That covers export files sitting in email, on shared drives or on a consultant's laptop just as much as the live systems.

Questions for the new vendor

  • Have you migrated firms from our current system before, and can we speak to one of them?
  • Which data types move automatically, which need manual work, and which cannot move at all?
  • Is a full test migration into a sandbox included, and how many reruns are included?
  • Who maps custom fields, and who signs off the mapping?
  • How are trust balances and ledger history brought across?
  • What does the migration cost if it overruns, and who pays for fixing errors you introduce?
  • How do we get all our data out again if we leave you?

Put the answers in the contract or statement of work. A migration promise in a sales email is hard to enforce when the cutover weekend goes wrong.

Build a data map

A data map lists every kind of information in the old system, whether it will move, and how you will prove it arrived intact. Build it with the people who use each part of the system, because they know which fields actually matter.

Data map for a practice management migration
Data typeUsually migrates?How to validate
Contacts and clientsYesCompare record counts and spot-check addresses and phone numbers
Matters and statusesYesCounts by status, plus an open-matter list reviewed by each responsible lawyer
Documents and foldersUsually, but structure may flattenCompare file counts per matter and open a sample from each year
Calendar events and deadlinesOften only partlyExport future deadlines separately and check each one by hand
Time entries and unbilled workYes, if fields are mappedUnbilled hours and value by matter match before and after
Invoices and paymentsYes, sometimes as history onlyAccounts receivable by client match to the cent
Trust ledgersVaries; balances at minimumThree-way reconciliation before and after cutover
Custom fields and notesOften lossyList each custom field and decide its new home

Deadlines deserve special suspicion. A calendar event that migrates without its reminder, its responsible lawyer or its link to the matter can look fine in a spot check and still be missed. Treat every future court date and limitation deadline as something a person verifies individually.

Trust accounting needs its own plan

ABA Model Rule 1.15 requires client funds to be kept separate from the lawyer's own property and requires complete records of those funds to be kept and preserved for five years after the representation ends[1]. Your state's rule may differ, so check it, but the practical point is the same: the migration must not leave gaps in the ledger history you may need to produce in an audit or a dispute.

  • Complete a three-way reconciliation of bank statement, trust ledger and client ledgers in the old system on the cutover date.
  • Bring opening balances per client into the new system and reconcile again before any new transactions.
  • Keep read-only access to the old system, or a full export of trust records, for your retention period.
  • Freeze trust transactions during the cutover window, or record them in both systems and reconcile both.

The migration timeline

  1. Clean up, weeks one to three

    Close finished matters, merge duplicate contacts and archive what will not move. Less data means fewer errors and a faster migration.

  2. Export and secure, week four

    Export through the vendor's supported tools and keep export files in one encrypted location that only the migration team can open.

  3. Test migration, weeks five and six

    Run a full test into a sandbox, validate it against the data map and log every difference.

  4. Fix and retest, week seven

    Correct the field mappings and run a second test. Repeat until counts and balances reconcile.

  5. Cutover, week eight

    Pick a quiet weekend, freeze changes in the old system, run the final migration, reconcile and switch.

  6. Close support, weeks nine and ten

    Hold daily check-ins with staff, keep an issues log and give each issue an owner.

  7. Close out

    Delete temporary export files, confirm archive access and sign off the project in writing.

Protect the data while it moves

Export files concentrate everything sensitive in one place, which makes them the most attractive target in the whole project. If your firm is subject to the California Consumer Privacy Act, statutory damages for a data breach run from $107 to $799 per consumer per incident, or actual damages if greater[4]. Many small firms fall below the CCPA's thresholds, which from 2025 include annual gross revenue above $26,625,000[4], but the confidentiality duty applies to every firm regardless of size.

CCPA statutory damages for a data breach, per consumer per incident, 2025
CCPA statutory damages for a data breach, per consumer per incident, 2025Comparison. Minimum: $107; Maximum: $799.$107MinimumMinimum: $107$799MaximumMaximum: $799CCPA statutory damages for a data breach, per consumer per incident, 2025Comparison. Minimum: $107; Maximum: $799.$107MinimumMinimum: $107$799MaximumMaximum: $799

Source: California Privacy Protection Agency, 2025[4]

Show the data
ItemValue
Minimum$107
Maximum$799
  • Use the vendors' secure transfer methods, not email attachments or personal cloud storage.
  • Give consultants time-limited access and remove it as soon as cutover is done.
  • Log who handled export files, where they were stored and when they were deleted.
  • Confirm in writing that the old vendor will delete your data after the archive period ends.

Prepare people, not only data

Train staff in the sandbox during the test migrations, using their own matters, so the first time they see the new system is not Monday morning after cutover. Give each role a one-page guide to the five tasks they do most often. Name a go-to person in each team who has had extra training, and tell everyone where to report problems.

Tell clients only what affects them. If portal logins, invoice formats or payment links change, send a short notice a week before cutover and again on the day, with a phone number for help. Clients do not need to know which vendor you chose; they need to know that their next invoice will look different and how to pay it.

Example: a cutover weekend

Example: a fictional nine-person immigration firm plans its cutover for a Friday evening. At five o'clock, staff stop entering time and trust transactions. The bookkeeper completes the trust reconciliation by seven, and the vendor runs the final migration overnight. On Saturday the office manager checks record counts against the data map, and each lawyer reviews their open matters and every deadline in the next sixty days. On Sunday the bookkeeper reconciles trust again in the new system. On Monday morning staff log in with a one-page guide, and a dedicated chat channel collects issues for the vendor and the office manager.

Example: the firm finds two problems on Saturday. A custom field for receipt numbers did not map, and some document folders flattened. Both are fixed before Monday because the team had planned time for exactly this.

After go-live: audit and adopt

  1. Week one: keep a daily issues list by owner; fix data problems first and training problems second.
  2. Week two: verify every deadline due in the next ninety days against the old system or the source documents.
  3. Month one: run the first billing cycle from the new system and compare it line by line with the previous cycle.
  4. Month three: review adoption, and look for staff rebuilding old workarounds instead of using the new features.
  5. Through the retention period: keep archive access to the old data as long as your retention policy requires.

Budget for the migration as a project, not a line item; see budgeting for legal technology. Trial the new system with a structured pilot before committing, check how consultations will sync with the new practice management calendar, and move client request tracking into a shared inbox if the new system supports it.

Frequently asked questions

How long does a practice management migration take?

For a small firm, plan on about two months from cleanup to go-live, including at least one full test migration. Larger data sets and trust accounting add time.

What data is hardest to migrate?

Calendar deadlines, custom fields, notes and trust ledger history are the usual problem areas. Validate each one by hand.

Should we migrate everything?

No. Close and archive finished matters you do not need in the new system, but keep accessible copies for your retention period.

What about trust account records?

Reconcile before and after cutover, bring client balances across, and keep the full trust history accessible for your state's retention period.

References

  1. American Bar Association (2026). Rule 1.15: Safekeeping Property, ABA Model Rules of Professional Conduct (archived copy) (opens in a new tab) โ†‘

  2. American Bar Association (2025). Rule 1.6: Confidentiality of Information, ABA Model Rules of Professional Conduct (archived copy) (opens in a new tab) โ†‘

  3. U.S. Census Bureau (2023). County Business Patterns 2023: U.S. detail file (cbp23us) (opens in a new tab) โ†‘

  4. California Privacy Protection Agency (2025). Updated Monetary Thresholds in CCPA (opens in a new tab) โ†‘

Book a demo

See Ava handle your calls.

Book a short demo. Weโ€™ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo