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

Data migration route

LawBase to Lawmatics migration

LawBase is a case management system, and Lawmatics is a cloud CRM and intake system. This route carries people and their history into Lawmatics, and the table shows how much of the firm’s files and money has a place there.

FromLawBaseCase management
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Notes: Carried across
  4. Calendar: Carried across
  5. Tasks: Carried across
  6. Emails: Carried with mapping
  7. Custom fields: Carried with mapping
  8. Templates: Carried 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
ToLawmaticsCloud
  • 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 Lawmatics

Each row is a kind of record LawBase holds, whether Lawmatics 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 Lawmatics
RecordIn LawBaseIn LawmaticsWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldScreens and fields are designed per office and practice area.Has a placeLoaded from CSV with a status of PNC, Hired or Lost and a pipeline stage.Carried across
ContactsClients, other parties and referrersHeldA configurable address book; contacts are entered once and linked to matters.Has a placeContacts and companies load from CSV; relationships link further parties to a matter.Carried across
DocumentsFiles stored in or linked from the systemTo be confirmedHas a place in partFiles and folders on each matter, added by upload or API, not by the spreadsheet import.Confirmed in the analysis
EmailsEmails saved to matters or to the storeHeld in partBi-directional integration with Microsoft Outlook.Has a place in partEmails reach a matter through mail sync from a connected mailbox.Carried with mapping
NotesFile notes, matter notes and contact notesHeldCase notes of unlimited free text.Has a placeNotes on matters, contacts and companies.Carried across
CalendarAppointments, court dates and deadlinesHeldDocketing of appointments and tasks through the email calendar.Has a placeAppointments, called events, with types and locations.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldHas a placeCarried across
Time and expensesTime and expense entries, billed and unbilledTo be confirmedHas a place in partTime entries and expenses, where the Time & Billing module is enabled.Confirmed in the analysis
BillingInvoices, payments and debtor balancesTo be confirmedHas a place in partInvoices and payments; a past invoice is entered as sent, then marked paid.Confirmed in the analysis
Trust moneyTrust or client account ledgers and balancesTo be confirmedHas a place in partA trust account with a running balance; deposits are allocated to a contact and matter.Confirmed in the analysis
Firm accountsGeneral ledger, office account and payablesTo be confirmedNo placeNo 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 placeMatter, contact and company fields. A field must exist before data is imported into it.Carried with mapping
TemplatesPrecedents, document templates and automationHeldDocument assembly through HotDocs.Has a place in partDocument and email templates are rebuilt with Lawmatics merge fields.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas a placePipelines and stages, marketing sources and campaigns.Confirmed in the analysis

What the plans mean

Carried across
Lawmatics has a place for this kind of record. It is loaded there and checked against LawBase.
Carried with mapping
Lawmatics 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

People and history move. Files and accounts stay.

A CRM wants to know who the firm knows and what has passed between them. From LawBase that means contacts, their roles, their matters as a history of work done, and the referrers who sent them. Loaded into Lawmatics, a past client becomes someone the firm can contact again with that history in view. That is usually the reason for this route: the firm is adding an intake and marketing system beside its matter system, or replacing the front end of it.

A CRM is not usually where documents, time, billing and trust are kept, and the table above shows what Lawmatics takes. What it does not take stays in LawBase or its successor. So the plan has to say which system is the master for a contact once both are running, or the two lists drift apart. Contacts are de-duplicated before the load, and anyone who has asked not to be contacted is flagged in Lawmatics from the first day.

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. LawBase runs on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. Lawmatics is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.

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

Lawmatics takes matters, contacts and companies from CSV files, and its API accepts notes, tasks, appointments, files, time entries and invoices. It is an intake and client relationship system, so a firm arriving from full practice management has to decide what it is for. People and matters load well. There is no general ledger, and years of billing history have no natural home.

  1. Contacts and matters load separately

    The import expects two spreadsheets: one for contacts or companies with no case, such as referrers and other lawyers, and one for matters. A matter import creates the matter and its primary contact together. Every matter has exactly one primary contact, so joint clients are loaded as one primary and one relationship.

  2. Set up before loading

    Owner, stage, practice area, source and campaign are matched by name. A value on the spreadsheet that does not match one in Lawmatics exactly creates a new one, which is how a firm ends up with two spellings of the same practice area. Users, pipelines, practice areas and marketing sources are set up first, and custom fields must exist before data is loaded into them.

  3. Statuses and matter numbers

    Each imported matter must be PNC (potential new client), Hired or Lost, with open and closed handled as sub-statuses the firm creates. The case number is a system field assigned by an auto-numbering pattern and cannot be edited by hand afterwards. Whether old matter numbers can be loaded into it, or belong in a custom field, is tested in the trial load.

  4. Duplicates are matched by email

    With Match Contacts by Email switched on, a contact whose email already exists is skipped or updated, never doubled. Names and phone numbers are not checked. Matters are not deduplicated at all, so two rows with one email create two matters on one contact. Clean-up therefore happens in the spreadsheet, and automations are switched off for every load.

  5. What has no place

    There is no general ledger. The Time & Billing module holds time entries, expenses, invoices and a trust account with a running balance per matter, and past invoices are entered as already sent and then marked paid. A firm that needs its full accounting history keeps the old system read only or carries the books in an accounting package.

More about moving into Lawmatics

How NewLaw runs it

Four steps, in this order.

No financial cutover is planned on this route, so a load can be run again until it is right. If the analysis finds financial records with a place in Lawmatics, they get a rehearsed cutover of their own.

  1. Analysis

    We read what LawBase holds and how it is organised, then agree with you where each kind of record will sit in Lawmatics. Anything with no place there stays behind or is archived, and you see which before the move.

  2. Clean-up

    Duplicate clients, matters and folders are merged where they can be identified, and naming is put into one format, before anything is copied. It is not always possible to find every one, so some may carry across.

  3. Trial load

    A trial is loaded into Lawmatics and checked against LawBase: record and file counts, the links between records, document dates, and a sample opened by your own people. Exceptions are listed for you to decide.

  4. Cutover

    After a short freeze on changes in LawBase, a final pass over a weekend picks up what changed since the trial. If the analysis found financial records to move, their cutover is rehearsed on a full trial load first. LawBase is kept read only as the fall-back record.

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 toLawmatics

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

Setting up Lawmatics

Loaded data is not yet a working system. This is what NewLaw sets up in Lawmatics, beyond the migration, so that people can work in it from the first day.

In Lawmatics the design comes before the data. The pipeline stages, practice areas, custom fields and relationship types decide what the import can hold, and the forms and automations decide what the firm’s intake looks like from the first day. If a practice system sits behind it, the field mapping between the two is part of the same job.

Set-up decisions in Lawmatics

  • Pipelines and stages for intake and for open matters
  • Practice areas, sub-statuses, relationship types and the matter numbering pattern
  • Custom fields on matters, contacts and companies
  • Intake forms, booking links and e-signature document templates
  • Follow-up automations, with marketing sources and campaigns
  • Mail and calendar sync, user roles and practice system integration

Questions

LawBase to Lawmatics: 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.

Do trust balances in LawBase have a place in Lawmatics?

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. If Lawmatics turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.

Does everything in LawBase have a place in Lawmatics?

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 Lawmatics is kept as a readable archive, and you see which before the move.

What has to be decided before LawBase data is loaded into Lawmatics?

Emails, custom fields and templates are carried 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 which closed matters and how many versions of a document are in scope.

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 Lawmatics are the names and marks of their owners, used here only to identify the two systems.

Moving from LawBase to Lawmatics?

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

We reply within one business day.