Data migration route
LEAP 365 to Actionstep migration
LEAP 365 and Actionstep are each a cloud practice management system. Both run a whole practice, so this is a full move, and the financial records set the timetable.
LEAP 365Cloud- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Emails: Carried across
- Calendar: Carried across
- Time and expenses: Carried across
- Trust money: Carried across
- Firm accounts: Carried across
- Intake: Carried across
- Billing: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
ActionstepCloud- 9 carried
- 3 mapped
- 2 to confirm
What moves
What moves from LEAP 365 to Actionstep
Each row is a kind of record LEAP 365 holds, whether Actionstep has a place for it, and what is planned. On this route nine kinds of record carry across, three kinds need mapping and two kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldThe same electronic matters as the desktop program. | Has a placeImported with a matter type, a status and the old number as File Reference. | Carried across |
| ContactsClients, other parties and referrers | HeldCards, as in the rest of LEAP. | Has a placeImported first, then linked to matters through a parties import. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldStored in the matter on LEAP’s servers. | Has a placeFiled in matter folders; not part of the spreadsheet import tool. | Carried across |
| EmailsEmails saved to matters or to the store | HeldOnly emails that were saved to a matter. | Has a placeSaved emails sit on the matter they were filed to. | Carried across |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a placeThe import tool has a file notes template. | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | Held in partCritical dates sit on the matter; anything further is confirmed in the analysis. | Has a placeAppointments have a place; the standard import templates do not cover them. | Carried across |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | Has a placeThe import tool has a tasks template. | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | Held | Has a placeTime entries and disbursements each have an import template. | Carried across |
| BillingInvoices, payments and debtor balances | Held | Has a place in partUnpaid invoices load as accounts receivable; older invoice history is confirmed in the analysis. | Carried with mapping |
| Trust moneyTrust or client account ledgers and balances | HeldLEAP’s in-built trust accounting. | Has a placeTrust balances load per matter through the trust accounts import. | Carried across |
| Firm accountsGeneral ledger, office account and payables | Held in partLEAP’s office accounting module, or Xero or MYOB through an integration. | Has a placeOpening balances are entered against the general ledger, or the books stay in Xero. | Carried across |
| Custom fieldsFields and record types the firm added itself | Held in partFields come mainly from LEAP’s matter types, with matter tables for repeating data. | Has a placeData collections are built per matter type before values are loaded. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldLEAP’s forms library and the firm’s own precedents. | Has a placeRebuilt as Actionstep templates with its merge fields. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldEnquiries are recorded in LEAP CRM. | Has a place | Carried across |
What the plans mean
- Carried across
- Actionstep has a place for this kind of record. It is loaded there and checked against LEAP 365.
- Carried with mapping
- Actionstep holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.
- Confirmed in the analysis
- We could not confirm this from the two products’ own material, so it is checked against your data before the plan is fixed.
The table states what the two products hold and what NewLaw plans for. It is not a promise that every record moves: that is settled against your own data in the analysis.
This kind of move
The whole practice moves, accounts included.
A move between two practice management systems is the widest kind there is. LEAP 365 and Actionstep each keep matters, contacts, documents, time and money in one place, but no two systems link those records the same way. In one, a client is a contact with a role on the matter. In another, every matter carries its own client card. Most of the analysis goes into those links, because a matter that arrives without its client or its documents is the first thing staff find.
The financial side decides the dates. Unbilled time, debtor balances and trust ledgers have to agree with LEAP 365’s own reports as at one day, and a new system usually wants them as opening balances, not as years of transactions. So the firm decides early how much history comes across as live records and how much is kept as reports. Matter and document loads can be repeated until they are right. The money is loaded once.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of LEAP 365 depends on its export tools and on what its maker provides on request, and that is confirmed during the analysis, before a date is set. The subscription to LEAP 365 is kept running until the checks on Actionstep are finished.
Where the data is now
Leaving LEAP 365
For a firm on LEAP 365 the migration is a LEAP migration. The browser is only the window; the records sit in LEAP’s cloud and are extracted from there. What differs is the firm’s working habits. Browser-first firms often have people on Macs or at home with no LEAP software installed, so nothing can be gathered from local machines.
One account, two front ends
LEAP 365 and LEAP Desktop open the same account. A firm with some staff in the browser and others on the desktop program has one set of data, and it is moved once. The matter list a partner sees in Chrome at home is the list the office sees, with the same matter numbers.
No local copies to rely on
With the browser version there is no installed program holding working copies of documents. Every file has to come from LEAP’s export. We test the export for completeness by counting documents per matter against what LEAP shows on screen, for a sample of large and small files, before the trial load.
Emails that were never saved
Only correspondence saved to a matter is in LEAP. Emails still sitting in a lawyer’s mailbox are not part of the export, whichever version of LEAP was used. If the firm wants them on the file in the new system, they are saved to the matter before the freeze or handled as a separate mailbox exercise.
Enquiries in LEAP CRM
LEAP CRM keeps enquiries that have not become matters, with a record of calls and emails and the conflict details taken at first contact. They are not in the matter list. The firm decides whether open enquiries move to the new system’s intake tool and whether old ones are kept at all.
Month end before cutover
Trust accounting in LEAP includes an end-of-month process with reconciliation and statements. Cutover is timed so that process has been completed in LEAP for the final period. The closing trust balance on each matter is then the figure loaded, and it reads the same in the browser, the desktop program and the reports.
Where it is going
Arriving in Actionstep
Actionstep has its own import tool, which takes spreadsheets in a set order: contacts, then matters, then the parties that join them. Tasks, time entries, trust balances, disbursements, unpaid invoices and file notes follow once the matters exist. None of it can start until the matter types, participant types and data collections have been built, because every imported row refers to them.
Matter types before any data
A matter’s type decides its workflow steps, its document folders, which party roles are available and which custom data it carries. So the first job is deciding how the old system’s matter types map to Actionstep’s, and building any that are missing. An imported matter also needs a step to sit at, usually the one closest to its old status.
Old numbers go to File Reference
Actionstep assigns its own Matter ID to each imported matter. The number the firm has always used goes into the File Reference field, which the quick search reads from the start of the reference. Staff can keep finding matters by the number printed on old letters and file covers.
Check before anyone edits
The import tool can roll back a load, but only while the imported records are untouched. Once someone edits them, the rollback no longer works. Trial loads are therefore checked straight away against the old system, and nobody outside the project works in the new records until the counts and balances agree.
Folders come from the matter type
Default document folders are set per matter type. There is no single folder list that applies across all matters. Before documents are loaded, the old folder names are mapped to the folders each matter type will have, so a conveyancing file and a litigation file each open with the layout the firm designed for them.
Opening balances can be locked
Trust balances load against matters, unpaid invoices load as accounts receivable, and general ledger opening balances are entered on the accounts list. An opening balance that has been locked cannot be edited afterwards. The figures are rehearsed on a trial load and agreed with the firm’s accountant before the lock is applied in the live system.
How NewLaw runs it
Four steps, in this order.
Trust money moves on this route, so the trust cutover gets a rehearsal of its own.
Analysis
We read what LEAP 365 holds and how its records link, then agree with you, field by field, where each piece will sit in Actionstep. Anything with no place there comes across as a note or stays behind, and you see which before the move.
Clean-up
Duplicate contacts and matters are merged where they can be identified, and inconsistent entries are put into one format, in LEAP 365, before extraction. It is not always possible to find every one, so some may carry across.
Trial load
The data is loaded into Actionstep as a trial and checked against LEAP 365: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in LEAP 365 are frozen for an agreed window, the data is collected a final time and Actionstep goes live over a weekend. The trust and financial cutover is rehearsed on a full trial load first, because it cannot be re-run the way a document load can. LEAP 365 is kept read only as the fall-back record.
Fixed price, agreed after the analysis. How NewLaw moves legal data
Start
Start this migration
Tell us what is in LEAP 365 and roughly how much of it. The first step is the analysis, and the price is fixed once it is done.
Step 1 of 5
What happens after you send it
- A free first call
We go through your answers with you and ask about anything they leave open.
- An analysis of what LEAP 365 holds
What is in it, how its records link, and where each piece would sit in Actionstep. Anything with no place there comes across as a note or stays behind, and you see which before the move.
- A fixed price in writing
Set after the analysis, so it reflects what is in your data. You have it before any work starts.
Beyond the data
Setting up Actionstep
Loaded data is not yet a working system. This is what NewLaw sets up in Actionstep, beyond the migration, so that people can work in it from the first day.
Most of the work in an Actionstep set-up is design. The firm decides what its matter types are, what steps each one moves through and what happens at each step. Templates, billing and trust settings are then built around those matter types. People are trained on their own workflows, since a generic demonstration looks little like the firm’s finished system.
Set-up decisions in Actionstep
- Matter types, with workflow steps and default document folders
- Participant types and data collections for each matter type
- Document and email templates rebuilt with Actionstep merge fields
- Trust accounts, chart of accounts and the optional Xero link
- System roles and data permissions for each group of staff
- Outlook add-in, divisions and the firm’s billing preferences
Questions
LEAP 365 to Actionstep: what firms ask
We only use LEAP in the browser. Is the move simpler?
The data work is the same, because the records are held by LEAP either way. There is less to do on the firm’s computers, as no program has to be uninstalled. Training can be easier where the new system is also used in a browser, since staff already work that way.
Can we keep using LEAP 365 to look things up afterwards?
Only for as long as the firm’s LEAP agreement allows access. That is read from the agreement before notice is given. If access ends on a fixed date, the records the firm must keep, including trust and billing history, are exported as reports and documents before then and stored where the firm can reach them.
Do our matter numbers change?
They need not. LEAP’s matter number is loaded as the matter number in the new system where that system accepts one. Documents are matched to matters on that number, so it has to be unique. Any duplicates found in the analysis are corrected in LEAP before extraction.
Do trust balances in LEAP 365 have a place in Actionstep?
Yes. Actionstep keeps trust ledgers. Trust balances load per matter through the trust accounts import. Balances are loaded by matter and agreed to the trust report from LEAP 365 as at the cutover date. That load cannot be re-run the way a document load can, so it is rehearsed on a full trial load first.
Does everything in LEAP 365 have a place in Actionstep?
Most of it does on paper. Notes and tasks could not be confirmed from the two products’ own material, so those are checked in the analysis. Anything that turns out to have no place in Actionstep is kept as a readable archive, and you see which before the move.
What has to be decided before LEAP 365 data is loaded into Actionstep?
Billing records, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Notes and tasks are confirmed in the analysis. The firm also sets the cutover date and how much financial history comes across as live records.
Other routes
Other routes from LEAP 365 and into Actionstep
Other destinations from LEAP 365
Other systems that move into Actionstep
Where to start
Before and after the move.
Choosing the system comes before a migration. Setting it up and putting AI to work come after.
Choose your systems
Technology stack selection
Decide which practice management system your firm runs, with the evidence and the cost beside it.
About four weeks for a firm of about 15 people. Fixed price, set after a free first call.
Move your data
Data migration
Your data is cleaned up before anything moves, then a trial load is checked against the old system.
Fixed price, agreed after the analysis.
Set up your new system
Implementation
Your new system set up around the way your firm works: configuration, document automation and training.
A small firm of 1 to 10 users typically takes 4 to 8 weeks. A mid-sized firm of 10 to 50 users takes 8 to 16 weeks.
Put AI to work
AI advisory and enablement
A small group of your people learn to use an approved AI tool on real work, under written rules.
Two to four weeks for a small first group. Fixed price, set after a free first call.
LEAP 365 and Actionstep are the names and marks of their owners, used here only to identify the two systems.
Moving from LEAP 365 to Actionstep?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.