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

Data migration route

Zola Suite data to SQLite

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

FromZola SuiteCloud
  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 Zola Suite to SQLite

Each row is a kind of record Zola Suite 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 Zola Suite and their place in SQLite
RecordIn Zola SuiteIn SQLiteWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldHas 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 systemHeldAny file type, indexed for search, with a new version saved on each edit.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 storeHeldAn email client is part of the product and files messages against matters.Has a place in partAs message files in folders, indexed in a table.Exported with mapping
NotesFile notes, matter notes and contact notesHeldHas a placeA notes table linked to matters.Exported in full
CalendarAppointments, court dates and deadlinesHeldHas a placeA table of dated entries, with no calendar view.Exported in full
TasksTo-dos and workflow steps assigned to peopleHeldHas a placeA table of tasks and their status at the final date.Exported in full
Time and expensesTime and expense entries, billed and unbilledHeldHas a placeA table of time and expense entries.Exported in full
BillingInvoices, payments and debtor balancesHeldOne matter can be split between several billing clients, each with its own invoice.Has a placeInvoice and receipt tables; invoice PDFs kept as files.Exported in full
Trust moneyTrust or client account ledgers and balancesHeldHas a placeTrust transactions as rows, for look-up and not for accounting.Exported in full
Firm accountsGeneral ledger, office account and payablesHeldVendor bills, cheque writing and financial statements sit in the same system.Has a placeLedger journals as rows, where the source held them.Exported in full
Custom fieldsFields and record types the firm added itselfHeldHas a placeColumns added to the table they belonged to.Exported with mapping
TemplatesPrecedents, document templates and automationHeldNo placePrecedent files are kept in folders, not in the database.Kept as a readable archive
IntakeLeads, enquiries, intake forms and pipelinesHeldLeads and intake forms are handled in the built-in CRM.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 Zola Suite.
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 Zola Suite 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 Zola Suite 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 Zola Suite 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.

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

Where the data is now

Nobody moves off Zola Suite as such any more. The records are in CARET Legal, and that is the system the data is taken from. Firms that joined in the Zola years tend to have the longest history in it, with billing arrangements and document links set up long ago that current staff may not know about. Finding those early is most of the analysis.

  1. One account, two names

    Staff who say Zola and staff who say CARET are talking about the same login. The vendor announced a new name, not a new system, so there should be no older archive to hunt for. Old bookmarks, saved report names and procedure documents may still carry the Zola name, and it helps to list them before cutover.

  2. Split billing on a matter

    A single matter can be billed to several clients at set percentages, with fees and costs split separately and a distinct invoice number for each payer. Many systems expect one bill-to client per matter. Split matters are listed in the analysis, and the firm chooses between sub-matters and a manual split in the destination.

  3. Payables and cheques

    Vendor bills, outgoing payments and cheque runs are recorded here, along with the costs passed on to matters. When the firm leaves, its unpaid vendor bills and its vendor list need a home in whatever accounting package comes next. That list is reconciled to the payables report on the day of the freeze.

  4. Worldox or NetDocuments links

    Some firms never used the built-in document store. They linked each matter to a Worldox cabinet or a NetDocuments workspace and worked from there. Those documents are not in the practice management database at all. The analysis records which store each matter points to, so no folder is assumed to be empty when it is only held elsewhere.

  5. Every edit kept as a version

    Editing a Word document inside the product saves a new version each time, and any earlier one can be restored. A long-running matter may hold dozens of versions of one agreement. The firm decides whether all of them move or only the current one, and the document count in the trial load is checked against that decision.

More about moving off Zola Suite

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

Zola Suite to SQLite: what firms ask

Is Zola Suite still available?

Not under that name. The vendor renamed it CARET Legal after AbacusNext became CARET, and the Zola Suite web address now leads to the CARET Legal site. It was presented as a rebrand, so a firm that never left is simply using CARET Legal.

Our invoices go back to when we started on Zola. Can the full billing history move?

It depends on what the destination will accept. Some systems take historic invoices and payments as records. Others take only open balances, with the old invoices attached as PDFs. Split-billed matters need the closest look, since each payer has its own invoice number.

Do we plan the move as Zola Suite or as CARET Legal?

As CARET Legal, because that is what the firm logs into and what the vendor supports. The planning is the same either way. One extra step for a long-standing Zola firm is checking for features switched on years ago, such as split billing or a Worldox link.

Does the copy in SQLite hold trust ledgers from Zola Suite?

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 Zola Suite as at the export date.

What happens to records SQLite has no place for?

On this route that is templates. They are exported from Zola Suite 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 Zola Suite 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

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

Moving from Zola Suite 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.