Data migration route
LawCloud data to SQLite
LawCloud is a cloud practice management system, 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 LawCloud holds and keeps it readable and open to queries.
LawCloudCloud- Matters: Exported in full
- Notes: Exported in full
- Time and expenses: Exported in full
- Billing: Exported in full
- Trust money: Exported in full
- Firm accounts: Exported in full
- Documents: Exported with mapping
- Emails: Exported with mapping
- Contacts: Confirmed in the analysis
- Calendar: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Templates: Confirmed in the analysis
- Intake: Confirmed in the analysis
SQLiteFiles- 6 carried
- 2 mapped
- 6 to confirm
What moves
What moves from LawCloud to SQLite
Each row is a kind of record LawCloud holds, whether SQLite has a place for it, and what is planned. On this route six kinds of record carry across, two kinds need mapping and six kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldOrganised as cases, with every activity logged to the case record. | Has a placeA matters table keyed by matter number. | Exported in full |
| ContactsClients, other parties and referrers | To be confirmed | Has a placeContacts and their roles on matters as linked tables. | Confirmed in the analysis |
| DocumentsFiles stored in or linked from the system | HeldDocuments are stored and searched within the case. | 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 | HeldEmails are logged to the case record. | Has a place in partAs message files in folders, indexed in a table. | Exported with mapping |
| NotesFile notes, matter notes and contact notes | Held in partPhone calls are logged against the case. | Has a placeA notes table linked to matters. | Exported in full |
| CalendarAppointments, court dates and deadlines | To be confirmed | Has a placeA table of dated entries, with no calendar view. | Confirmed in the analysis |
| 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 | HeldBuilt-in 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 | HeldClient accounting under Law Society of Scotland and SRA accounts rules. | Has a placeTrust transactions as rows, for look-up and not for accounting. | Exported in full |
| Firm accountsGeneral ledger, office account and payables | HeldSolicitors’ accounts software in the same system as case management. | Has a placeLedger journals as rows, where the source held them. | Exported in full |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a placeColumns added to the table they belonged to. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | To be confirmed | No placePrecedent files are kept in folders, not in the database. | Confirmed in the analysis |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | Has a placeAn enquiries table, where the source tracked them. | Confirmed in the analysis |
What the plans mean
- Exported in full
- SQLite has a place for this kind of record. It is loaded there and checked against LawCloud.
- 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.
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 LawCloud 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 LawCloud 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.
LawCloud 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 LawCloud will release depends on its export tools, and that is confirmed in the analysis.
Where the data is now
Leaving LawCloud
A LawCloud firm does not hold its own database: LawWare hosts it. Leaving starts with a request for a copy of the data and documents, and with working out which edition the firm is actually on. Because legal accounts sit in the same system as the cases, the client ledgers and the case files leave together and have to agree with each other on arrival.
Hosted LawWare, by another name
LawCloud is LawWare’s Enterprise edition run from LawWare’s hosting. Staff may call it LawWare, LawCloud or just the case management system. We confirm the edition and version with the vendor at the start, because LawWare describes New LawWare as a complete redesign of version 4, and the extraction has to match the version in use.
The case record logs everything
Every phone call, document, email and time entry is written to the case record as an activity. That log is the running history of the file. Systems that keep documents, notes and time in separate lists can hold each item, but the single history is rebuilt only if entries keep their dates and authors.
Scottish accounts rules
The accounts software is written for the Law Society of Scotland’s accounts rules, including real-time monitoring of surpluses, as well as the rules south of the border. A destination must cope with the rules the firm practises under. For Scottish firms that is the first thing to confirm with any replacement.
Outsourced cashiering
LawWare also runs an outsourced legal cashiering service, and some firms have their books kept that way. If so, the people who know the ledgers are outside the firm. They need to be part of the cutover plan: closing the period, producing the final reconciliation and confirming the balances that are loaded.
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 LawCloud holds, table by table, and agree with you what the copy in SQLite must be able to answer later. Everything LawCloud 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 LawCloud: record counts, totals where LawCloud 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 LawCloud, the export is run a final time and checked again. There is nothing to go live. LawCloud 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 LawCloud 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 LawCloud 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
LawCloud to SQLite: what firms ask
Who gives us our data if LawWare hosts it?
The firm asks LawWare for it. We set out what is needed: the database, the document store and the closing accounts reports, taken at the same moment. How the copy is supplied and how long it takes are confirmed with LawWare during the analysis, and the cutover date is set around that answer.
Is LawCloud the same thing as LawWare?
For migration purposes, yes. LawCloud was the name for LawWare’s hosted service, and the software behind it is LawWare. What matters is the version: the older version 4 or the redesigned New LawWare. The firm’s support contact can confirm that, and we plan the extraction around it.
Does the copy in SQLite hold trust ledgers from LawCloud?
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 LawCloud as at the export date.
Does everything in LawCloud have a place in SQLite?
Most of it does on paper. Contacts, calendar entries, tasks, custom fields, templates and intake records 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 SQLite is kept as a readable archive, and you see which before the move.
What has to be decided before LawCloud is written out to SQLite?
Documents and emails are exported with mapping, so each mapping is agreed with you first. Contacts, calendar entries, tasks, custom fields, templates and intake records 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 LawCloud and into SQLite
Other destinations from LawCloud
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.
LawCloud and SQLite are the names and marks of their owners, used here only to identify the two systems.
Moving from LawCloud 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.