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

Data migration route

LawBase data to Full data export

LawBase is a case management system, and Full data export 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. Templates: Exported with mapping
  9. Documents: Confirmed in the analysis
  10. Time and expenses: Confirmed in the analysis
  11. Billing: Confirmed in the analysis
  12. Trust money: Confirmed in the analysis
  13. Firm accounts: Confirmed in the analysis
  14. Intake: Confirmed in the analysis
ToFull data exportFiles
  • 5 carried
  • 3 mapped
  • 6 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from LawBase to Full data export

Each row is a kind of record LawBase holds, whether Full data export has a place for it, and what is planned. On this route five kinds of record carry across, three kinds need mapping and six kinds are confirmed in the analysis.

Records in LawBase and their place in Full data export
RecordIn LawBaseIn Full data exportWhat 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 the original matter number.Exported in full
ContactsClients, other parties and referrersHeldA configurable address book; contacts are entered once and linked to matters.Has a placeA contacts table and a table of each contact’s role on each matter.Exported in full
DocumentsFiles stored in or linked from the systemTo be confirmedHas a placeFiles under their original names, in client and matter folders.Confirmed in the analysis
EmailsEmails saved to matters or to the storeHeld in partBi-directional integration with Microsoft Outlook.Has a place in partFiled emails as message files in the matter’s folder, if the source exposes them.Exported with mapping
NotesFile notes, matter notes and contact notesHeldCase notes of unlimited free text.Has a placeA notes table with matter, author and date for each note.Exported in full
CalendarAppointments, court dates and deadlinesHeldDocketing of appointments and tasks through the email calendar.Has a placeA table of appointments and key dates; nothing shows it as a diary.Exported in full
TasksTo-dos and workflow steps assigned to peopleHeldHas a placeA table of tasks with assignee, due date and status.Exported in full
Time and expensesTime and expense entries, billed and unbilledTo be confirmedHas a placeA time entries table with fee earner, matter, units, rate and billed status.Confirmed in the analysis
BillingInvoices, payments and debtor balancesTo be confirmedHas a placeInvoice, line and receipt tables; invoice PDFs can be kept beside them.Confirmed in the analysis
Trust moneyTrust or client account ledgers and balancesTo be confirmedHas a placeA trust transactions table; ledger reports can be kept as PDF beside it.Confirmed in the analysis
Firm accountsGeneral ledger, office account and payablesTo be confirmedHas a place in partJournals and account balances, where the source held a general ledger.Confirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldThe whole database layout is defined by the office.Has a placeExtra columns under their original field names.Exported with mapping
TemplatesPrecedents, document templates and automationHeldDocument assembly through HotDocs.Has a place in partTemplate files only; the merge fields in them will not run.Exported with mapping
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas a place in partAn enquiries table, where the source tracked leads.Confirmed in the analysis

What the plans mean

Exported in full
Full data export has a place for this kind of record. It is loaded there and checked against LawBase.
Exported with mapping
Full data export 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.

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 Full data export 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 Full data export 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 full export is judged by whether a stranger can use it. In five years the question will be something like: what was the trust balance on this matter the day it closed, and where is the signed agreement. The export is planned backwards from questions of that kind, and it is checked against the live system while the live system can still be opened.

  1. Tables that still join up

    Each kind of record becomes its own table: matters, contacts, time entries, invoices, trust transactions. The identifiers that link them are kept in every table, so a time entry can still be traced to its matter and its fee earner. An export that keeps the rows and drops the keys cannot be rejoined later.

  2. Documents with an index

    Documents are written to folders by client and matter under their original names. On their own they can be found only by name. An index listing each file with its matter number, title, author, dates and path is what lets someone find the right version of a lease among forty thousand files without the old system’s search. What the index records is settled in the analysis.

  3. Reports a person can read

    Raw tables do not satisfy an auditor or a former client. The firm decides which reports are also printed to PDF from the old system as at the final date: trust ledgers, matter ledgers, debtor lists and issued invoices are the usual candidates. They cannot be regenerated once the licence ends.

  4. What an export does not keep

    Screens, workflows, document automation, saved searches and user permissions belong to the software and stay with it. Figures the system calculated on the fly, such as a matter’s unbilled total, exist in an export only if they were captured as a report. The firm is told which of these are being let go.

  5. Checked while the source is open

    Record counts and financial totals in the export are reconciled to the live system: number of matters, sum of trust balances, total debtors, document count per matter on a sample. This is done before the subscription lapses or the server is turned off, because afterwards there is nothing left to compare against.

More about moving into Full data export

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 Full data export 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 Full data export 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 toFull data export

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 Full data export. 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

Full data export 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.

With no product to configure, the set-up is custody, and the decisions are the firm’s. Someone there owns the export, knows where it is kept and can open it. Access needs restricting, because it contains every client’s affairs in one place with none of the old system’s security. The firm sets a destruction date from its retention obligations and decides how the next custodian will learn to use it.

What is agreed and set up

  • Folder layout for tables, documents and reports
  • What the key to tables, columns and identifiers records
  • Where the copies are stored and who is custodian
  • Who may open it, as approved by a partner
  • Which look-ups staff must be able to do unaided
  • Retention period and the date it is next reviewed

Questions

LawBase to Full data export: 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 Full data export 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.

Does everything in LawBase have a place in Full data export?

Most of it does on paper. Documents, time entries, billing records, trust ledgers, the firm’s accounts and intake records could not be confirmed from the two products’ own material, so those are checked in the analysis. Anything that turns out to have no place in Full data export is kept as a readable archive, and you see which before the move.

What has to be decided before LawBase is written out to Full data export?

Emails, custom fields and templates 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 Full data export are the names and marks of their owners, used here only to identify the two systems.

Moving from LawBase to Full data export?

Tell us what you are moving. You get a plan and a fixed price after the analysis.

We reply within one business day.