Data migration route
LEAP Desktop data to SQLite
LEAP Desktop is a practice management system that runs on the desktop and keeps its data in its maker’s cloud, and SQLite is a store of data kept as files the firm holds. This is not a move to a new working system: the route writes out what LEAP Desktop holds and keeps it readable and open to queries.
LEAP DesktopDesktop and cloud- 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
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
SQLiteFiles- Templates: Kept as a readable archive
- 8 carried
- 3 mapped
- 2 to confirm
- 1 archived
What moves
What moves from LEAP Desktop to SQLite
Each row is a kind of record LEAP Desktop holds, whether SQLite has a place for it, and what is planned. On this route eight kinds of record carry across, three kinds need mapping, one kind has no place in SQLite and is archived and two kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldElectronic matters built on LEAP’s pre-configured matter types. | Has a placeA matters table keyed by matter number. | Exported in full |
| ContactsClients, other parties and referrers | HeldHeld as cards and attached to matters. | Has a placeContacts and their roles on matters as linked tables. | Exported in full |
| DocumentsFiles stored in or linked from the system | HeldDocuments, correspondence, searches and forms are stored in the matter. | Has a place in partListed in a table; the files themselves stay in folders beside the database. | Exported with mapping |
| EmailsEmails saved to matters or to the store | HeldSaved to the matter through the Outlook integration. | Has a place in partAs message files in folders, indexed in a table. | Exported with mapping |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a placeA notes table linked to matters. | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | Held in partCritical dates on matters; other calendar records are confirmed in the analysis. | Has a placeA table of dated entries, with no calendar view. | Exported in full |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | Has a placeA table of tasks and their status at the final date. | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | HeldTimesheet entries and automatic time recording. | Has a placeA table of time and expense entries. | Exported in full |
| BillingInvoices, payments and debtor balances | Held | Has a placeInvoice and receipt tables; invoice PDFs kept as files. | Exported in full |
| Trust moneyTrust or client account ledgers and balances | HeldIn-built trust accounting, including controlled money. | Has a placeTrust transactions as rows, for look-up and not for accounting. | Exported in full |
| Firm accountsGeneral ledger, office account and payables | Held in partAn office accounting module, with integrations to Xero and MYOB. | Has a placeLedger journals as rows, where the source held them. | Exported in full |
| Custom fieldsFields and record types the firm added itself | Held in partMatter tables and custom matter types; fields otherwise come from LEAP’s matter types. | Has a placeColumns added to the table they belonged to. | Exported with mapping |
| TemplatesPrecedents, document templates and automation | HeldLEAP’s forms library, the firm’s own precedents and a Clause Library. | No placePrecedent files are kept in folders, not in the database. | Kept as a readable archive |
| IntakeLeads, enquiries, intake forms and pipelines | HeldLEAP CRM records enquiries and converts them to matters. | Has a placeAn enquiries table, where the source tracked them. | Exported in full |
What the plans mean
- Exported in full
- SQLite has a place for this kind of record. It is loaded there and checked against LEAP Desktop.
- Exported with mapping
- SQLite 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
- SQLite has no place for it. It is exported in a format that opens without LEAP Desktop 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
Not a new system. A complete copy the firm can query.
Writing LEAP Desktop out to SQLite 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 Desktop 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 Desktop is hosted by its maker and SQLite 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 Desktop will release depends on its export tools, and that is confirmed in the analysis.
Where the data is now
Leaving LEAP Desktop
LEAP runs on the PC but keeps the firm’s data in its own cloud, so there is no database in the office to copy. The move is planned around the export: what LEAP provides, in what format, and by when. A firm leaving LEAP is also replacing things LEAP supplied, such as its matter types, court forms and the forms library.
Nothing to copy from the office
The desktop program synchronises with LEAP’s servers. What sits on the PC is a working copy, not the firm’s record. A complete set of matters, cards, documents and accounting data has to come from LEAP’s side. We ask early how that export is delivered, and check the first copy against LEAP’s own reports before relying on it.
Cards, and the same person twice
LEAP calls a contact a card. A card is attached to a matter, and the same person can end up with several: once as a client, again as the other side on someone else’s matter. Cards are compared on name, address, email and phone, and merged in LEAP before extraction where they are clearly one person.
Matter types came from LEAP
A matter’s detail fields come from its LEAP matter type, and LEAP maintains more than a thousand of them. The destination will not have the same types or the same fields. Each type the firm really uses is mapped, and fields with no home are brought across as a note or left behind, as agreed beforehand.
Forms stay, precedents are rebuilt
Court and government forms in LEAP come from LEAP’s own library and stay with it. The firm’s own precedents move. Their merge fields are LEAP’s, so each one is replaced with the new system’s equivalent. Clause Library content is listed too, because it is easy to forget until someone goes looking for a clause.
Office accounts: module or package
Trust accounting is inside LEAP. Office accounting may be in LEAP’s office module or in Xero or MYOB through the integration. We establish which before anything else financial is planned, because it decides whether the firm’s own books are part of the move or only the trust ledgers and debtor balances.
Where it is going
Arriving in SQLite
A SQLite archive suits a firm that wants the old system’s records kept, seldom consulted, and free of any server or subscription. Everything structured goes into one file. That simplicity moves the responsibility elsewhere: the file has no security of its own and no administrator watching it, so where it is stored and who can reach it are the real decisions.
One file, kept with the archive
Matters, contacts, time, invoices and trust transactions become tables in a single file. It is stored with the firm’s closed-matter records and can be copied like any document. A checksum recorded when the file is finalised lets anyone confirm, years later, that the copy they hold has not been altered, and the firm decides whether to keep one.
No logins inside the file
SQLite has no users or passwords. Anyone who can open the file can read every client’s ledger. Protection comes from where it is kept, such as a restricted folder or an encrypted volume, and that choice is the firm’s. It can suit an archive consulted by two people, and it is said plainly so nobody assumes otherwise.
Built for reading, not sharing
Only one program can write to the file at a time, and SQLite’s authors point people to a client/server database where many users share data over a network. A finished archive never meets that limit. It is the reason SQLite is used here for records that are closed and not for anything staff still update.
Documents stay outside it
Documents remain ordinary files in matter folders, and a table in the database lists each one with its matter, title, dates and path. Keeping them as files means they open with a double-click and can be handed to a client. The table is how a file is found by matter number instead of by guessing its name.
Someone has to open it
SQLite publishes its own command-line program for opening a database file, and other tools read the format too. None of that helps if nobody remembers how. Saved queries for the usual look-ups and a short note on which tool to use can sit in the same folder as the file, and the firm decides what it needs.
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 Desktop holds, table by table, and agree with you what the copy in SQLite must be able to answer later. Everything LEAP Desktop 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 SQLite as a trial and checked against LEAP Desktop: record counts, totals where LEAP Desktop 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 Desktop, the export is run a final time and checked again. There is nothing to go live. LEAP Desktop 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 Desktop 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 Desktop holds
What is in it, how its records link, and where each piece would sit in SQLite. 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
SQLite 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.
There is nothing to install on a server and nothing to license. The work is in making the file usable and safe to keep: naming it, documenting its tables, storing it where the firm’s records policy says archives go, and checking that a member of staff can open it and find a matter. Whether a second copy is held somewhere separate is the firm’s call.
What is agreed and set up
- File name, storage location and whether a second copy exists
- Whether a checksum is recorded for later verification
- Saved queries for matter, ledger and document look-ups
- Which tool staff will use to open the file
- Who may open the folder the file sits in
- Retention period and destruction date noted beside the file
Questions
LEAP Desktop to SQLite: what firms ask
Is LEAP Desktop different from LEAP 365 for a migration?
No. They are two ways into the same LEAP account, and the data is the same whichever one staff use. One migration covers both. The only practical difference is on the PCs: the desktop program and its Office integration are removed once the firm no longer needs read-only access.
What happens to our closed matters?
They can move in full, move as documents only, or stay in the archive. A common pattern is that open matters and recent closed ones move as full records, and older files come across as documents attached to a matter shell. How long LEAP access continues after notice is read from the firm’s agreement.
Will trust history come across?
Balances move. Each matter’s trust balance is loaded as an opening balance and checked against LEAP’s trust reports at the cutover date. The transactions behind those balances normally stay in the old record or in exported reports, because few systems accept another system’s trust history as live ledger entries.
Does the copy in SQLite hold trust ledgers from LEAP Desktop?
Yes. Trust transactions as rows, for look-up and not for accounting. Trust ledgers are written out with the rest, and counts and totals are agreed to the reports in LEAP Desktop as at the export date.
What happens to records SQLite has no place for?
On this route that is templates. They are exported from LEAP Desktop 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 Desktop is written out to SQLite?
Documents, emails and custom fields 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 Desktop and into SQLite
Other destinations from LEAP Desktop
Other systems that move into SQLite
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 Desktop and SQLite are the names and marks of their owners, used here only to identify the two systems.
Moving from LEAP Desktop to SQLite?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.