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

Data migration route

ProLaw data to SQLite

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

FromProLawServer
  1. Matters: Exported in full
  2. Contacts: Exported in full
  3. Calendar: Exported in full
  4. Time and expenses: Exported in full
  5. Billing: Exported in full
  6. Trust money: Exported in full
  7. Firm accounts: Exported in full
  8. Intake: Exported in full
  9. Documents: Exported with mapping
  10. Emails: Exported with mapping
  11. Custom fields: Exported with mapping
  12. Notes: Confirmed in the analysis
  13. Tasks: Confirmed in the analysis
  14. Templates: Confirmed in the analysis
ToSQLiteFiles
  • 8 carried
  • 3 mapped
  • 3 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from ProLaw to SQLite

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

Records in ProLaw and their place in SQLite
RecordIn ProLawIn 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 referrersHeldOne database of clients, prospects and relationships, also used for conflict checks.Has a placeContacts and their roles on matters as linked tables.Exported in full
DocumentsFiles stored in or linked from the systemHeldDocuments are reached from the matter, with Word, Outlook and Adobe integration.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 partThrough the Outlook integration.Has a place in partAs message files in folders, indexed in a table.Exported with mapping
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeA notes table linked to matters.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldRules-based docketing and calendaring.Has a placeA table of dated entries, with no calendar view.Exported in full
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeA table of tasks and their status at the final date.Confirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldHas a placeA table of time and expense entries.Exported in full
BillingInvoices, payments and debtor balancesHeldBilling history and invoicing status are held with the matter.Has a placeInvoice and receipt tables; invoice PDFs kept as files.Exported in full
Trust moneyTrust or client account ledgers and balancesHeldPart of the back office accounting.Has a placeTrust transactions as rows, for look-up and not for accounting.Exported in full
Firm accountsGeneral ledger, office account and payablesHeldFinancial accounting, budgeting and cost recovery, including contingency case accounting.Has a placeLedger journals as rows, where the source held them.Exported in full
Custom fieldsFields and record types the firm added itselfHeldCustom tabs, which can also link to other applications.Has a placeColumns added to the table they belonged to.Exported with mapping
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 pipelinesHeld in partProspects are kept in the same contact database as clients.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 ProLaw.
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 ProLaw 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 ProLaw 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 ProLaw stays untouched until the copy in SQLite has been checked.

Where the data is now

A firm that runs both halves of ProLaw has a wide scope to move: matters, a shared contact database, documents, docket entries, records management, time, billing and the ledgers. Having it all in one system on the firm’s server helps. The effort goes into custom tabs, rules-based docket entries and deciding where the back office goes if the destination has no general ledger.

  1. Front office and back office

    The front office holds matters, contacts, documents, events and conflicts, and the back office holds billing and the firm’s accounts. A firm may have licensed one half and run another product for the rest. Which halves are in use, and what the other product is, sets the shape of the whole move.

  2. Custom tabs

    ProLaw lets a firm add its own tabs and connect them to other applications. Years of practice-specific data end up there. Each tab is listed with its fields and how many matters use them, and the firm chooses which become fields in the new system and which become a note.

  3. Docket entries from rules

    Deadlines can be generated from court rules, so one trigger date produces a set of related events. The dates come across as calendar entries, but the tie back to the rule does not, so a changed hearing date will not recalculate the old set. Open matters with rule-based deadlines are flagged for the lawyers to review.

  4. One contact, many uses

    A single contact database serves clients, prospects, other parties and marketing lists, and the conflict check reads the same people. Duplicates therefore distort conflict results as well as mailings. They are merged in ProLaw before extraction where they can be identified, and each relationship type is mapped.

  5. Physical file records

    Records management tracks paper files and where they are kept. It is easy to forget until someone needs a file from storage. The location recorded for each matter’s paper file is carried to a field or note on the matter in the destination.

More about moving off ProLaw

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

ProLaw to SQLite: what firms ask

Who makes ProLaw now?

Elite. ProLaw was sold under the Thomson Reuters name for years, and Elite, once a Thomson Reuters business, now publishes it as a separate company. Elite’s own site carries ProLaw customer news and a ProLaw summit for 2026. Your support contract shows which entity you deal with.

Do documents keep their matter links?

Documents saved through ProLaw are recorded against a matter. The record and the file are brought together again in the destination, under the same matter and with the original dates. Files saved outside ProLaw, on desktops or shared drives, are a separate source that the firm identifies during the analysis.

Can contingency matters and their costs move?

Yes, but they need more care than hourly matters. Advanced costs and expected fees are extracted per matter and agreed to ProLaw’s reports. Where the destination handles contingency work differently, the firm’s accounts staff decide how each balance is to be shown before the trial load.

Does the copy in SQLite hold trust ledgers from ProLaw?

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

Does everything in ProLaw have a place in SQLite?

Most of it does on paper. Notes, tasks 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 ProLaw is written out to SQLite?

Documents, emails and custom fields are exported with mapping, so each mapping is agreed with you first. Notes, tasks 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

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

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