Skip to content
NEWLAW.COM
+61 1300 495 281
Let’s talk

Data migration route

Tabs3 Trust Accounting data to SQLite

Tabs3 Trust Accounting 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 Trust Accounting holds and keeps it readable and open to queries.

FromTabs3 Trust AccountingServer
  1. Matters: Exported in full
  2. Contacts: Exported in full
  3. Trust money: Exported in full
  4. Notes: Confirmed in the analysis
  5. Custom fields: Confirmed in the analysis
  6. Templates: Confirmed in the analysis
ToSQLiteFiles
  • 3 carried
  • 3 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Tabs3 Trust Accounting to SQLite

Each row is a kind of record Tabs3 Trust Accounting holds, whether SQLite has a place for it, and what is planned. On this route three kinds of record carry across and three kinds are confirmed in the analysis.

Records in Tabs3 Trust Accounting and their place in SQLite
RecordIn Tabs3 Trust AccountingIn SQLiteWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeld in partTrust accounts are keyed by a Trust ID in the same format as client numbers.Has a placeA matters table keyed by matter number.Exported in full
ContactsClients, other parties and referrersHeld in partShares client and contact details with Billing and PracticeMaster.Has a placeContacts and their roles on matters as linked tables.Exported in full
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeA notes table linked to matters.Confirmed in the analysis
Trust moneyTrust or client account ledgers and balancesHeldTrust ledgers, cheques and EFTs, bank reconciliation and a 3-Way Reconciliation Report.Has a placeTrust transactions as rows, for look-up and not for accounting.Exported in full
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeColumns added to the table they belonged to.Confirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedNo placePrecedent files are kept in folders, not in the database.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 Tabs3 Trust Accounting.
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 Tabs3 Trust Accounting 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 Trust Accounting 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 Trust Accounting stays untouched until the copy in SQLite has been checked.

Where the data is now

Trust is the one part of a Tabs3 move that cannot be re-run casually. Each trust account balance is taken at an agreed date, by Trust ID and by bank account, and proved against a completed three-way reconciliation. The same figures are rehearsed on a full trial load. Only then is the cutover booked, and the old program is kept so past ledgers can be printed.

  1. A trust account is a ledger

    In this program a trust account means one client’s ledger, and a bank account is a separate record. Many trust accounts sit in one bank account. A destination that uses the words differently needs the mapping written down: Trust ID to matter, bank account to bank account.

  2. Trust IDs mirror Client IDs

    Trust IDs use the same key type and decimal places as client numbers, so a trust account normally lines up with a client and matter in Billing. Where a firm opened extra trust accounts for one matter, or one for several, those are found in the analysis and the firm decides which matter each balance belongs to.

  3. Payments to the firm

    A trust cheque or EFT marked as a payment to the firm posts to the client’s statement in Billing, or to General Ledger where Billing is not installed. Cutover falls between those two sides. The freeze begins only after every such payment has posted both ways, so no fee is paid in one system and unpaid in the other.

  4. Uncleared items at cutover

    Opening balances in the new system are ledger balances, but the first bank reconciliation there needs the uncleared cheques and deposits as well. Those are extracted as a list from the last Tabs3 reconciliation, for each bank account, and entered so the opening bank position agrees to the statement.

  5. 1099 totals and year end

    Trust payees can be reported on 1099 forms, combined with Accounts Payable vendors. A mid-year move leaves part of the year’s payments in each system. Year-to-date totals for each payee are extracted so the firm’s year-end 1099 run is complete.

More about moving off Tabs3 Trust Accounting

Where it is going

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

More about moving into SQLite

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.

  1. Analysis

    We read what Tabs3 Trust Accounting holds, table by table, and agree with you what the copy in SQLite must be able to answer later. Everything Tabs3 Trust Accounting holds is in scope unless you take it out.

  2. 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.

  3. Trial export

    The data is written to SQLite as a trial and checked against Tabs3 Trust Accounting: record counts, totals where Tabs3 Trust Accounting holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.

  4. Final export

    After the last day of work in Tabs3 Trust Accounting, the export is run a final time and checked again. There is nothing to go live. Tabs3 Trust Accounting 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 Trust Accounting 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

Step 1 of 5: Start with the route

Moving fromTabs3 Trust Accounting
Moving toSQLite

The route comes from this page. Four short steps follow. Nothing you send commits your firm to anything.

What happens after you send it

  1. A free first call

    We go through your answers with you and ask about anything they leave open.

  2. An analysis of what Tabs3 Trust Accounting 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.

  3. 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 Trust Accounting to SQLite: what firms ask

Can trust be moved at a different time from billing?

It can, though it is rarely worth it. Trust balances show on statements and trust payments settle bills, so the two modules lean on each other. Moving them on the same weekend keeps one cut-off date. If they must be staged, the manual steps in between are agreed first.

Do closed trust ledgers come across?

Zero-balance trust accounts for finished matters carry history a regulator may ask for. Their transactions can be loaded where the destination accepts historical trust entries. Otherwise the ledgers are printed to PDF per client and filed to the matter, and Tabs3 is kept read only for the retention period.

What if the three-way reconciliation is out?

Then the difference is found and fixed in Tabs3 first. Loading an unreconciled trust ledger only moves the problem into a system nobody knows yet. The analysis includes the latest reconciliation, and cutover is not scheduled until bank, book and client ledger totals agree.

Does the copy in SQLite hold trust ledgers from Tabs3 Trust Accounting?

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 Trust Accounting as at the export date.

Does everything in Tabs3 Trust Accounting have a place in SQLite?

Most of it does on paper. Notes, custom fields and templates 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 Tabs3 Trust Accounting is written out to SQLite?

Notes, custom fields and templates are confirmed in the analysis. The firm also decides who may open the archive and how long it is kept.

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.

How we do itDiscovery to rollout, step by step

Tabs3 Trust Accounting and SQLite are the names and marks of their owners, used here only to identify the two systems.

Moving from Tabs3 Trust Accounting 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.