Data migration route
CARET Legal data to SQLite
CARET Legal 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 CARET Legal holds and keeps it readable and open to queries.
CARET LegalCloud- Matters: Exported in full
- Contacts: Exported in full
- Notes: Exported in full
- Calendar: Exported in full
- Tasks: 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
SQLiteFiles- Templates: Kept as a readable archive
- 10 carried
- 3 mapped
- 1 archived
What moves
What moves from CARET Legal to SQLite
Each row is a kind of record CARET Legal holds, whether SQLite has a place for it, and what is planned. On this route ten kinds of record carry across, three kinds need mapping and one kind has no place in SQLite and is archived.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldMatter fields include status, date opened, primary clients and three separate attorney roles. | Has a placeA matters table keyed by matter number. | Exported in full |
| ContactsClients, other parties and referrers | Held | Has a placeContacts and their roles on matters as linked tables. | Exported in full |
| DocumentsFiles stored in or linked from the system | HeldNative store with folders and version history; NetDocuments or Worldox can be linked instead. | 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 | HeldBuilt-in email client syncs with Google, Office 365 or IMAP and copies messages to the matter. | Has a place in partAs message files in folders, indexed in a table. | Exported with mapping |
| NotesFile notes, matter notes and contact notes | Held | Has a placeA notes table linked to matters. | Exported in full |
| CalendarAppointments, court dates and deadlines | HeldIncludes rules-based court deadlines. | Has a placeA table of dated entries, with no calendar view. | Exported in full |
| TasksTo-dos and workflow steps assigned to people | Held | Has a placeA table of tasks and their status at the final date. | Exported in full |
| Time and expensesTime and expense entries, billed and unbilled | HeldA timer can run while an email is written and save the entry on send. | Has a placeA table of time and expense entries. | Exported in full |
| BillingInvoices, payments and debtor balances | HeldIncludes pre-billing, batch billing, LEDES and split billing. | Has a placeInvoice and receipt tables; invoice PDFs kept as files. | Exported in full |
| Trust moneyTrust or client account ledgers and balances | Held | Has a placeTrust transactions as rows, for look-up and not for accounting. | Exported in full |
| Firm accountsGeneral ledger, office account and payables | HeldGeneral ledger, profit and loss, balance sheet and vendor bills are built in. | Has a placeLedger journals as rows, where the source held them. | Exported in full |
| Custom fieldsFields and record types the firm added itself | HeldCustom fields can be defined for each practice area. | Has a placeColumns added to the table they belonged to. | Exported with mapping |
| TemplatesPrecedents, document templates and automation | HeldDocument automation is built in, with a HotDocs-based option for complex documents. | No placePrecedent files are kept in folders, not in the database. | Kept as a readable archive |
| IntakeLeads, enquiries, intake forms and pipelines | HeldCRM with lead sources, intake forms and conversion of a lead to a matter. | 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 CARET Legal.
- 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.
- Kept as a readable archive
- SQLite has no place for it. It is exported in a format that opens without CARET Legal 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 CARET Legal 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 CARET Legal 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.
CARET Legal 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 CARET Legal will release depends on its export tools, and that is confirmed in the analysis.
Where the data is now
Leaving CARET Legal
CARET Legal keeps email, documents, leads and the firm’s books inside one product, so leaving it usually means replacing several things at once. Matters and documents are the familiar part. The firm also has to decide where its general ledger goes, what happens to years of email filed against matters, and whether the destination can hold the lead records that sit in the CRM.
Email is part of it
The built-in email client copies messages into each matter’s Communications tab, and it attaches inbound mail from known matter contacts automatically. A firm can end up with far more filed email than staff ever filed by hand. The analysis counts it per matter, and the firm decides whether it moves as documents or stays in the mail provider.
The firm’s books are inside
There is no separate accounting package to leave running. The general ledger, the profit and loss, the balance sheet and vendor bills are all in CARET Legal. If the destination has no general ledger, an accounting system is chosen and opened first, and the cutover date is set at the end of an accounting period.
Three attorneys per matter
Each matter records a responsible, an originating and a billing attorney. Plenty of systems hold one or two of those. Origination often drives partner compensation reports, so where the destination has no field for it, a custom field is created and tested against a known report before the final load.
Fields differ by practice area
Custom fields are set up per practice area, so a family law matter and a personal injury matter carry different sets. The mapping is done one practice area at a time. Fields that feed intake forms or document automation are marked, because their names matter to templates in the new system.
Leads that never became matters
The CRM holds prospects with their source, practice area and expected value, and only some were converted to matters. A destination without a lead pipeline has nowhere obvious to put the rest. They are exported as a list for the firm to keep, or loaded as contacts with a tag.
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 CARET Legal holds, table by table, and agree with you what the copy in SQLite must be able to answer later. Everything CARET Legal 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 CARET Legal: record counts, totals where CARET Legal 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 CARET Legal, the export is run a final time and checked again. There is nothing to go live. CARET Legal 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 CARET Legal 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 CARET Legal 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
CARET Legal to SQLite: what firms ask
We used to be on Zola Suite. Is that data separate from CARET Legal?
No. Zola Suite was renamed CARET Legal, and the firm’s account carried on under the new name. Everything entered in the Zola years is in the same database as what was entered last week, so there is one extraction to plan.
Our documents are in NetDocuments, linked to CARET Legal. Do they need to move?
Not necessarily. Where NetDocuments or Worldox holds the documents, the files can stay there. What has to be rebuilt is the link between each matter and its workspace, if the new practice management system supports one. Documents saved in CARET Legal’s own store do move, with their folders.
Can we move part-way through a financial year?
Yes, but the general ledger makes the date matter more than it does for a system that only bills. Opening balances are taken at a period end that the accountant has closed, and the trust cutover is rehearsed on a full trial load before the real one.
Does the copy in SQLite hold trust ledgers from CARET Legal?
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 CARET Legal as at the export date.
What happens to records SQLite has no place for?
On this route that is templates. They are exported from CARET Legal 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 CARET Legal is written out to SQLite?
Documents, emails and custom fields are exported with mapping, so each mapping is agreed with you first. The firm also decides who may open the archive and how long it is kept.
Other routes
Other routes from CARET Legal and into SQLite
Other destinations from CARET Legal
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.
CARET Legal and SQLite are the names and marks of their owners, used here only to identify the two systems.
Moving from CARET Legal 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.