LEAP migration for law firms
Moving your firm off LEAP? NewLaw migrates law firms off LEAP as a fixed-price service, whether you are going to Clio, Actionstep, Smokeball or another system. Before anything is imported we analyse your LEAP data, de-duplicate it and clean it, so fewer duplicates and errors follow you into the new system.
This page covers what to check before you decide, what moves and what does not, and how long it takes.
Choose your path
Where are you moving to?
LEAP to Clio
What Clio says can be migrated from LEAP, what cannot, and the work around the import.
Read the Clio pathLEAP to Actionstep
How LEAP data gets into Actionstep, what to decide about accounts, and how long implementation takes.
Read the Actionstep pathLEAP to Smokeball
What Smokeball's import tool brings in, what to confirm with Smokeball, and what to prepare.
Read the Smokeball path
Another system, or not decided yet?How we migrate legal data Technology stack selection
Before you decide
Five things to check before you give notice.
What a move off LEAP has to cover
LEAP describes itself as an all-in-one, cloud-based legal solution. Its Australian website lists matter management, email management, document assembly and management, legal accounting with in-built trust accounting, court and government forms, legal searching, a client portal and a Microsoft 365 integration. A move has to account for each of those parts your firm uses, not only the matter list. Source: LEAP's Australian website (opens in a new tab)
Your agreement
Read your LEAP agreement for its term, renewal date and notice period before you set any date. The end of the agreement is a planning constraint, not a migration date: the new system has to be chosen, set up and tested first.
How your data comes out
Before you give notice, ask LEAP how your data and documents will be exported, in what format and by when, and check the answer against your own agreement. The migration is planned around that export.
What you use in LEAP today
List the parts of LEAP your firm relies on: its matter types, the court and government forms it supplies, your own precedents, searches, trust accounting, the client portal and the Microsoft 365 integration. Each one needs an answer in the new system, and each answer should be checked, not assumed.
What has to be kept
Decide what history the firm must be able to reach after the move, for how long, and who needs to reach it. Full billing and trust transaction history usually stays in a read-only copy of the old system or in exported reports, so plan how that archive will be kept.
Whether to move at all
Staying is a real option. If the decision is still open, technology stack selection tests LEAP against the same requirements and the same three-year cost as the alternatives, and says so if the evidence favours staying.
What moves and what does not
Balances and records move. History stays in the archive.
This is the usual position. The new system sets the boundary: what it can hold decides what is imported, so the exact list differs for Clio, Actionstep and Smokeball.
Usually moves
- Clients and contacts, with their addresses, phone numbers and email addresses
- Matters, with their client, the other parties and the people responsible
- Documents and emails filed to matters, as files in the matching matter
- Unbilled time and disbursements (work in progress)
- Outstanding invoices or balances
- Trust and office account opening balances
- Your own precedents, as base templates
Usually stays in the archive
- Full billing history and paid invoices
- Trust and office transaction history before the opening balances
- The general ledger and accounts payable
- Data marked as deleted, audit detail and document version history
- Fields with no matching place in the new system, which are generally brought across as a note or left behind
- The automation inside precedents: merge fields are rebuilt in the new system
Before anything is imported
Analysis, de-duplication and clean-up come first.
An import brings across the records it is given. Most of the work in a good migration happens before it.
What we analyse
How many contacts, matters and documents there are, and how many matters are open or closed. Which fields and matter types the firm actually uses. Whether every matter has a client and every document belongs to a matter. Whether work in progress, outstanding balances and trust balances in the data agree with LEAP's own reports.
What we de-duplicate
Contacts and matters that were entered more than once: the same person saved as a client on one matter and as the other party on another, or the same company under two spellings. Duplicates are merged in the LEAP data before it is extracted. We aim to remove them all. It is not always possible, so some may still carry across.
What we clean
Inconsistent and legacy-format entries, such as names, addresses and phone numbers stored in different ways. Matter references that documents are matched on, which have to be unique. Old fields that need a place in the new system's structure. Each is fixed or mapped before the trial load.
Why it decides whether the new system is trusted on day one
On the first morning a lawyer searches for a client. If three versions of that client come up, a conflict check can miss a match, the client's matters are split between the records, and nobody knows which one to update.
If a trust balance does not match the day before, the accounts team stops relying on the new system and keeps a spreadsheet beside it.
People decide in the first week whether the new system is the record of the firm. Clean data is what lets them decide yes.
How we run it
Five steps, in this order.
Analyse
We look at what is in your LEAP data and at what the new system can hold, then give you a plan and a fixed price.
De-duplicate and clean
Duplicates are merged and inconsistent entries fixed in the source data, before it is extracted.
Map
Each field in the old data is mapped to its place in the new system, including custom fields and the records that do not fit neatly.
Trial load and check
A full test migration. We check it against LEAP on record counts, financial totals, the links between clients, matters and documents, and document dates. Your people check it too.
Cut over
A short freeze on changes in LEAP, a final collection of the data, and the move over a weekend: close off on Friday, start in the new system on Monday.
Document and matter migration can be run again, so each trial load is checked until it agrees with LEAP. The trust and financial cutover cannot be re-run in the same way. It gets a rehearsal on a full trial load, a freeze window and a go or no-go decision beforehand.
After the cutover the old system is kept as the read-only record of what was not imported, where your LEAP agreement allows it. That is one reason to read the agreement first.
How long it takes
How long a LEAP migration takes
It depends on five things:
- how many matters and documents there are
- how much clean-up the data needs
- how many trial loads it takes before the checks agree
- which financial balances move, and when your accounts can close off
- the new system's own set-up timetable, and your people's time to check the test migration
As a guide to the whole project, setting up a new practice management system typically takes four to eight weeks for a firm of up to 10 users, eight to 16 weeks for 10 to 50 users, and three to six months for a larger or multi-office firm. The cutover itself is planned for a single weekend.
Questions
Moving from LEAP: what firms ask
Answers for the partner or practice manager planning the move.
Can NewLaw migrate our firm from LEAP?
Yes. NewLaw migrates law firms off LEAP as a fixed-price service, and the destination can be Clio, Actionstep, Smokeball or another practice management system. The work covers analysing the LEAP data, de-duplicating and cleaning it, mapping it to the new system, a trial load that is checked against LEAP, and the cutover.
What data moves from LEAP to a new system?
Usually clients and contacts, matters and their parties, documents and emails filed to matters, unbilled time and disbursements, outstanding invoices or balances, trust and office opening balances, and your own precedents as base templates. The new system sets the boundary: what it can hold decides what is imported, so the exact list differs by system.
Does our trust and billing history move?
As a rule, balances move and history stays. Work in progress, outstanding invoices and opening balances for trust and office accounts are brought across. Full billing history, paid invoices and trust transaction history before the opening balances usually stay in a read-only copy of the old system or in exported reports, so plan how that archive will be kept and who can reach it.
Do our precedents and forms move from LEAP?
Your own precedents come across as base templates, and their automation is rebuilt in the new system, because merge fields written for one system do not work in another. The court and government forms LEAP supplies are part of LEAP's service, so list the forms your team uses and decide how each will be produced after the move.
How long does a LEAP migration take?
It depends on how many matters and documents there are, how much clean-up the data needs, how many trial loads it takes before the checks agree, which financial balances move, and the new system's own set-up timetable. As a guide to the whole project, setting up a new practice management system typically takes four to eight weeks for a firm of up to 10 users, eight to 16 weeks for 10 to 50 users, and three to six months for a larger or multi-office firm. The cutover itself is planned for a single weekend.
Will the firm have to stop work during the move?
The cutover is planned for a weekend: close off on Friday and start in the new system on Monday. There is a short freeze on changes in LEAP beforehand so the final collection of data is complete. Anything entered in the old system after that final collection has to be entered again in the new one.
Why clean and de-duplicate the data before moving?
Because an import brings across whatever it is given. If the same client exists three times in LEAP, the client exists three times in the new system, a conflict check can miss a match and the client's matters are split between the records. Merging duplicates and fixing inconsistent entries in the source data, before it is extracted, is what lets people rely on the new system from the first day. We aim to remove every duplicate, it is not always possible, and some may still carry across.
Which system should we move to from LEAP?
That depends on your firm's requirements, and it is a separate decision from the move itself. If you have chosen, see our pages on LEAP to Clio, LEAP to Actionstep and LEAP to Smokeball. If you have not, the stack builder gives a starting point in six questions, and technology stack selection is the full fixed-price comparison, with LEAP assessed alongside the alternatives.
How is a LEAP migration priced?
It is fixed price. Every firm's data is different, so the price is set after a free first call and a look at what is in your LEAP data: the number of matters and documents, how much clean-up it needs and what the new system has to hold. You get the price in writing before any work starts.
Two ways to start
Still deciding where to move?
Choose the system before you plan the move, and see where AI fits once your data is in it.
Choose your systems
Technology stack selection
- What you get
- A requirements register, a costed comparison of the shortlisted systems, the vendors' offers in writing and one written recommendation.
- How long
- About four weeks for a firm of about 15 people. 12 to 16 weeks for a larger firm with a separate document system.
- Pricing
- Fixed price. Every firm is different, so the price is set after a free first call.
- What happens next
- A free first call, then a written fixed-price proposal. Work starts on a date agreed when you accept.
How big is your team?
Step 1 of 6 in the stack builder
Choosing an answer opens the stack builder at step 2 with your answer kept.
Put AI to work
AI advisory and enablement
- What you get
- Guided working sessions on your real tasks, an AI use policy your firm approves, a register of tested tasks and a reference library you own.
- How long
- Two to four weeks for a small first group. 12 to 16 weeks for a larger firm, alongside technology stack selection.
- Pricing
- Fixed price. Every firm is different, so the price is set after a free first call.
- What happens next
- A free first call, then a written fixed-price proposal. The first session is booked when you accept.
How is your firm currently using AI?
Question 1 of 7 in the readiness assessment
Choosing an answer opens the AI readiness assessment at question 2 with your answer kept.
The two are often run together as one engagement.
Planning a move off LEAP?
Tell us where you are moving and roughly how many matters you have. A free first call, then a fixed price in writing.
We reply within one business day.