Data migration route
Tabs3 Billing data to SQLite
Tabs3 Billing is a server-based accounting and billing 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 Tabs3 Billing holds and keeps it readable and open to queries.
Tabs3 BillingServer- Matters: Exported in full
- Contacts: Exported in full
- Time and expenses: Exported in full
- Billing: Exported in full
- Trust money: Exported in full
- Notes: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
SQLiteFiles- Templates: Kept as a readable archive
- 5 carried
- 2 to confirm
- 1 archived
What moves
What moves from Tabs3 Billing to SQLite
Each row is a kind of record Tabs3 Billing holds, whether SQLite has a place for it, and what is planned. On this route five kinds of record carry across, 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 | HeldEach matter is a Client ID; the digits after the decimal point are the matter. | Has a placeA matters table keyed by matter number. | Exported in full |
| ContactsClients, other parties and referrers | Held in partClient names and addresses; fuller contact records are in PracticeMaster. | Has a placeContacts and their roles on matters as linked tables. | Exported in full |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a placeA notes table linked to matters. | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | HeldFees with hours worked and hours to bill, plus costs. | Has a placeA table of time and expense entries. | Exported in full |
| BillingInvoices, payments and debtor balances | HeldDraft and final statements, payments and a client ledger. | Has a placeInvoice and receipt tables; invoice PDFs kept as files. | Exported in full |
| Trust moneyTrust or client account ledgers and balances | Held in partClient funds for retainers; trust ledgers are in the Trust Accounting module. | Has a placeTrust transactions as rows, for look-up and not for accounting. | 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 | HeldStatement layouts built in the Statement Designer. | No placePrecedent files are kept in folders, not in the database. | Kept as a readable archive |
What the plans mean
- Exported in full
- SQLite has a place for this kind of record. It is loaded there and checked against Tabs3 Billing.
- 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 Tabs3 Billing 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 Tabs3 Billing 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 Tabs3 Billing 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 Tabs3 Billing stays untouched until the copy in SQLite has been checked.
Where the data is now
Leaving Tabs3 Billing
Billing is where a Tabs3 firm’s money history sits. A move takes unbilled fees and costs, open statements, payments, client funds and the receivable ledger, and agrees each to a Tabs3 report at a statement cut-off. The archive of billed transactions is large and is handled as its own decision. Trust and the general ledger are other modules and move alongside.
Work in process and archive
Updating a final statement moves its fees, costs and payments out of the working files into archive files named T3ARCH. So unbilled work is in one place and billed history in another. Unbilled items are loaded as unbilled. The archive is loaded as history only where the destination can hold billed entries without billing them again.
Statements can be undone
Tabs3 can undo an updated statement, which moves its transactions back from the archive to work in process. Before the final extraction, the firm confirms that no statements are waiting to be undone or run again. A statement reversed after the data is taken would leave the two systems disagreeing about what has been billed.
Client funds are not trust
The client funds feature tracks non-refundable retainers and similar money kept in the firm’s general account, apart from the receivable balance. It is a different thing from the Trust Accounting module. Each client funds balance is mapped on purpose, usually to a retainer or credit on the matter, and not to the trust ledger.
Courtesy discounts change history
When a client is billed with a courtesy discount, each archived fee is reduced by its share of the discount. The archive therefore shows fees net of discount, not as first recorded. History loaded elsewhere is compared with Tabs3 on that basis, or the totals look wrong when they are not.
Deleted clients take history
Deleting a client in Tabs3 deletes its archived transactions too. A firm that tidied its client list years ago may hold less history than it expects. The analysis reports the earliest transaction date for each client, so nobody plans around records that are no longer there.
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 Tabs3 Billing holds, table by table, and agree with you what the copy in SQLite must be able to answer later. Everything Tabs3 Billing 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 Tabs3 Billing: record counts, totals where Tabs3 Billing 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 Tabs3 Billing, the export is run a final time and checked again. There is nothing to go live. Tabs3 Billing 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 Tabs3 Billing 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 Tabs3 Billing 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
Tabs3 Billing to SQLite: what firms ask
Can billed fee history be loaded, or only balances?
Open statements and their balances are loaded, because the firm still has to collect them. Whether every billed fee line from the archive comes across depends on the destination: some accept billed time as history, others only take invoice totals. Where detail cannot be loaded, the archive stays readable in Tabs3, which is kept read only.
What about our statement templates?
Statement layouts are built in the Tabs3 Statement Designer and do not open in another product. The firm picks the layouts it still uses, and those are rebuilt as invoice templates in the new system. A side-by-side print of one real client’s bill from each system is the test.
Do timekeeper rates and billing categories move?
Timekeepers, rate tables and transaction codes are extracted as lists and set up in the destination before any time is loaded, because every fee entry refers to them. Client and matter rate exceptions are loaded with the matter. Codes nobody has used in years are left out by agreement.
Does the copy in SQLite hold trust ledgers from Tabs3 Billing?
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 Tabs3 Billing as at the export date.
What happens to records SQLite has no place for?
On this route that is templates. They are exported from Tabs3 Billing 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 Tabs3 Billing is written out to SQLite?
Notes and custom fields 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 Tabs3 Billing and into SQLite
Other destinations from Tabs3 Billing
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.
Tabs3 Billing and SQLite are the names and marks of their owners, used here only to identify the two systems.
Moving from Tabs3 Billing 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.