Data migration route
Time Matters data to SQLite
Time Matters is a server-based 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 Time Matters holds and keeps it readable and open to queries.
Time MattersServer- 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
- Documents: Exported with mapping
- Emails: Exported with mapping
- Custom fields: Exported with mapping
- Trust money: Confirmed in the analysis
- Intake: Confirmed in the analysis
SQLiteFiles- Templates: Kept as a readable archive
- 7 carried
- 3 mapped
- 2 to confirm
- 1 archived
What moves
What moves from Time Matters to SQLite
Each row is a kind of record Time Matters holds, whether SQLite has a place for it, and what is planned. On this route seven 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 | Held | 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 | HeldDocuments are created, searched and tied to clients and matters. | 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 and attachments are managed against matters. | Has a place in partAs message files in folders, indexed in a table. | Exported with mapping |
| NotesFile notes, matter notes and contact notes | HeldNotes and phone calls are separate records. | Has a placeA notes table linked to matters. | Exported in full |
| CalendarAppointments, court dates and deadlines | HeldCalled Events. | Has a placeA table of dated entries, with no calendar view. | Exported in full |
| TasksTo-dos and workflow steps assigned to people | HeldCalled ToDos. | 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 | HeldTime and expenses. | Has a placeA table of time and expense entries. | Exported in full |
| BillingInvoices, payments and debtor balances | Held in partBasic billing; advanced billing in the Billing Matters edition. | Has a placeInvoice and receipt tables; invoice PDFs kept as files. | Exported in full |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | Has a placeTrust transactions as rows, for look-up and not for accounting. | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldForms, fields and record layouts are set by the firm. | Has a placeColumns added to the table they belonged to. | Exported with mapping |
| TemplatesPrecedents, document templates and automation | HeldMerge Templates, AutoEntry Forms, Triggers and Chains. | No placePrecedent files are kept in folders, not in the database. | Kept as a readable archive |
| 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 Time Matters.
- 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 Time Matters 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 Time Matters 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 Time Matters 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.
Both ends are on equipment the firm controls, so the work is done on the firm’s own network with its IT provider. Disk space for a second full copy is checked first. The original in Time Matters stays untouched until the copy in SQLite has been checked.
Where the data is now
Leaving Time Matters
Firms that have used Time Matters for years have usually reshaped it, and that is what takes thought when leaving. The standard records, which are contacts, matters, events, to-dos, notes, phone calls, emails and documents, move in a predictable way. What differs in every installation is the firm’s own forms, added fields, Triggers and Chains, and the analysis spends most of its time there.
Forms the firm redesigned
Record forms, field labels and layouts can be changed by the firm. A field that the default form calls one thing may carry a different label, and a different meaning, on the firm’s version. The mapping is made from the firm’s own form definitions, never from the default names.
Triggers and Chains
Triggers start tasks or events when a date or status changes, and Chains join steps into a sequence. AutoEntry Forms cut down repeated entry. The records they created come across, but the rules do not, so the processes that still matter are written down with the staff who use them and rebuilt in the destination.
Every record type is separate
Events, ToDos, phone calls, notes, emails and documents are distinct kinds of record, each tied to a matter or contact. Phone records in particular have no equivalent in many systems, and are loaded as dated notes. Counts for each record type are checked against Time Matters matter by matter.
Billing may be elsewhere
Time and expenses are recorded here, but invoices and ledgers may be kept in PCLaw or QuickBooks through a link, or in Billing Matters. The move identifies which, and treats that program as a second source. Matters are paired across the two using the reference the link relies on.
Supported versions turn over
The vendor retires versions on a published schedule, release by release, so a firm that has not upgraded for a few years may be on one that is out of support. It can still be moved. Its backup is checked early, since vendor help with a failed restore may not be on offer for a retired release.
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 Time Matters holds, table by table, and agree with you what the copy in SQLite must be able to answer later. Everything Time Matters 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 Time Matters: record counts, totals where Time Matters 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 Time Matters, the export is run a final time and checked again. There is nothing to go live. Time Matters 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 Time Matters 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 Time Matters 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
Time Matters to SQLite: what firms ask
Do our documents come across with their matter links?
Each document in Time Matters has a record that ties it to a client or matter. The record supplies the matter, description and date, and the file supplies the content. Both are needed. Where a record refers to a file that has been moved or deleted, it is reported before the trial load.
Can we keep our custom fields?
The ones in use, yes, if the destination has custom fields for matters and contacts. Every field the firm added is listed in the analysis with how often it is filled. Fields that held structured data move as fields. Those used as scratch space usually become part of a note, by the firm’s choice.
We link Time Matters to PCLaw. Do they move together?
They should be planned together even if they go live a few days apart. The link keeps clients, matters and time in step between the two, and both feed the new system. One matter list is built from both, with PCLaw as the authority for money and Time Matters for the rest.
Does the copy in SQLite hold trust ledgers from Time Matters?
That is confirmed in the analysis. We could not establish it from the two products’ own material, so it is checked against your data in Time Matters before the plan is fixed.
What happens to records SQLite has no place for?
On this route that is templates. They are exported from Time Matters 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 Time Matters is written out to SQLite?
Documents, emails and custom fields are exported with mapping, so each mapping is agreed with you first. Trust ledgers 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 Time Matters and into SQLite
Other destinations from Time Matters
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.
Time Matters and SQLite are the names and marks of their owners, used here only to identify the two systems.
Moving from Time Matters 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.