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

Data migration route

CloudLex to LexWorkplace migration

CloudLex is a cloud case management system for personal injury work, 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.

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

What moves

What moves from CloudLex to LexWorkplace

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

Records in CloudLex and their place in LexWorkplace
RecordIn CloudLexIn LexWorkplaceWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldMatters with type, status and sub-status. Intakes are a separate record.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 firm-level directory, linked to matters by role.No placeOnly a client name, status, attorneys and tags.Kept as a readable archive
DocumentsFiles stored in or linked from the systemHeldPer matter, in categories and folders, with version control and party association.Has a placeFiled to a matter or to Firm Documents, in folders.Carried across
EmailsEmails saved to matters or to the storeHeldMatter email syncs with Microsoft 365. Gmail and Outlook add-ins file to a matter.Has a placeOn the matter’s Email tab, in their own folders.Carried across
NotesFile notes, matter notes and contact notesHeldMatter notes, also reachable from the global side panel.Has a placeAs Matter Notes on the matter’s Notes tab.Carried across
CalendarAppointments, court dates and deadlinesHeldEvents tied to the matter, including deadlines.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleHeldManual tasks and tasks generated by workflow templates.To 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 itselfTo be confirmedHas a place in partOld categories can become document types, statuses or tags.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeld in partWorkflow templates by matter type and status. Document templates were not confirmed.Has a place in partStored as files in Firm Documents.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldLead Manager and Intake Manager. An intake is converted to a matter.No placeKept as a readable archive

What the plans mean

Carried across
LexWorkplace has a place for this kind of record. It is loaded there and checked against CloudLex.
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 CloudLex 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 CloudLex 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 CloudLex for matters and billing, or into an archive.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of CloudLex 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 CloudLex is kept running until the checks on LexWorkplace are finished.

Where the data is now

Leaving CloudLex is a three-part job, because the firm’s records are split between Intake Manager, Matter Manager and Digital Archiver. Active matters carry the most structure, in the Details sections. Archived matters carry the most volume. The plan covers each part separately and states which archived files, if any, are being brought into the new system.

  1. The Details sections

    Medical information, medical bills, insurance, liens, expenses and settlement are separate sections of a matter, each a list of rows with amounts and dates. They map well to an injury-specific destination. In a general one, each section needs a home agreed in advance, and the outstanding balances on bills and liens are checked after loading.

  2. Closed matters in Digital Archiver

    Closed files are moved off the active list into Digital Archiver, where they stay searchable for the retention period. They are easy to forget when counting matters. The archive is inventoried at the start, and the firm chooses between loading those files, keeping an export, or leaving them where they are until retention ends.

  3. Negotiations and the settlement calculator

    A matter records its negotiations, and a calculator applies settlement rules to work out fees and the client’s share. The negotiation history is useful in the next system as a dated list. Calculator rules are firm settings, and they are entered again in the destination if it has an equivalent.

  4. Contacts linked by role

    One contact record serves every matter it appears on, as a provider, adjuster, attorney or referrer. That is tidy, and it means a merge or a typo affects many matters at once. Roles are extracted with the link, so an insurer on forty matters arrives once and is attached forty times.

  5. Client messages and texts

    Texts sent through Client Messenger are logged against the intake or matter. They are part of the file and often the only record of what a client was told. Such messages are carried as dated notes or as a transcript document on the matter, depending on what the destination can display.

More about moving off CloudLex

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 CloudLex and checking each trial against CloudLex.

  1. Analysis

    We read what CloudLex 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 CloudLex: 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 CloudLex, a final pass over a weekend picks up what changed since the trial. CloudLex 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 CloudLex 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 fromCloudLex
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 CloudLex 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

CloudLex to LexWorkplace: what firms ask

CloudLex calls them matters. Does that make the move simpler?

Only in the naming. The structure under a matter is still personal injury data: treatment, bills, liens, insurance and settlement. A destination that also says matter may have no sections for those. What decides the effort is whether the new system has a place for each Details section, and that is settled in the analysis.

What do we do about files in Digital Archiver?

Decide early. Archived matters are retained for years and are rarely opened, so loading them into the new system is optional. The options are a full load, a summary record with documents, or an export held by the firm. Whatever is chosen, the count of archived matters is agreed and checked.

Will emails filed to a matter come across?

Emails saved to a matter from Outlook, Gmail or the built-in mail are part of the matter record and are in scope. They move as email files or as documents, with the date sent preserved so the correspondence still sorts in order. Mailboxes themselves stay in Microsoft 365 or Google and are not touched.

Do trust balances in CloudLex 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 CloudLex 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, calendar entries and intake records. They are exported from CloudLex 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 CloudLex data is loaded into LexWorkplace?

Matters and templates are carried with mapping, so each mapping is agreed with you first. Tasks, time entries, billing records, trust ledgers, the firm’s accounts and custom fields 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

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

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