Data migration route
LEAP 365 to Box migration
LEAP 365 is a cloud practice management system, and Box is cloud file storage. Documents move into a folder for each client and matter, and the data behind them is kept as an export.
LEAP 365Cloud- Documents: Carried across
- Emails: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
BoxCloud- Matters: Kept as a readable archive
- Contacts: Kept as a readable archive
- Calendar: Kept as a readable archive
- Time and expenses: Kept as a readable archive
- Billing: Kept as a readable archive
- Trust money: Kept as a readable archive
- Firm accounts: Kept as a readable archive
- Intake: Kept as a readable archive
- 1 carried
- 3 mapped
- 2 to confirm
- 8 archived
What moves
What moves from LEAP 365 to Box
Each row is a kind of record LEAP 365 holds, whether Box has a place for it, and what is planned. On this route one kind of record carries across, three kinds need mapping, eight kinds have no place in Box and are archived 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. | No placeA matter is a folder, optionally with metadata; there is no matter record. | Kept as a readable archive |
| ContactsClients, other parties and referrers | HeldCards, as in the rest of LEAP. | No place | Kept as a readable archive |
| DocumentsFiles stored in or linked from the system | HeldStored in the matter on LEAP’s servers. | Has a placeFiles and folders, named and dated as they are loaded. | Carried across |
| EmailsEmails saved to matters or to the store | HeldOnly emails that were saved to a matter. | Has a place in partAs .msg or .eml files in the matter folder. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a place in partAs documents in the matter folder, not as a notes record. | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | Held in partCritical dates sit on the matter; anything further is confirmed in the analysis. | No place | Kept as a readable archive |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | No place | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | Held | No place | Kept as a readable archive |
| BillingInvoices, payments and debtor balances | Held | No place | Kept as a readable archive |
| Trust moneyTrust or client account ledgers and balances | HeldLEAP’s in-built trust accounting. | No place | Kept as a readable archive |
| Firm accountsGeneral ledger, office account and payables | Held in partLEAP’s office accounting module, or Xero or MYOB through an integration. | No place | Kept as a readable archive |
| 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 place in partMetadata templates can hold fields such as matter number and client. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldLEAP’s forms library and the firm’s own precedents. | Has a place in partPrecedents load as ordinary files; no document automation. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldEnquiries are recorded in LEAP CRM. | No place | Kept as a readable archive |
What the plans mean
- Carried across
- Box has a place for this kind of record. It is loaded there and checked against LEAP 365.
- Carried with mapping
- Box 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.
- Kept as a readable archive
- Box has no place for it. It is exported in a format that opens without LEAP 365 and handed to the firm as a read-only archive.
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
Out of the system, into folders the firm can read.
File storage has folders and files and nothing else. Moving from LEAP 365 into Box means turning matters into a folder tree, usually client, then matter, then the folders used inside it. The naming rule is agreed first, because it is hard to change once thousands of folders exist: whether the matter number leads, how closed matters are separated, what happens to characters Box does not allow in a name.
Everything that is not a document needs somewhere to go. Contacts, notes, time, invoices and trust ledgers have no place in a folder, so they are exported as spreadsheets and reports and stored alongside, often as a summary file in each matter folder and a full set in an archive area. Firms choose this route to keep a readable copy of a system they are retiring, or as a staging step. The export is checked either way: folders against matters, files against the document register in LEAP 365.
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 Box 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 Box
Loading a firm’s files into Box means deciding the folder tree and its owners first, because permissions follow the tree. Box has no matter record. A matter is a folder, and anything else the firm knew about it, such as the matter number, client or status, survives only in the folder name or in metadata fields set up before the load.
Decide who owns the top level
Box’s own planning guidance sets out two models: users create their own top-level folders, or administrators own them all and invite people in. For matter files most later decisions depend on this one, including who can share outside the firm and whose storage allowance the files count against.
Restricted matters go near the top
Access in Box only flows downward. A person who can open a client folder can open every matter under it, and a subfolder cannot be hidden from them. Matters behind an information barrier therefore need their own top-level folders, and the list of those matters is agreed before the structure is built.
Names Box will not accept
Box rejects a slash or backslash anywhere in a file or folder name, and spaces at the start or end. Files from older systems and from Macs often have both. They are renamed by rule before loading and the firm receives the list, so that a document cited by its old name can still be found.
Matter details become metadata
A metadata template can hold the matter number, client name, practice area and closed date against each matter folder. The template has to exist before the files arrive so the values can be written during the load. Without it, the folder name is the only place that information lives.
File size follows the owner’s plan
The largest file Box accepts depends on the plan of whoever owns the folder. Litigation matters with video or forensic images are where this bites. Oversized files are found in the analysis, and the firm chooses between a higher plan and keeping those files somewhere else.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Box on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what LEAP 365 holds and how it is organised, then agree with you where each kind of record will sit in Box. Anything with no place there stays behind or is archived, and you see which before the move.
Clean-up
Duplicate clients, matters and folders are merged where they can be identified, and naming is put into one format, before anything is copied. It is not always possible to find every one, so some may carry across.
Trial load
A trial is loaded into Box and checked against LEAP 365: record and file counts, the links between records, document dates, and a sample opened by your own people. Exceptions are listed for you to decide.
Cutover
There is no financial cutover on this route. After a short freeze on changes in LEAP 365, a final pass over a weekend picks up what changed since the trial. 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 Box. 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
Structure, permissions and handover
Box is storage, not an application, so there is no product to configure. What is agreed and set up is the folder structure, who can open what, and how the result is handed to the firm.
Most of a Box set-up is governance. The folder tree, the groups that are invited into it and the rules on sharing outside the firm are decided and built before any file is loaded. After the load, staff need Box Drive on their PCs and a short written guide to where a new matter folder is created and who creates it.
What is agreed and set up
- Top-level folder structure and who owns each folder
- Groups for teams, mapped to collaborator roles
- Metadata template for matter number, client and status
- Shared link defaults and rules for external collaborators
- Box Drive installed and signed in on each PC
- Version limits and retention agreed with the firm’s records policy
Questions
LEAP 365 to Box: 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 Box?
No. Box does not keep trust ledgers. Trust records from LEAP 365 are exported as ledgers and statements that open without it, and the firm settles where its trust accounting runs from the cutover date before the move is planned.
What happens to records Box has no place for?
On this route that is matters, contacts, calendar entries, time entries, billing records, trust ledgers, the firm’s accounts and intake records. They are exported from LEAP 365 in formats that open without it, spreadsheets and PDFs, and handed to the firm as a read-only archive. You see the list before the move.
What has to be decided before LEAP 365 data is loaded into Box?
Emails, 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 decides which closed matters and how many versions of a document are in scope.
Other routes
Other routes from LEAP 365 and into Box
Other destinations from LEAP 365
Other systems that move into Box
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 Box are the names and marks of their owners, used here only to identify the two systems.
Moving from LEAP 365 to Box?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.