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

Data migration route

ProTempus data to SQLite

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

FromProTempusServer
  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. Notes: Confirmed in the analysis
  12. Tasks: Confirmed in the analysis
  13. Custom fields: Confirmed in the analysis
ToSQLiteFiles
  1. Templates: Kept as a readable archive
Readable archiveNo place in SQLite
  • 8 carried
  • 2 mapped
  • 3 to confirm
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from ProTempus to SQLite

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

Records in ProTempus and their place in SQLite
RecordIn ProTempusIn SQLiteWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCalled cases; a client can have several, each with its own rate and billing type.Has a placeA matters table keyed by matter number.Exported in full
ContactsClients, other parties and referrersHeldClients and other parties, with a role on each case and user-defined contact types.Has a placeContacts and their roles on matters as linked tables.Exported in full
DocumentsFiles stored in or linked from the systemHeld in partNot stored in the program: each client links to a network folder, with keyword indexes.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 partEmails are saved as files into the client’s document folder.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 deadlinesHeldA calendar per timekeeper, with optional Outlook or Google sync.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 unbilledHeldTime can be created from calendar events and phone calls.Has a placeA table of time and expense entries.Exported in full
BillingInvoices, payments and debtor balancesHeldHourly, contingency, flat rate and unit billing; invoices can be split between parties.Has a placeInvoice and receipt tables; invoice PDFs kept as files.Exported in full
Trust moneyTrust or client account ledgers and balancesHeldTrust accounting, with invoices payable from the client’s trust balance.Has a placeTrust transactions as rows, for look-up and not for accounting.Exported in full
Firm accountsGeneral ledger, office account and payablesHeldReceivables, payables and general ledger, or an optional QuickBooks interface.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 automationHeldBoilerplate forms filled from the database.No placePrecedent files are kept in folders, not in the database.Kept as a readable archive
IntakeLeads, enquiries, intake forms and pipelinesHeld in partA client’s completed PDF intake form can be imported into the case file.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 ProTempus.
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.
Kept as a readable archive
SQLite has no place for it. It is exported in a format that opens without ProTempus 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 ProTempus 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 ProTempus 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 ProTempus stays untouched until the copy in SQLite has been checked.

Where the data is now

ProTempus keeps its database on the firm’s own network and never took the documents in, so both are close at hand. The detail to watch is how tightly billing is tied to everything else. Calendar entries become charges, cases under one client bill on different terms, and one invoice can be divided among several payers. Those arrangements need to survive the move.

  1. Documents were never imported

    The program does not hold documents. Each client is linked to a folder on the firm’s network, with subfolders for cases, and invoices are saved there as PDFs. The files are already ordinary files. What has to be carried is the link between each client or case and its folder, and any keyword index built on top.

  2. The calendar bills

    A calendar event or logged phone call can be turned into a billable item, and it then shows green. Time entries and calendar entries are therefore two views of the same work. Both are extracted, and the billed flag is checked so that an appointment already charged is not loaded as unbilled time.

  3. Cases under a client

    Each client can have several cases, and each case has its own rate and its own billing type: hourly, contingency, flat rate or unit. By default each case gets its own invoice. A destination that sets billing terms at client level needs those terms moved down to the matter, one case at a time.

  4. Invoices split between payers

    A case’s bill can be divided among any number of parties, each paying a share. The invoice history then shows several debtors for one piece of work. Open balances are loaded against the party who owes them, and the split percentages are recorded on the matter so future bills follow the same rule.

  5. Books inside or QuickBooks

    The firm either uses the embedded payables and general ledger or connects to QuickBooks, where each client’s trust money is a sub-account. Where QuickBooks is used, the program can audit its trust balances against those sub-accounts. That audit is run and cleared before extraction, so both sets of figures start out equal.

More about moving off ProTempus

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

ProTempus to SQLite: what firms ask

Our documents are in folders on the server. Do they move?

They can stay or move. ProTempus only points at those folders, so nothing has to be extracted from the program itself. If the new system stores documents, each client folder is loaded against the matching client and matter. The folder names are checked against the client list first, because renamed folders are the usual cause of orphans.

We enter every caller for conflict checks. Do they all come?

They should. A contact list that includes people who only ever phoned is what makes a conflict search worth running. They are loaded as contacts with no matter attached. The clean-up step looks for the same caller entered more than once, though not every duplicate can be found and some may carry across.

Can trust and operating balances be moved together?

Yes, and they are checked together. Each client’s trust balance is loaded as an opening balance and the total is matched to the bank. Unpaid invoices are loaded as debtors. The trust and financial cutover is rehearsed on a full trial load before the real one, because it cannot be run twice.

Does the copy in SQLite hold trust ledgers from ProTempus?

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

What happens to records SQLite has no place for?

On this route that is templates. They are exported from ProTempus 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 ProTempus is written out to SQLite?

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

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

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