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

Data migration route

LawBase data to SQLite

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

FromLawBaseCase management
  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. Emails: Exported with mapping
  7. Custom fields: Exported with mapping
  8. Documents: Confirmed in the analysis
  9. Time and expenses: Confirmed in the analysis
  10. Billing: Confirmed in the analysis
  11. Trust money: Confirmed in the analysis
  12. Firm accounts: Confirmed in the analysis
  13. Intake: Confirmed in the analysis
ToSQLiteFiles
  1. Templates: Kept as a readable archive
Readable archiveNo place in SQLite
  • 5 carried
  • 2 mapped
  • 6 to confirm
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from LawBase to SQLite

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

Records in LawBase and their place in SQLite
RecordIn LawBaseIn SQLiteWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldScreens and fields are designed per office and practice area.Has a placeA matters table keyed by matter number.Exported in full
ContactsClients, other parties and referrersHeldA configurable address book; contacts are entered once and linked to matters.Has a placeContacts and their roles on matters as linked tables.Exported in full
DocumentsFiles stored in or linked from the systemTo be confirmedHas a place in partListed in a table; the files themselves stay in folders beside the database.Confirmed in the analysis
EmailsEmails saved to matters or to the storeHeld in partBi-directional integration with Microsoft Outlook.Has a place in partAs message files in folders, indexed in a table.Exported with mapping
NotesFile notes, matter notes and contact notesHeldCase notes of unlimited free text.Has a placeA notes table linked to matters.Exported in full
CalendarAppointments, court dates and deadlinesHeldDocketing of appointments and tasks through the email calendar.Has 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 unbilledTo be confirmedHas a placeA table of time and expense entries.Confirmed in the analysis
BillingInvoices, payments and debtor balancesTo be confirmedHas a placeInvoice and receipt tables; invoice PDFs kept as files.Confirmed in the analysis
Trust moneyTrust or client account ledgers and balancesTo be confirmedHas a placeTrust transactions as rows, for look-up and not for accounting.Confirmed in the analysis
Firm accountsGeneral ledger, office account and payablesTo be confirmedHas a placeLedger journals as rows, where the source held them.Confirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldThe whole database layout is defined by the office.Has a placeColumns added to the table they belonged to.Exported with mapping
TemplatesPrecedents, document templates and automationHeldDocument assembly through HotDocs.No placePrecedent files are kept in folders, not in the database.Kept as a readable archive
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 LawBase.
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 LawBase 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 LawBase 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 LawBase 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.

How LawBase is run at the firm is settled at the start of the analysis, because its maker’s own material does not settle it. The usual arrangement is assumed here. 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 LawBase stays untouched until the copy in SQLite has been checked.

Where the data is now

No two LawBase databases are the same, because each office designed its own screens and fields. A move off it starts with reading that design: what tables exist, what each field means in this office, and which are still used. Offices that have run it for decades also hold very long case histories, and the retention decision is made early.

  1. A database the office designed

    LawBase lets an office lay out its own screens and choose its own fields for each practice area. A field labelled Adjuster or Docket Number exists because someone asked for it. There is no standard layout to map from. We document the one in use, with the office’s own people explaining what each field has come to mean.

  2. SmartFolders are groupings

    SmartFolders group files automatically by attorney, subject or any other value in the system. They behave like saved searches, not containers, so there is nothing in them to move. The useful ones are recreated as saved views or reports in the destination, once the fields they depend on have been loaded.

  3. HotDocs templates

    Document assembly runs through HotDocs, and producing a document can also create notes and tasks. The templates are HotDocs files with their own variables and logic. If the destination also works with HotDocs, they may be reused with remapped variables. Otherwise each template is rebuilt in the new system’s own tool.

  4. File room records

    LawBase is used for file room management, tracking physical files as well as electronic records. Those entries say where a paper file is. Few cloud systems have a file room module. The location data is brought across in custom fields, or exported as a register for whoever looks after the firm’s storage.

  5. Workflow fired by field changes

    Changing a single field can trigger an email, a document, other field updates, a note or calendar tasks. Over the years offices build many of these rules. They are listed during the analysis, because staff often no longer know which steps the system does for them until the new one fails to do it.

More about moving off LawBase

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

LawBase to SQLite: what firms ask

Our LawBase has thirty years of cases. Do they all move?

They can, but the office does not have to take them all. Open matters and those inside the retention period move as full records. Older ones can come across as a summary record with notes, or remain in the LawBase database kept read only. The office’s retention policy and how often old files are consulted decide the line.

Does LawBase hold our billing?

The vendor’s material describes case, matter and practice management and does not describe a billing ledger, so we do not assume one. If your office records time or costs in LawBase fields it designed, those are found in the analysis. Any separate billing system is scoped as its own source.

Can our custom screens be recreated?

The fields can, where the destination supports custom fields by matter type. Exact screen layouts usually cannot, and they are rarely worth chasing. We agree with each practice group which fields they still need on screen, load the rest where they can be reported on, and drop fields that have sat empty for years.

Does the copy in SQLite hold trust ledgers from LawBase?

That is confirmed in the analysis. We could not establish it from the two products’ own material, so it is checked against your data in LawBase before the plan is fixed.

What happens to records SQLite has no place for?

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

Emails and custom fields are exported with mapping, so each mapping is agreed with you first. Documents, time entries, billing records, trust ledgers, the firm’s accounts 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

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

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