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

Data migration route

Liberate data to SQLite

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

FromLiberatePractice management
  1. Matters: Exported in full
  2. Tasks: Exported in full
  3. Time and expenses: Exported in full
  4. Billing: Exported in full
  5. Firm accounts: Exported in full
  6. Documents: Exported with mapping
  7. Emails: Exported with mapping
  8. Contacts: Confirmed in the analysis
  9. Notes: Confirmed in the analysis
  10. Calendar: Confirmed in the analysis
  11. Trust money: Confirmed in the analysis
  12. Custom fields: 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 Liberate to SQLite

Each row is a kind of record Liberate 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 Liberate and their place in SQLite
RecordIn LiberateIn SQLiteWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldElectronic matters holding data, documents and emails.Has a placeA matters table keyed by matter number.Exported in full
ContactsClients, other parties and referrersTo be confirmedHas a placeContacts and their roles on matters as linked tables.Confirmed in the analysis
DocumentsFiles stored in or linked from the systemHeldTags and definable document categories, with version control.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 storeHeldEmails are held on the matter; time spent in Outlook can be recorded.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 deadlinesTo be confirmedHas a placeA table of dated entries, with no calendar view.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleHeld in partAuthorisation workflows and business process automation.Has a placeA table of tasks and their status at the final date.Exported in full
Time and expensesTime and expense entries, billed and unbilledHeldIncludes automatic time recording.Has a placeA table of time and expense entries.Exported in full
BillingInvoices, payments and debtor balancesHeldOne-click and scheduled billing, with credit control procedures.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 payablesHeldPurchase ledger, supplier database and built-in financial reporting.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 automationHeldPrecedents and document templates filled with matter data.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 Liberate.
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 Liberate 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 Liberate 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 Liberate 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 Liberate 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 Liberate stays untouched until the copy in SQLite has been checked.

Where the data is now

Linetime sells Liberate to larger firms, which tend to have high matter volumes and an accounts department that runs credit control inside the system. Customisation by Linetime is part of the offer. A move therefore begins with an inventory of what was changed for this firm, and with the accounts team, whose billing schedules, credit control procedures and purchase ledger all have to be closed off or carried over.

  1. Customised for the firm

    Linetime offers customisation to meet a firm’s own needs, and long-standing clients may have screens, fields and processes built for them. Those additions are not in any manual. We ask the firm and the vendor for a list, then confirm it against the database, so a field built only for this firm is not missed.

  2. Categories and tags, not folders

    Documents are organised by tags and by categories the firm defines. A matter’s documents may never have been in a folder. For a destination that files by folder, the category becomes the folder name, tags are carried as metadata where the new system has it, and uncategorised documents are placed in a general folder for review.

  3. Documents under version control

    Liberate keeps documents under version control. A migration normally takes the latest version of each document. Where the firm needs earlier drafts, we establish how Liberate stores them and whether the destination has its own versioning to receive them, then test on a matter with a long drafting history.

  4. Credit control procedures

    Credit control is run inside Liberate, with procedures that can be set at client and matter level. An unpaid bill may be part-way through a chasing sequence at cutover. The debtor balances move as figures. Alongside them, the stage each debt has reached is exported as a list so the accounts team can pick up the chase.

  5. Scheduled bills in progress

    Billing can be scheduled, so some clients are billed automatically on set dates. Those schedules do not transfer. They are listed before cutover with their amounts and dates, the last scheduled run is completed in Liberate, and the equivalent arrangement is set up in the new system before the next one falls due.

More about moving off Liberate

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

Liberate to SQLite: what firms ask

How do we find out what was customised for us?

Start with the people who asked for it: accounts, department heads, IT. Linetime’s records of development work for the firm help as well. We then compare the firm’s database with the list, looking for tables and fields that hold data but appear in nobody’s account, and ask what they were for.

Does our purchase ledger move?

Only if the new system, or an accounting package beside it, has a purchase ledger. Supplier records and unpaid supplier invoices are extracted and loaded there as opening items. Paid history stays in the archive. A firm moving to a product without office accounts decides on its accounting package during the analysis.

Can the move be staged by department?

Case data can sometimes be staged. Accounts cannot be split easily, because billing and the ledgers for the whole firm sit in one system. Running two systems also means two places to check conflicts. Most firms move everything in one cutover and stage the training instead.

Does the copy in SQLite hold trust ledgers from Liberate?

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

What happens to records SQLite has no place for?

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

Documents and emails are exported with mapping, so each mapping is agreed with you first. Contacts, notes, calendar entries, trust ledgers, custom fields 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

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

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