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

Data migration route

PracticeMaster data to SQLite

PracticeMaster is a server-based case 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 PracticeMaster holds and keeps it readable and open to queries.

FromPracticeMasterServer
  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. Intake: Exported in full
  8. Documents: Exported with mapping
  9. Emails: Exported with mapping
  10. Custom fields: Exported with mapping
ToSQLiteFiles
  1. Templates: Kept as a readable archive
Readable archiveNo place in SQLite
  • 7 carried
  • 3 mapped
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from PracticeMaster to SQLite

Each row is a kind of record PracticeMaster holds, whether SQLite has a place for it, and what is planned. On this route seven kinds of record carry across, three kinds need mapping and one kind has no place in SQLite and is archived.

Records in PracticeMaster and their place in SQLite
RecordIn PracticeMasterIn SQLiteWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldClient file mirrored with Tabs3 Billing, one record per Client ID.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 systemHeldDocument Management records link files to a client or contact, with check-out and versions.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 storeHeldEmail records in the Journal, created through 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 notesHeldNote, phone call and research records in the Journal.Has a placeA notes table linked to matters.Exported in full
CalendarAppointments, court dates and deadlinesHeldFirm-wide calendar with Outlook integration and calendar plan templates.Has a placeA table of dated entries, with no calendar view.Exported in full
TasksTo-dos and workflow steps assigned to peopleHeldTasks and reminders on the calendar.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 partTimer records and fees that pass to Tabs3 Billing.Has a placeA table of time and expense entries.Exported in full
Custom fieldsFields and record types the firm added itselfHeldAreas of Practice with the firm’s own files and fields.Has a placeColumns added to the table they belonged to.Exported with mapping
TemplatesPrecedents, document templates and automationHeldDocument assembly with Word or HotDocs, WorkFlows and calendar plan templates.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 handles leads and intake and passes them to 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 PracticeMaster.
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 PracticeMaster 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 PracticeMaster 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 PracticeMaster 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 PracticeMaster stays untouched until the copy in SQLite has been checked.

Where the data is now

PracticeMaster is the part of Tabs3 that looks most like other practice systems, and the part firms have customised most. Contacts, calendar and journal records move in a familiar way. The detail is in the Areas of Practice the firm built, the documents it linked, and the WorkFlows it depends on, none of which have the same shape in another product.

  1. Areas of Practice are tables

    Each Area of Practice has its own files, and firms add files and fields through File Maintenance. A probate area might hold assets and heirs, a family area children and hearings. These can hold many rows for one matter. Every file is listed with its row counts, and each needs a home or a decision.

  2. The Journal mixes record types

    Timer records, phone calls, emails, research and notes are all stored in one Journal file, told apart by a record type. Destinations usually split those into time entries, emails and file notes. Journal records are sorted by type on the way out, so a timer record already billed is not loaded a second time as a note.

  3. Documents are linked, with versions

    The Document Management file links documents to a client or contact, with check-out, check-in and versions. Each record is only the link, and the document is a file on the firm’s storage. PracticeMaster has its own verify function for these links, and it is run before extraction so broken ones are known.

  4. Template paths by practice area

    Document assembly templates sit in a Template Path for each Area of Practice, by default a DOCS folder under that area, and may be Word or HotDocs templates. Their merge codes refer to PracticeMaster fields. Templates are rebuilt against the new system’s fields, starting with the ones produced most often.

  5. WorkFlows and calendar plans

    WorkFlows fire when records are added or changed, and calendar plan templates lay down a series of dated events. Events already created come across as calendar entries. The automation itself is described and rebuilt with the destination’s own tools, because rules do not transfer between products.

More about moving off PracticeMaster

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

PracticeMaster to SQLite: what firms ask

Do emails saved from Outlook come across?

Emails saved through the Outlook integration become journal records on the client. They are loaded to the matter as emails where the destination has an email record, otherwise as dated notes with the message saved as a file.

We want to keep PracticeMaster and replace billing. Is that possible?

The two are tied by mirrored client files and only integrate when installed together. Replacing Billing alone breaks the flow of fees from PracticeMaster. If the plan is to split them, the analysis sets out the manual steps that would stand in for the link, and what they cost in staff time.

What happens to conflict searching?

Conflict searching in PracticeMaster reads the fields the firm marked for it, across clients, contacts and linked documents. After the move, searches run in the new system over the migrated contacts and matters. Names that lived only in free text or old documents are worth a check, since they may not be indexed the same way.

Does the copy in SQLite hold documents from PracticeMaster?

In part. Listed in a table; the files themselves stay in folders beside the database. What SQLite can hold is written out once its mapping is agreed, and the rest is kept beside the data as files that open without PracticeMaster.

What happens to records SQLite has no place for?

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

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

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