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

Data migration route

CloudLex to SharePoint migration

CloudLex is a cloud case management system for personal injury work, and SharePoint is cloud file storage. Documents move into a folder for each client and matter, and the data behind them is kept as an export.

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

What moves

What moves from CloudLex to SharePoint

Each row is a kind of record CloudLex holds, whether SharePoint has a place for it, and what is planned. On this route one kind of record carries across, seven kinds need mapping, one kind has no place in SharePoint and is archived and five kinds are confirmed in the analysis.

Records in CloudLex and their place in SharePoint
RecordIn CloudLexIn SharePointWhat 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 partAs a site, library, folder or list row the firm designs; no built-in matter record.Carried with mapping
ContactsClients, other parties and referrersHeldA firm-level directory, linked to matters by role.Has a place in partOnly as rows in a list built for the purpose.Carried with mapping
DocumentsFiles stored in or linked from the systemHeldPer matter, in categories and folders, with version control and party association.Has a placeFiles in libraries, with columns and versions.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 place in partAs .msg or .eml files, with columns for sender and date if set up.Carried with mapping
NotesFile notes, matter notes and contact notesHeldMatter notes, also reachable from the global side panel.Has a place in partAs documents, or as rows in a notes list if one is built.Carried with mapping
CalendarAppointments, court dates and deadlinesHeldEvents tied to the matter, including deadlines.Has a place in partPossible as a list; usually left in Outlook.Carried with mapping
TasksTo-dos and workflow steps assigned to peopleHeldManual tasks and tasks generated by workflow templates.Has a place in partPossible as a list; no legal workflow built in.Carried with mapping
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 placeColumns and content types on libraries and lists.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 partPrecedents as files; templates can be offered from a library.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
SharePoint has a place for this kind of record. It is loaded there and checked against CloudLex.
Carried with mapping
SharePoint 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
SharePoint 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

Out of the system, into folders the firm can read.

File storage has folders and files and nothing else. Moving from CloudLex into SharePoint means turning matters into a folder tree, usually client, then matter, then the folders used inside it. The naming rule is agreed first, because it is hard to change once thousands of folders exist: whether the matter number leads, how closed matters are separated, what happens to characters SharePoint does not allow in a name.

Everything that is not a document needs somewhere to go. Contacts, notes, time, invoices and trust ledgers have no place in a folder, so they are exported as spreadsheets and reports and stored alongside, often as a summary file in each matter folder and a full set in an archive area. Firms choose this route to keep a readable copy of a system they are retiring, or as a staging step. The export is checked either way: folders against matters, files against the document register in CloudLex.

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 SharePoint 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

SharePoint will take a firm’s documents in almost any arrangement, which is the difficulty. The structure has to be chosen before the load: what a client is, what a matter is, and where security is applied. Changing it afterwards means moving every file again. Most of the effort goes into that design and into the columns that describe each document.

  1. Site, library or folder per matter

    A matter can be a site, a library within a client site, or a folder in one large library. Each choice has consequences for permissions, for search and for how a new matter is opened. The firm makes that decision, and the people who open matters every day should be part of it.

  2. Columns are built before content

    If documents are to carry matter number, client, document type or author as columns, those columns and any content types exist before loading, so each file can be tagged as it arrives. Tagging hundreds of thousands of documents afterwards is a second project that seldom gets finished.

  3. The 400 character path

    SharePoint limits the full decoded path, site and library and folders and file name, to 400 characters. A deep tree copied from a server drive under a long site name can cross it. Path lengths are calculated against the planned structure, not the old one, before any file moves.

  4. Large libraries and the view threshold

    A library can hold millions of files, but a view that tries to show more than 5,000 items at once runs into the list view threshold. One flat library with a folder per matter needs indexed columns and filtered views from the start, or views begin to fail as the library fills.

  5. Security by library, not by file

    Microsoft supports up to 50,000 unique permissions in a library and recommends staying under 5,000. Restricting matters one folder at a time reaches that sooner than firms expect. Restricted work is better grouped into its own site or library, so the permission is set once.

More about moving into SharePoint

How NewLaw runs it

Four steps, in this order.

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

  1. Analysis

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

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

SharePoint is storage, not an application, so there is no product to configure. What is agreed and set up is the folder structure, who can open what, and how the result is handed to the firm.

Making SharePoint work as a firm’s document store is a design and build job in its own right. The sites, libraries, columns and permission groups are created, a way of opening a new matter is put in place so the structure repeats itself, and the Outlook and Teams habits around it are agreed. Search is tested with real questions from fee earners.

What is agreed and set up

  • Site and library structure for clients and matters
  • Columns and content types for matter number and document type
  • Permission groups, with restricted matters in their own libraries
  • A repeatable way to create each new matter’s workspace
  • Version history limits and retention labels for closed matters
  • Views, indexed columns and search tested on loaded data

Questions

CloudLex to SharePoint: 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 SharePoint?

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 SharePoint 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 SharePoint has no place for?

On this route that is 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 SharePoint?

Matters, contacts, emails, notes, calendar entries, tasks and templates are carried 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 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 SharePoint are the names and marks of their owners, used here only to identify the two systems.

Moving from CloudLex to SharePoint?

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

We reply within one business day.