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

Data migration route

LexWorkplace data to SQLite

LexWorkplace is a cloud document management system, and SQLite is a store of data kept as files the firm holds. What lands in SQLite is the register: every file’s name, place, dates and details, with the files themselves stored beside it.

FromLexWorkplaceCloud
  1. Matters: Exported in full
  2. Notes: Exported in full
  3. Documents: Exported with mapping
  4. Emails: Exported with mapping
  5. Custom fields: Exported with mapping
  6. Tasks: Confirmed in the analysis
ToSQLiteFiles
  1. Templates: Kept as a readable archive
Readable archiveNo place in SQLite
  • 2 carried
  • 3 mapped
  • 1 to confirm
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from LexWorkplace to SQLite

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

Records in LexWorkplace and their place in SQLite
RecordIn LexWorkplaceIn SQLiteWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeld in partName, custom matter ID, client, type, location, assigned staff, tags, open and close dates.Has a placeA matters table keyed by matter number.Exported in full
DocumentsFiles stored in or linked from the systemHeldAny file type, in folders within a matter, with type, status, tags 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 storeHeldSaved to a matter from Outlook, with their own folders on the matter’s Email tab.Has a place in partAs message files in folders, indexed in a table.Exported with mapping
NotesFile notes, matter notes and contact notesHeldRich-text Matter Notes, kept beside the matter’s documents and email.Has a placeA notes table linked to matters.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
Custom fieldsFields and record types the firm added itselfHeld in partFirm-defined document types, statuses, tags and matter types.Has a placeColumns added to the table they belonged to.Exported with mapping
TemplatesPrecedents, document templates and automationHeld in partTemplates are stored as files in Firm Documents and copied into matters.No placePrecedent files are kept in folders, not in the database.Kept as a readable archive

What the plans mean

Exported in full
SQLite has a place for this kind of record. It is loaded there and checked against LexWorkplace.
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 LexWorkplace 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

The files, and a register of what each one is.

A database is a poor place to keep documents and a good place to keep facts about them. On this route the files from LexWorkplace are exported to storage the firm controls, and SQLite receives the register: one row per file, with its path, size, dates, author and whatever profile or folder details existed. That register is what makes a large export searchable. It also proves completeness, since the row count and total size can be agreed to the source.

How useful the register is depends on how much LexWorkplace knows about each file. A document management system has a profile to carry. A plain folder has only a path and dates, and the client or matter has to be read out of folder names. Where versions or an audit history exist, each becomes a table of its own. The export is checked by picking documents at random in the source, finding them through SQLite, and opening the file to confirm it is the same one.

LexWorkplace is hosted by its maker and SQLite sits on equipment the firm controls. The data leaves a service that was backed up for the firm and arrives somewhere the firm must back up itself, so backup and access are arranged before the export is copied in. What LexWorkplace will release depends on its export tools, and that is confirmed in the analysis.

Where the data is now

A matter can be exported from LexWorkplace as a zip file, with its documents and emails in the folder structure the firm built. That export leaves out three things that usually matter: the matter notes, the matter’s own details, and earlier versions of documents. A full move collects those separately and joins them back to the right matter before anything is loaded elsewhere.

  1. What the matter export omits

    Export Matter gives a Documents folder and an Email folder. Matter Notes are not in it, nor are previous versions, nor the matter’s custom ID, client, type, staff and dates. Matter details can be exported to CSV from the matters list. The plan sets out how notes and versions are obtained, and whether older versions are needed at all.

  2. Custom Matter ID is the key

    LexWorkplace lets a firm give each matter a custom ID so that it matches the number in the practice management system. Where firms have used it consistently, documents line up with matters in the destination by that number. Where it is blank or free-typed, matters are matched by name and client, and the doubtful ones are listed.

  3. Automatic versioning adds up

    By default every save from Word makes a new numbered version, so a heavily edited contract can carry dozens. Firms on manual versioning have fewer, numbered 1.0, 1.1, 2.0. The analysis reports version counts so the firm can choose between bringing all of them, the latest only, or the latest plus the first.

  4. Trash and archive states

    Each matter, folder and item is active, archived or in the Trash Bin. Archived content stays in place but is not indexed or searched, and a matter export includes trashed items that have not been permanently deleted. Both need a decision before extraction, or deleted drafts reappear in the new system.

  5. Firm Documents sit outside matters

    Templates, policies and other internal files are kept in Firm Documents, which behaves like a matter but belongs to no client. It has no single export button: items are selected and downloaded. It is easy to leave off the list, and it is where the firm’s own templates are kept.

More about moving off LexWorkplace

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

LexWorkplace to SQLite: what firms ask

Does the matter export include our notes and old versions?

No. LexWorkplace’s own help says an exported matter contains documents and email, and does not include Matter Notes, matter details or previous versions of documents. Matter details can be exported to CSV separately. If notes and versions are needed in the next system, they are collected another way, and that is scoped in the analysis.

We use Clio Manage with LexWorkplace. What moves where?

Clio holds the clients, contacts, time, bills and trust records. LexWorkplace holds the documents, emails and notes, linked matter to matter. If both are being replaced, the two are extracted separately and joined on the matter. If only one is changing, the link to the other has to be rebuilt against the new matter numbers.

Does the copy in SQLite hold documents from LexWorkplace?

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 LexWorkplace.

What happens to records SQLite has no place for?

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

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

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

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