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

Data migration route

Firm Central data to SQLite

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

FromFirm CentralCloud
  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. Documents: Exported with mapping
  11. Emails: Confirmed in the analysis
  12. Custom fields: Confirmed in the analysis
  13. Templates: Confirmed in the analysis
  14. Intake: Confirmed in the analysis
ToSQLiteFiles
  • 9 carried
  • 1 mapped
  • 4 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Firm Central to SQLite

Each row is a kind of record Firm Central holds, whether SQLite has a place for it, and what is planned. On this route nine kinds of record carry across, one kind needs mapping and four kinds are confirmed in the analysis.

Records in Firm Central and their place in SQLite
RecordIn Firm CentralIn SQLiteWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldOpen and closed matters with practice area, client group, permissions and primary attorney.Has a placeA matters table keyed by matter number.Exported in full
ContactsClients, other parties and referrersHeldClients, contacts and client groups.Has a placeContacts and their roles on matters as linked tables.Exported in full
DocumentsFiles stored in or linked from the systemHeldMatter folders that could be layered freely, plus a My Documents area for each user.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 storeTo be confirmedHas a place in partAs message files in folders, indexed in a table.Confirmed in the analysis
NotesFile notes, matter notes and contact notesHeldMatter notes.Has a placeA notes table linked to matters.Exported in full
CalendarAppointments, court dates and deadlinesHeldCalendar events, and Deadline Assistant events for firms that had that add-on.Has a placeA table of dated entries, with no calendar view.Exported in full
TasksTo-dos and workflow steps assigned to peopleHeldMatter tasks.Has a placeA table of tasks and their status at the final date.Exported in full
Time and expensesTime and expense entries, billed and unbilledHeld in partThrough the Time & Billing module, which was supplied by eBillity.Has a placeA table of time and expense entries.Exported in full
BillingInvoices, payments and debtor balancesHeld in partPre-bills, invoices and payments in the Time & Billing module.Has a placeInvoice and receipt tables; invoice PDFs kept as files.Exported in full
Trust moneyTrust or client account ledgers and balancesHeld in partThe Time & Billing module had a Trusts & Retainers tab.Has a placeTrust transactions as rows, for look-up and not for accounting.Exported in full
Firm accountsGeneral ledger, office account and payablesHeld in partEditions sold with Accounting had a chart of accounts and accounts payable.Has a placeLedger journals as rows, where the source held them.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
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas 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 Firm Central.
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.

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

Firm Central 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 Firm Central will release depends on its export tools, and that is confirmed in the analysis.

Where the data is now

Firm Central was discontinued in 2024, so a move from it today starts with whatever the firm saved before the shutdown. Thomson Reuters’ extraction guide had firms download their data as a set of CSV files and zipped document bundles. The job is to find those files, work out what each contains, and rebuild matters from the pieces in a system the firm now uses.

  1. The source is an export

    What survives is a collection of downloads: contact and matter lists, document bundles and calendar files, saved by whoever ran the export in 2024. They may sit on one person’s computer. The analysis begins with an inventory of those files, including their dates, since an export taken weeks before the shutdown misses later work.

  2. One file per kind of record

    Matter lists, matter notes, matter tasks, billing rates, permissions and primary attorneys were each exported as their own CSV, and separately for open and closed matters. Each file is a flat list. The pieces are joined back together on the matter and client they name, and rows that match nothing are listed for the firm.

  3. Documents came out as zips

    Bulk document extraction produced zipped bundles holding each matter’s folders, with files in the format they were uploaded in. Firm Central allowed folders to be layered freely, so structures vary from matter to matter. Each user’s My Documents came out as a separate set and has no matter attached until someone assigns one.

  4. Billing sat with eBillity

    Time entries, invoices, payments and trust records were in the Time & Billing module, which eBillity supplied. Thomson Reuters told firms they could carry on with those eBillity products under a new billing arrangement. A firm that did so has its billing history in eBillity, not in the Firm Central export.

  5. What the export left out

    The guide notes that client portal messages could not be exported, and that links to Westlaw research saved in matter folders do not include the documents themselves. Neither can be recovered from the files. If either mattered to a particular matter, the firm’s email and Westlaw folders are the places to look.

More about moving off Firm Central

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

Firm Central to SQLite: what firms ask

Firm Central has shut down. Is it too late to move our data?

Not if the firm ran the exports. Thomson Reuters gave firms a way to download contacts, matters, notes, tasks, calendar events and documents before the product ended. Those files can be cleaned and loaded into a current system. If no export was taken, what remains is whatever was also saved elsewhere.

We exported everything in 2024 but never loaded it anywhere. What can be done with it?

Quite a lot. The CSV files are joined back into matters with their contacts, notes and tasks, and the document bundles are unzipped and filed against the right matter. Before anything is made final, the firm sees a trial load and a list of whatever could not be matched.

Where did our time and billing records go?

They were never in the main Firm Central database. Time & Billing was an eBillity product offered through Thomson Reuters. Firms that kept it moved to a direct arrangement with eBillity. Those that did not would have downloaded invoices and reports before the end, and those downloads are the record.

Does the copy in SQLite hold trust ledgers from Firm Central?

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 Firm Central as at the export date.

Does everything in Firm Central have a place in SQLite?

Most of it does on paper. Emails, custom fields, templates and intake records 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 Firm Central is written out to SQLite?

Documents are exported with mapping, so each mapping is agreed with you first. Emails, custom fields, templates and intake records 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

Firm Central and SQLite are the names and marks of their owners, used here only to identify the two systems.

Moving from Firm Central 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.