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

Data migration route

LexWorkplace to SimpleLaw migration

LexWorkplace is a cloud document management system, and SimpleLaw is a cloud practice management system. Documents and email move out of a store organised by profile and onto the matters they belong to.

FromLexWorkplaceCloud
  1. Matters: Carried across
  2. Documents: Carried across
  3. Notes: Carried across
  4. Custom fields: Carried with mapping
  5. Templates: Carried with mapping
  6. Emails: Confirmed in the analysis
  7. Tasks: Confirmed in the analysis
ToSimpleLawCloud
  • 3 carried
  • 2 mapped
  • 2 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from LexWorkplace to SimpleLaw

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

Records in LexWorkplace and their place in SimpleLaw
RecordIn LexWorkplaceIn SimpleLawWhat 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 placeCarried across
DocumentsFiles stored in or linked from the systemHeldAny file type, in folders within a matter, with type, status, tags and versions.Has a placeUploaded to SimpleLaw storage or held in a linked Dropbox, Google Drive or OneDrive.Carried across
EmailsEmails saved to matters or to the storeHeldSaved to a matter from Outlook, with their own folders on the matter’s Email tab.To be confirmedConfirmed in the analysis
NotesFile notes, matter notes and contact notesHeldRich-text Matter Notes, kept beside the matter’s documents and email.Has a placeCarried across
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeld in partFirm-defined document types, statuses, tags and matter types.Has a placeCarried with mapping
TemplatesPrecedents, document templates and automationHeld in partTemplates are stored as files in Firm Documents and copied into matters.Has a place in partTemplates are rebuilt using SimpleLaw’s own automation.Carried with mapping

What the plans mean

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

Profiled documents become matter documents.

A document management system files by profile: client, matter, author, document type, version. A practice management system files by matter. The move from LexWorkplace to SimpleLaw is a translation from one to the other, and it depends on the client and matter numbers in LexWorkplace matching matters that exist in SimpleLaw. Where they do not match, documents have nowhere to land. So the matter list is settled first and the documents follow it.

Versions and security each need a decision. Some practice systems keep every version of a document, others keep the latest and treat the rest as separate files. A restricted workspace has to become a restricted matter, or the restriction is lost on the way. Filed email comes across as message files against the matter. A document store holds no ledgers, so this route has no financial cutover.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of LexWorkplace depends on its export tools and on what its maker provides on request, and that is confirmed during the analysis, before a date is set. The subscription to LexWorkplace is kept running until the checks on SimpleLaw are finished.

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

Loading a firm into SimpleLaw is mostly a job of sorting contacts and setting up each matter’s billing type. The CRM holds leads, clients and everyone else, so every incoming contact needs a status. Where documents will be stored is decided early as well, since that choice determines where the files are sent. Accounting history stays in QuickBooks or the old system.

  1. Lead, client or contact

    A person is tracked from first enquiry to client in one CRM, with tasks and appointments kept against the contact. Source systems that only ever held clients load simply. Systems with separate intake records need each enquiry classed as a live lead, a lost one or a duplicate of an existing client.

  2. Billing type on each matter

    Every matter is billed as hourly, flat fee, instalments, contingency, pro bono, trust or LEDES. The source may record this loosely or not at all. During the trial load a billing type is set on each matter and checked by the person who raises the bills, because it controls how the invoice is built.

  3. Storage chosen before loading

    If the firm stores documents with SimpleLaw, files are uploaded against each matter. Where it prefers Dropbox, Google Drive or OneDrive, the files go there, and what the connection does with folders already in place is checked first. Switching later means moving everything again, so the choice is made at the start with the firm’s IT support.

  4. Custom fields named for templates

    Custom fields supply intake forms and document automation as well as reports. A field brought across from the old system is only useful if templates can call on it. Fields are therefore named and typed with the firm’s main documents in mind, and one template is tested against loaded data.

  5. Portal access client by client

    The client portal is optional and the firm chooses who has access and what each client can see. Nothing is exposed by loading data. After go-live, access is switched on for chosen clients, starting with a few, once the firm has reviewed what their matters show.

More about moving into SimpleLaw

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in SimpleLaw on this route, which makes it repeatable: a load can be run again until it is right.

  1. Analysis

    We read what LexWorkplace holds and how it is organised, then agree with you where each kind of record will sit in SimpleLaw. 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 SimpleLaw and checked against LexWorkplace: 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 LexWorkplace, a final pass over a weekend picks up what changed since the trial. LexWorkplace 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 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 toSimpleLaw

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

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

The set-up work is in making the product reflect the firm. Labels are adjusted to the firm’s terms. Intake forms and the custom fields behind them are built for each practice area, then document templates are made to draw on those fields. Workflows are written for the case types that follow a standard path, and the QuickBooks and payment connections are made last.

Set-up decisions in SimpleLaw

  • Labels for documents, activities, expenses and contact IDs
  • Custom fields and intake forms for each practice area
  • Document templates and the attorney-client agreement
  • Workflows for case types that follow a standard process
  • User permission sets and client portal visibility
  • QuickBooks connection and the online payment processor

Questions

LexWorkplace to SimpleLaw: 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.

Do documents from LexWorkplace keep their folders and dates in SimpleLaw?

SimpleLaw stores documents. Uploaded to SimpleLaw storage or held in a linked Dropbox, Google Drive or OneDrive. Each file is placed under the client and matter it came from, and created and modified dates are carried, so a document still shows when it was written. The trial load is checked by count and by opening a sample.

Does everything in LexWorkplace have a place in SimpleLaw?

Most of it does on paper. Emails and tasks 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 SimpleLaw is kept as a readable archive, and you see which before the move.

What has to be decided before LexWorkplace data is loaded into SimpleLaw?

Custom fields and templates are carried with mapping, so each mapping is agreed with you first. Emails and tasks 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

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

Moving from LexWorkplace to SimpleLaw?

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

We reply within one business day.