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

Data migration route

Legal Files data to SQLite

Legal Files are 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 Legal Files hold and keeps it readable and open to queries.

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

What moves

What moves from Legal Files to SQLite

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

Records in Legal Files and their place in SQLite
RecordIn Legal FilesIn SQLiteWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldAny type of case or matter, as configured by the organisation.Has a placeA matters table keyed by matter number.Exported in full
ContactsClients, other parties and referrersHeldContact management with checks for duplicate entries.Has a placeContacts and their roles on matters as linked tables.Exported in full
DocumentsFiles stored in or linked from the systemHeldDocument management with text searching.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 storeHeldTwo-way integration with Outlook and Gmail saves emails and attachments.Has a place in partAs message files in folders, indexed in a table.Exported with mapping
NotesFile notes, matter notes and contact notesHeldNotes, mail logs and phone logs.Has a placeA notes table linked to matters.Exported in full
CalendarAppointments, court dates and deadlinesHeldCalendaring with deadline tracking.Has a placeA table of dated entries, with no calendar view.Exported in full
TasksTo-dos and workflow steps assigned to peopleHeld in partWorkflows, alerts and follow-ups.Has 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 balancesHeld in partThe vendor lists eBilling among its functions.Has a placeInvoice and receipt tables; invoice PDFs kept as files.Exported in full
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 itselfHeldCustomers add and change fields and screens without programming.Has a placeColumns added to the table they belonged to.Exported with mapping
TemplatesPrecedents, document templates and automationHeldDocument assembly.No placePrecedent files are kept in folders, not in the database.Kept as a readable archive
IntakeLeads, enquiries, intake forms and pipelinesHeld in partLegal aid intake is among the uses the vendor describes.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 Legal Files.
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 Legal Files 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 Legal Files 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 Legal Files 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 Legal Files stays untouched until the copy in SQLite has been checked.

Where the data is now

Each office configured its own file types, fields and workflows, so one Legal Files system does not look like the next. The move starts with an inventory of that configuration. Then come the files, the people on them, documents and saved emails. Where the office is part of a government body or a company, retention rules and access restrictions on certain files have to survive the move as well.

  1. Configuration is the data model

    File types, screens and fields were set up by the office’s own administrator, often over many years. The field list has to be taken from that system, not assumed. Every custom field is reported with how many files use it, and the office picks the ones that deserve a place in the new system.

  2. Not built around billing

    Many of its users are in-house and government teams, which do not bill clients or hold trust money. If the destination is a law firm practice system, billing fields will be empty on every migrated matter. Where the office does record time or outside counsel spend, that is found in the analysis and mapped separately.

  3. Mail and phone logs

    Besides documents and emails, a file keeps logs of mail and of phone calls. Offices that answer to the public rely on these as the record of who was told what. They come across as dated notes on the matter with the log type kept, so they can still be filtered.

  4. Restricted files

    Investigations and other sensitive files are kept under controlled access. Those restrictions are extracted as a list of files and the users allowed to see them. The destination’s permissions are set from that list before the trial load is opened to staff, so restricted files are locked down before anyone else looks.

  5. On your servers or hosted

    The route to a copy of the data depends on where Legal Files runs. An on-premises site works through its own IT team. A hosted site works through the vendor. Government sites often need a security review before data leaves the building, and that review goes in the timetable.

More about moving off Legal Files

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

Legal Files to SQLite: what firms ask

Our system has been heavily customised. Does everything have to be rebuilt?

No. Custom fields that are still filled in are recreated. Ones that were abandoned years ago are reported and usually left behind. Workflows and document templates do not transfer between products, so the ones in regular use are rebuilt in the new system and the rest are retired.

Can saved emails stay attached to the right file?

Emails saved into Legal Files through its Outlook or Gmail integration are stored against the file, with attachments. They are loaded to the same matter in the destination with their sent date and sender kept. Counts are run per file, because saved emails are easy to lose in a move without anyone noticing.

What about records we are required to retain?

Retention obligations travel with the records, not the software. Files due to be kept are either loaded as closed matters or held in a read-only copy of Legal Files for the retention period. The choice is written down with the office’s records officer, along with who can reach the copy.

Does the copy in SQLite hold trust ledgers from Legal Files?

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 Legal Files before the plan is fixed.

What happens to records SQLite has no place for?

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

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

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

Moving from Legal Files 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.