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

Data migration route

Tabs3 data to SQLite

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

FromTabs3Server
  1. Matters: Exported in full
  2. Contacts: Exported in full
  3. Notes: Exported in full
  4. Calendar: Exported in full
  5. Tasks: Exported in full
  6. Time and expenses: Exported in full
  7. Billing: Exported in full
  8. Trust money: Exported in full
  9. Firm accounts: Exported in full
  10. Intake: Exported in full
  11. Documents: Exported with mapping
  12. Emails: Exported with mapping
  13. Custom fields: Exported with mapping
ToSQLiteFiles
  1. Templates: Kept as a readable archive
Readable archiveNo place in SQLite
  • 10 carried
  • 3 mapped
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Tabs3 to SQLite

Each row is a kind of record Tabs3 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.

Records in Tabs3 and their place in SQLite
RecordIn Tabs3In SQLiteWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldA matter is the part of the Client ID after the decimal point.Has a placeA matters table keyed by matter number.Exported in full
ContactsClients, other parties and referrersHeldHas a placeContacts and their roles on matters as linked tables.Exported in full
DocumentsFiles stored in or linked from the systemHeld in partPracticeMaster links documents to clients and contacts.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 storeHeld in partPracticeMaster keeps email records in its Journal.Has a place in partAs message files in folders, indexed in a table.Exported with mapping
NotesFile notes, matter notes and contact notesHeld in partNote, phone and research records in the PracticeMaster Journal.Has a placeA notes table linked to matters.Exported in full
CalendarAppointments, court dates and deadlinesHeld in partIn PracticeMaster.Has a placeA table of dated entries, with no calendar view.Exported in full
TasksTo-dos and workflow steps assigned to peopleHeld in partIn PracticeMaster.Has a placeA table of tasks and their status at the final date.Exported in full
Time and expensesTime and expense entries, billed and unbilledHeldIn Tabs3 Billing, with timers in PracticeMaster.Has a placeA table of time and expense entries.Exported in full
BillingInvoices, payments and debtor balancesHeldIn Tabs3 Billing.Has a placeInvoice and receipt tables; invoice PDFs kept as files.Exported in full
Trust moneyTrust or client account ledgers and balancesHeld in partWith the Trust Accounting module.Has a placeTrust transactions as rows, for look-up and not for accounting.Exported in full
Firm accountsGeneral ledger, office account and payablesHeld in partWith the General Ledger and Accounts Payable modules.Has a placeLedger journals as rows, where the source held them.Exported in full
Custom fieldsFields and record types the firm added itselfHeld in partPracticeMaster Areas of Practice carry the firm’s own files and fields.Has a placeColumns added to the table they belonged to.Exported with mapping
TemplatesPrecedents, document templates and automationHeld in partDocument assembly in PracticeMaster; statement layouts in Billing.No placePrecedent files are kept in folders, not in the database.Kept as a readable archive
IntakeLeads, enquiries, intake forms and pipelinesHeld in partTabs3 CRM covers leads and intake and works with PracticeMaster.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 Tabs3.
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 Tabs3 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 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 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 stays untouched until the copy in SQLite has been checked.

Where the data is now

The first question for a firm on Tabs3 is which modules it owns, because each one is a different set of records. Billing holds time, fees and receivables. PracticeMaster holds contacts, calendar, documents and the journal. Trust, payables and the ledger are separate programs again. All of them share the Client ID, which is what ties a move together.

  1. One ID for client and matter

    A Client ID is up to twelve characters including a decimal point. The part before the point is the client and the part after is the matter. Firms chose a numeric, alphabetic or mixed key type at set-up, and how many decimal places to allow. The ID is split on the way out and both halves are kept.

  2. Everything in one directory

    The modules integrate only when installed in the same directory, which the software calls the current working directory. Its data is a set of DAT and IDX files there. A complete copy of that directory, taken with all users out, is the source for every trial load.

  3. Standard and Platinum

    The Platinum edition adds a server component with scheduled HotBackup and SQL access to the data, and the standard edition has neither. Which edition the firm runs changes how a consistent copy is taken and what can read it, so it is established in the first conversation.

  4. Figures that are not stored

    The vendor’s own help notes that accounts receivable and work in process are calculated from ledger and fee records, not held as fields. So balances cannot be lifted out as a column. They are rebuilt from the transactions and then agreed to the reports the firm prints.

  5. Cloud or server

    Firms on Tabs3 Cloud use the suite as hosted by the vendor, and some on-premises firms run it with one of the vendor’s hosting partners. Where the files are, and who is able to copy them, is settled before a cutover date is set.

More about moving off Tabs3

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 holds, table by table, and agree with you what the copy in SQLite must be able to answer later. Everything Tabs3 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: record counts, totals where Tabs3 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, the export is run a final time and checked again. There is nothing to go live. Tabs3 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 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
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 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 to SQLite: what firms ask

We only have Tabs3 Billing and PracticeMaster. Is that a problem?

No. It means trust and the general ledger are kept in some other program, and that program is added to the plan. The move covers what Tabs3 holds, and the analysis names the other systems that have to agree with it at cutover.

Can we keep the client dot matter numbering?

If the destination allows a firm-set matter number, the full ID can be kept as it is, decimal point included. Where clients and matters are numbered separately, the two halves go into their own fields. Either way the original ID stays searchable, because it is printed on years of statements.

How are the modules extracted together?

From one copy of the working directory, taken at one moment, so billing, trust and ledger all describe the same day. Taking them at different times is how totals end up disagreeing. For the final cutover the copy is taken after month-end procedures are run and before anyone posts again.

Does the copy in SQLite hold trust ledgers from Tabs3?

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

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 and SQLite are the names and marks of their owners, used here only to identify the two systems.

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