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

Data migration route

CloudLex data to Full data export

CloudLex is a cloud case management system for personal injury work, 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 CloudLex holds and keeps it readable and open to queries.

FromCloudLexCloud
  1. Matters: Exported in full
  2. Contacts: Exported in full
  3. Documents: Exported in full
  4. Notes: Exported in full
  5. Calendar: Exported in full
  6. Tasks: Exported in full
  7. Emails: Exported with mapping
  8. Templates: Exported with mapping
  9. Intake: Exported with mapping
  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. Custom fields: Confirmed in the analysis
ToFull data exportFiles
  • 6 carried
  • 3 mapped
  • 5 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from CloudLex to Full data export

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

Records in CloudLex and their place in Full data export
RecordIn CloudLexIn Full data exportWhat 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 placeA matters table keyed by the original matter number.Exported in full
ContactsClients, other parties and referrersHeldA firm-level directory, linked to matters by role.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 systemHeldPer matter, in categories and folders, with version control and party association.Has a placeFiles under their original names, in client and matter folders.Exported in full
EmailsEmails saved to matters or to the storeHeldMatter email syncs with Microsoft 365. Gmail and Outlook add-ins file to a matter.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 notesHeldMatter notes, also reachable from the global side panel.Has a placeA notes table with matter, author and date for each note.Exported in full
CalendarAppointments, court dates and deadlinesHeldEvents tied to the matter, including deadlines.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 peopleHeldManual tasks and tasks generated by workflow templates.Has 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 itselfTo be confirmedHas a placeExtra columns under their original field names.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 partTemplate files only; the merge fields in them will not run.Exported with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldLead Manager and Intake Manager. An intake is converted to a matter.Has a place in partAn enquiries table, where the source tracked leads.Exported with mapping

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

CloudLex is hosted by its maker and Full data export sits on equipment the firm controls. The data leaves a service that was backed up for the firm and arrives somewhere the firm must back up itself, so backup and access are arranged before the export is copied in. What CloudLex will release depends on its export tools, and that is confirmed in the analysis.

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

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 CloudLex holds, table by table, and agree with you what the copy in Full data export must be able to answer later. Everything CloudLex 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 CloudLex: record counts, totals where CloudLex 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 CloudLex, the export is run a final time and checked again. There is nothing to go live. CloudLex 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 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 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 CloudLex 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

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

Does the copy in Full data export hold trust ledgers from CloudLex?

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.

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

Most of it does on paper. Time entries, billing records, trust ledgers, the firm’s accounts and custom fields 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 CloudLex is written out to Full data export?

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

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

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