Data migration route
LEAP 365 data to Microsoft SQL Server
LEAP 365 is a cloud practice management system, and Microsoft SQL Server is a database on a server the firm runs. This is not a move to a new working system: the route writes out what LEAP 365 holds and keeps it readable and open to queries.
LEAP 365Cloud- Matters: Exported in full
- Contacts: Exported in full
- Calendar: Exported in full
- Time and expenses: Exported in full
- Billing: Exported in full
- Trust money: Exported in full
- Firm accounts: Exported in full
- Intake: Exported in full
- Documents: Exported with mapping
- Emails: Exported with mapping
- Custom fields: Exported with mapping
- Templates: Exported with mapping
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
Microsoft SQL ServerServer- 8 carried
- 4 mapped
- 2 to confirm
What moves
What moves from LEAP 365 to Microsoft SQL Server
Each row is a kind of record LEAP 365 holds, whether Microsoft SQL Server has a place for it, and what is planned. On this route eight kinds of record carry across, four 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 placeA table of matters linked to clients, parties and fee earners. | Exported in full |
| ContactsClients, other parties and referrers | HeldCards, as in the rest of LEAP. | Has a placePeople and companies, with their roles on each matter. | Exported in full |
| DocumentsFiles stored in or linked from the system | HeldStored in the matter on LEAP’s servers. | Has a place in partAs files in folders with an index table; storing files in the database is possible. | Exported with mapping |
| EmailsEmails saved to matters or to the store | HeldOnly emails that were saved to a matter. | Has a place in partAs message files with an index table, or as rows of header fields. | Exported with mapping |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a placeRows of text linked to matters and contacts. | 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 placeRows of appointments and key dates; nothing displays them as a calendar. | Exported in full |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | Has a placeRows with assignee, due date and status. | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | Held | Has a placeTime and expense rows with rates and billed status. | Exported in full |
| BillingInvoices, payments and debtor balances | Held | Has a placeInvoices, lines and receipts as rows; invoice PDFs kept as files. | Exported in full |
| Trust moneyTrust or client account ledgers and balances | HeldLEAP’s in-built trust accounting. | Has a placeTransactions and balances for look-up; it is not a trust accounting system. | Exported in full |
| Firm accountsGeneral ledger, office account and payables | Held in partLEAP’s office accounting module, or Xero or MYOB through an integration. | Has a placeGeneral ledger journals and balances, where the source held them. | Exported in full |
| 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 placeAs added columns, or a table of field names and values. | Exported with mapping |
| TemplatesPrecedents, document templates and automation | HeldLEAP’s forms library and the firm’s own precedents. | Has a place in partPrecedent files can be stored; automation does not run here. | Exported with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldEnquiries are recorded in LEAP CRM. | Has a placeEnquiry rows, where the source recorded them. | Exported in full |
What the plans mean
- Exported in full
- Microsoft SQL Server has a place for this kind of record. It is loaded there and checked against LEAP 365.
- Exported with mapping
- Microsoft SQL Server 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
Not a new system. A complete copy the firm can query.
Writing LEAP 365 out to Microsoft SQL Server is not a migration into a new working system. Nobody will open a matter there on Monday morning. The aim is a complete, faithful copy that can be queried and reported on after the old system is gone. So the rules change. Nothing is cleaned or merged unless the firm asks, because an archive should show the records as they were. Every table and field is carried, including those a new system would have had no place for.
What makes an archive usable is the description that goes with it. The export is delivered with a plain account of each table: what it holds, how it joins to the others, what the codes mean. Record counts and financial totals are agreed to the reports in LEAP 365 as at the export date, so the archive can stand as the record. Documents are exported beside the data with a table linking each file to its matter. Access is restricted, since the archive holds everything the live system did.
LEAP 365 is hosted by its maker and Microsoft SQL Server sits on equipment the firm controls. The data leaves a service that was backed up for the firm and arrives somewhere the firm must back up itself, so backup and access are arranged before the export is copied in. What LEAP 365 will release depends on its export tools, and that is confirmed in the analysis.
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 Microsoft SQL Server
There are two ways to put a retired system into SQL Server, and they suit different firms. The old system’s own database can be restored as it is. Or the data can be loaded into a new set of tables designed to be read by people. The first is quicker and harder to use. Which suits is worked out in the analysis, and the choice is the firm’s.
Restored copy or rebuilt schema
Where the old practice system already kept its data in SQL Server, a backup can be restored onto a new server. The tables keep the vendor’s names and codes, which can be cryptic, and reading them takes someone who knows that product’s database. A rebuilt schema uses plain names such as Matter and TrustTransaction.
No screens come with it
A database has no matter screen. Someone has to ask it questions in SQL or through a reporting tool. Saved views can be set up for the things the firm will really look up: a matter with its parties, its ledger, its time entries and its list of documents. Which are worth having is agreed in the analysis.
Documents sit beside the database
Files are normally kept in folders on the same server, with a table recording each document’s matter, title, dates and path. Storing the files inside the database is possible but makes it far larger. On the Express edition, the cap on database size rules that out for most firms’ document stores.
The edition follows the size
A firm’s tables may fit within the Express limit once documents are kept outside the database. A long trust and time history at a larger firm may not. The size of the source data is measured in the analysis, and the edition is chosen from that figure with the firm’s IT provider.
Backups and a test restore
An archive that is never backed up is one disk failure from gone. Backups belong to the firm’s IT provider: a full one once the load is finished, and a schedule if anything is still being added. It is worth restoring one to a second machine as a test, because a backup that has never been restored is only a hope.
How NewLaw runs it
Four steps, in this order.
This route produces an archive, not a working system, so the steps are about completeness and proof.
Analysis
We read what LEAP 365 holds, table by table, and agree with you what the copy in Microsoft SQL Server must be able to answer later. Everything LEAP 365 holds is in scope unless you take it out.
Clean-up, if you want it
An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.
Trial export
The data is written to Microsoft SQL Server as a trial and checked against LEAP 365: record counts, totals where LEAP 365 holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.
Final export
After the last day of work in LEAP 365, the export is run a final time and checked again. There is nothing to go live. LEAP 365 is kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.
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 Microsoft SQL Server. 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
Microsoft SQL Server is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.
Standing up SQL Server as an archive is IT work shared with the firm’s provider. A server or instance is chosen, logins are created for the few people who need to read the data, and nobody is given rights to change it. Views and a handful of reports are built for the common questions, and the IT provider owns the backup routine.
What is agreed and set up
- Server, instance and edition agreed with the IT provider
- Read-only logins and roles for named staff
- Views for matter, ledger, time and document look-ups
- Backup schedule and who tests a restore
- Plain names and descriptions for tables and columns
- Excel or Power BI connected for reporting
Questions
LEAP 365 to Microsoft SQL Server: 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.
Does the copy in Microsoft SQL Server hold trust ledgers from LEAP 365?
Yes. Transactions and balances for look-up; it is not a trust accounting system. Trust ledgers are written out with the rest, and counts and totals are agreed to the reports in LEAP 365 as at the export date.
Does everything in LEAP 365 have a place in Microsoft SQL Server?
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 Microsoft SQL Server is kept as a readable archive, and you see which before the move.
What has to be decided before LEAP 365 is written out to Microsoft SQL Server?
Documents, emails, custom fields and templates are exported with mapping, so each mapping is agreed with you first. Notes and tasks are confirmed in the analysis. The firm also decides who may open the archive and how long it is kept.
Other routes
Other routes from LEAP 365 and into Microsoft SQL Server
Other destinations from LEAP 365
Other systems that move into Microsoft SQL Server
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 Microsoft SQL Server are the names and marks of their owners, used here only to identify the two systems.
Moving from LEAP 365 to Microsoft SQL Server?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.