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

Data migration route

Lawcus to SharePoint migration

Lawcus is a cloud practice management system, 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.

FromLawcusCloud
  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. Custom fields: Carried with mapping
  9. Templates: Carried with mapping
ToSharePointCloud
  1. Time and expenses: Kept as a readable archive
  2. Billing: Kept as a readable archive
  3. Trust money: Kept as a readable archive
  4. Intake: Kept as a readable archive
Readable archiveNo place in SharePoint
  • 1 carried
  • 8 mapped
  • 4 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Lawcus to SharePoint

Each row is a kind of record Lawcus holds, whether SharePoint has a place for it, and what is planned. On this route one kind of record carries across, eight kinds need mapping and four kinds have no place in SharePoint and are archived.

Records in Lawcus and their place in SharePoint
RecordIn LawcusIn SharePointWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldShown as cards on boards with a stage, or as a list; numbers come from a saved scheme.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 referrersHeldContacts with custom fields and field groups.Has a place in partOnly as rows in a list built for the purpose.Carried with mapping
DocumentsFiles stored in or linked from the systemHeldFolders in Lawcus, with two-way sync to Google Drive and links to Dropbox, Box or OneDrive.Has a placeFiles in libraries, with columns and versions.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmails and attachments logged to a matter through the Gmail or Outlook add-ins.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 notesHeldNotes and interactions on a matter can be pinned or starred.Has a place in partAs documents, or as rows in a notes list if one is built.Carried with mapping
CalendarAppointments, court dates and deadlinesHeldHas a place in partPossible as a list; usually left in Outlook.Carried with mapping
TasksTo-dos and workflow steps assigned to peopleHeldNo-code workflows can create tasks when a matter changes.Has a place in partPossible as a list; no legal workflow built in.Carried with mapping
Time and expensesTime and expense entries, billed and unbilledHeldNo placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeldHourly, flat fee and contingency; invoice templates per currency; credit notes.No placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeldTrust balances and a minimum retainer threshold per matter.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfHeldCustom fields and field groups for contacts and matters.Has a placeColumns and content types on libraries and lists.Carried with mapping
TemplatesPrecedents, document templates and automationHeldDocument automation and reusable invoice templates.Has a place in partPrecedents as files; templates can be offered from a library.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldLeads on a Kanban board, with client-facing and internal forms.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 Lawcus.
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.
Kept as a readable archive
SharePoint has no place for it. It is exported in a format that opens without Lawcus 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 Lawcus 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 Lawcus.

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

Where the data is now

In Lawcus a matter’s position on a board says as much about it as any field. Stages, boards and the automations attached to them are how a firm on Lawcus knows where every file stands. A move off it has to turn that visual arrangement into something the destination can store, and it has to do so without losing the difference between a lead and a matter.

  1. Stages are the status

    Each board has its own stages, and a matter’s stage is what staff look at to see progress. A conveyancing board and a litigation board will not share stage names. Destinations tend to offer one status list, or a status per matter type. Every board’s stages are mapped separately, and the firm approves the mapping.

  2. Leads sit on boards too

    Prospects are tracked on a Kanban board of their own before they become clients. A lead and a matter can look alike in the interface. The extraction keeps them apart, and leads that were never converted are loaded as intake records or left as an exported list, depending on what the destination offers.

  3. Automations are not data

    No-code workflows send emails, create tasks and produce documents when a matter changes stage or a form comes in. None of that is a record that can be moved. The workflows are documented as rules during the analysis, and the firm chooses which ones to rebuild in the new system’s own automation.

  4. QuickBooks was fed one way

    Lawcus pushes invoices, payments and expenses to QuickBooks Online and takes nothing back. An edit made directly in QuickBooks is therefore unknown to Lawcus. The two can drift apart. Receivables are compared on both sides before cutover, and the firm decides which figure is right where they differ.

  5. More than one currency

    Invoice templates can be set up for clients billed in different currencies. A destination that works in one currency cannot hold those balances as they are. Foreign-currency clients are identified early, and the firm decides whether their history is converted at a stated rate or kept in the old system.

More about moving off Lawcus

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 Lawcus 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 Lawcus: 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 Lawcus, a final pass over a weekend picks up what changed since the trial. Lawcus 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 Lawcus 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 fromLawcus
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 Lawcus 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

Lawcus to SharePoint: what firms ask

Our documents sync between Lawcus and Google Drive. Which copy is moved?

The Google Drive copy is usually the easier source, because it is in the firm’s own account and the sync keeps the two alike. Lawcus supplies the link between each folder and its matter. A sample of matters is compared on both sides first to confirm nothing is missing from the Drive.

Can our matter numbers be kept?

Yes. Lawcus generates matter numbers from a numbering scheme the firm saved, so the numbers are consistent and can be carried as they are. If the destination produces numbers in another format, the Lawcus number is kept in a reference field and new matters follow the new format.

What happens to forms our clients filled in?

Answers that were saved to fields on a contact or matter are data and move with that record. Forms marked internal are treated the same way. The form designs are specific to Lawcus. If the new system has intake forms, they are rebuilt there from the same questions.

Do trust balances in Lawcus have a place in SharePoint?

No. SharePoint does not keep trust ledgers. Trust records from Lawcus are exported as ledgers and statements that open without it, and the firm settles where its trust accounting runs from the cutover date before the move is planned.

What happens to records SharePoint has no place for?

On this route that is time entries, billing records, trust ledgers and intake records. They are exported from Lawcus 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 Lawcus data is loaded into SharePoint?

Matters, contacts, emails, notes, calendar entries, tasks, custom fields and templates are carried with mapping, so each mapping is agreed with you first. 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

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

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