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

Data migration route

LawBase to LexWorkplace migration

LawBase is a case management system, and LexWorkplace is a cloud document management system. Documents and email move, filed under the matters they came from. Time, billing and trust have no place in a document system.

FromLawBaseCase management
  1. Emails: Carried across
  2. Notes: Carried across
  3. Matters: Carried with mapping
  4. Custom fields: Carried with mapping
  5. Templates: Carried with mapping
  6. Documents: Confirmed in the analysis
  7. Tasks: Confirmed in the analysis
  8. Time and expenses: Confirmed in the analysis
  9. Billing: Confirmed in the analysis
  10. Trust money: Confirmed in the analysis
  11. Firm accounts: Confirmed in the analysis
  12. Intake: Confirmed in the analysis
ToLexWorkplaceCloud
  1. Contacts: Kept as a readable archive
  2. Calendar: Kept as a readable archive
Readable archiveNo place in LexWorkplace
  • 2 carried
  • 3 mapped
  • 7 to confirm
  • 2 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from LawBase to LexWorkplace

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

Records in LawBase and their place in LexWorkplace
RecordIn LawBaseIn LexWorkplaceWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldScreens and fields are designed per office and practice area.Has a place in partName, custom ID, client, type, location, staff, tags and dates. No parties or financial fields.Carried with mapping
ContactsClients, other parties and referrersHeldA configurable address book; contacts are entered once and linked to matters.No placeOnly a client name, status, attorneys and tags.Kept as a readable archive
DocumentsFiles stored in or linked from the systemTo be confirmedHas a placeFiled to a matter or to Firm Documents, in folders.Confirmed in the analysis
EmailsEmails saved to matters or to the storeHeld in partBi-directional integration with Microsoft Outlook.Has a placeOn the matter’s Email tab, in their own folders.Carried across
NotesFile notes, matter notes and contact notesHeldCase notes of unlimited free text.Has a placeAs Matter Notes on the matter’s Notes tab.Carried across
CalendarAppointments, court dates and deadlinesHeldDocketing of appointments and tasks through the email calendar.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleHeldTo be confirmedConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledTo be confirmedNo placeConfirmed in the analysis
BillingInvoices, payments and debtor balancesTo be confirmedNo placeConfirmed in the analysis
Trust moneyTrust or client account ledgers and balancesTo be confirmedNo placeConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesTo be confirmedNo placeConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldThe whole database layout is defined by the office.Has a place in partOld categories can become document types, statuses or tags.Carried with mapping
TemplatesPrecedents, document templates and automationHeldDocument assembly through HotDocs.Has a place in partStored as files in Firm Documents.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedNo placeConfirmed in the analysis

What the plans mean

Carried across
LexWorkplace has a place for this kind of record. It is loaded there and checked against LawBase.
Carried with mapping
LexWorkplace 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
LexWorkplace has no place for it. It is exported in a format that opens without LawBase 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 documents move. The accounts do not.

Moving from a matter system into a document management system is a documents job. LexWorkplace has no place for time, invoices or trust, so there is no financial cutover on this route. What it does want is structure. Every document from LawBase is filed into a workspace or folder for its client and matter, with a profile that says what it is. The client and matter list becomes that structure, which is why it is cleaned before any file is copied.

A document’s own details count for more here than anywhere. Created and modified dates, author, document type and version become searchable profile fields, and a wrong date on a few thousand files is hard to undo. Email filed to matters is carried as messages. Document copies can be run again, so the trial is repeated until counts and dates agree. Matter data that LexWorkplace cannot hold goes to whatever replaces LawBase for matters and billing, or into an archive.

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

LexWorkplace expects every document and email to belong to a matter, so loading it starts with the matter list: name, custom ID, client, type and dates. Uptime Legal states that it runs migration and onboarding for its customers itself. The preparation is getting the old system’s content into a clean client and matter structure, with the exceptions resolved, ready for that load.

  1. Matters carry little, by design

    A matter record holds a name, a custom ID, a client, a type, a location, assigned staff, tags and open and close dates. Parties, court details and financial data have no fields. Those stay in the practice management system, and the two are tied together by using the same matter number as the custom ID.

  2. Clients are only containers

    LexWorkplace says plainly that its clients are for grouping matters, not for client management. A client has a name, a status, primary attorneys and tags. Addresses, phone numbers and contact history from the old system are not loaded here. They go to the practice management system or stay behind.

  3. Three tabs per matter

    Content arrives as documents, emails or notes, each on its own tab with its own folders. Emails held as message files in an old folder tree have to be recognised and loaded as emails, not as documents, or they will not appear where lawyers look for correspondence.

  4. Closed matters and archive

    A matter is closed by giving it a close date, and closed matters can be moved to archive storage, where they keep their place but are not searched or indexed until un-archived. Old matters can therefore be loaded and archived straight away. The firm sets the cut-off year.

  5. Profiling is optional unless enforced

    Document type, status and tags are not required by default, though a firm can switch on mandatory profiling for matters. If the old system had document types, they are mapped to LexWorkplace types during the load. If it had none, the firm chooses between loading unprofiled and assigning types by folder name.

More about moving into LexWorkplace

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in LexWorkplace on this route, which makes it repeatable: a load can be run again until it is right. The maker of LexWorkplace says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in LawBase and checking each trial against LawBase.

  1. Analysis

    We read what LawBase holds and how it is organised, then agree with you where each kind of record will sit in LexWorkplace. 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 LexWorkplace 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

    There is no financial cutover on this route. After a short freeze on changes in LawBase, a final pass over a weekend picks up what changed since the trial. 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 toLexWorkplace

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

Loaded data is not yet a working system. The maker of LexWorkplace runs or arranges the set-up of its product, so this is what has to be decided and put in place in LexWorkplace, whoever does the work, before people rely on it from the first day.

Setting LexWorkplace up for a firm is a short list of decisions made in its settings, plus software on each computer. The decisions are what the firm calls its matter types, document types and statuses, who can open which matters by default, and whether versioning is automatic or manual. The Launcher and the Outlook add-in are then installed for every user.

Set-up decisions in LexWorkplace

  • Matter types, document types, statuses and tag conventions
  • Groups, rights and default permissions for new matters
  • Automatic or manual versioning, and whether profiling is mandatory
  • Linking matters to Clio Manage where the firm uses it
  • Launcher, Office and Outlook add-ins on each Windows or Mac computer
  • A Firm Documents structure for templates, policies and internal files

Questions

LawBase to LexWorkplace: 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 LexWorkplace?

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

What happens to records LexWorkplace has no place for?

On this route that is contacts and calendar entries. They are exported from LawBase 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 LawBase data is loaded into LexWorkplace?

Matters, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Documents, tasks, 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 LexWorkplace are the names and marks of their owners, used here only to identify the two systems.

Moving from LawBase to LexWorkplace?

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

We reply within one business day.