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

Data migration route

CosmoLex to SharePoint migration

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

FromCosmoLexCloud
  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. Firm accounts: Kept as a readable archive
  5. Intake: Kept as a readable archive
Readable archiveNo place in SharePoint
  • 1 carried
  • 8 mapped
  • 5 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from CosmoLex to SharePoint

Each row is a kind of record CosmoLex 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 five kinds have no place in SharePoint and are archived.

Records in CosmoLex and their place in SharePoint
RecordIn CosmoLexIn SharePointWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldEach has a Matter File #, an area of law and a matter owner.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 referrersHeldClients and other contacts; payees for accounts payable are a separate list.Has a place in partOnly as rows in a list built for the purpose.Carried with mapping
DocumentsFiles stored in or linked from the systemHeldBuilt-in storage, or OneDrive, Google Drive, Dropbox, Box or NetDocuments linked by matter.Has a placeFiles in libraries, with columns and versions.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmails sent to the firm’s forwarding address are tagged to matters by sender or recipient.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 notesHeldHas 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 peopleHeldTask workflows can be loaded into new or existing matters.Has a place in partPossible as a list; no legal workflow built in.Carried with mapping
Time and expensesTime and expense entries, billed and unbilledHeldEntries are called timecards.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeldNo placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeldTrust ledgers, journals and three-way reconciliation reports.No placeKept as a readable archive
Firm accountsGeneral ledger, office account and payablesHeldGeneral ledger with chart of accounts, bank feeds, accounts payable and cheque printing.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfHeldCustom fields can be used as merge fields in documents.Has a placeColumns and content types on libraries and lists.Carried with mapping
TemplatesPrecedents, document templates and automationHeldTemplates are Word documents using merge fields downloaded from CosmoLex.Has a place in partPrecedents as files; templates can be offered from a library.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partIntake forms are included; the vendor also describes lead tracking.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 CosmoLex.
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 CosmoLex 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 CosmoLex 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 CosmoLex.

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

Where the data is now

Leaving CosmoLex is rarely just a practice management change. For most firms it is also the day their accounting system changes, since the general ledger, bank reconciliations and trust records are all inside. The matters and documents are planned in the usual way. A harder conversation is the one with the bookkeeper and accountant about where the books go next and on what date.

  1. One ledger for everything

    Billing posts straight to the general ledger, on a cash or accrual basis the firm chose at set-up. The books are not in a separate package that carries on unchanged. A destination with lighter accounting means a new package for the books, and trial balances from both are compared at the cutover date.

  2. Reconciliations stay behind

    Bank feeds, matched transactions and completed reconciliation statements are a record of work done, not data another system can load. Before cutover the firm runs and saves the reconciliation and three-way reports for every period it may be asked about, and the read-only copy of CosmoLex is kept as the fall-back record.

  3. Inactive means settled

    A matter can only be made inactive once its trust funds are disbursed, and on accrual accounting once its receivable is cleared. So an active matter is not always a live one. Some are finished files still holding money. They are listed for the firm, because the destination will treat them as open.

  4. Emails tagged by address

    Forwarded emails are tagged to a matter when the sender or recipient matches an email address on the client record, and land in a Tagged folder. Where there is no match, or more than one, the email waits for someone to file it. That untagged pile is either cleared or knowingly left behind before extraction.

  5. Law society records in Canada

    The Canadian edition produces law society compliance reports such as the clients’ general journal and general receipts journal. A Canadian firm needs those reports complete to the cutover date and stored where they can be produced on request. The destination’s own reports only start from the opening balances.

More about moving off CosmoLex

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

CosmoLex to SharePoint: what firms ask

We are on CosmoLex Classic and are being moved to NextGen. Should we wait before changing systems?

It makes little difference to the data. The vendor describes NextGen as the same core functions with a new interface, and the firm’s records carry over. If a move away is already decided, the analysis can be done on whichever version the firm is using on the day.

Can our Word templates be reused?

The documents themselves can. CosmoLex templates are ordinary Word files that use mail merge fields taken from a CosmoLex field list. In a new system the wording and layout survive, and each merge field is replaced with the destination’s equivalent. Fields based on custom data take the longest to match.

How far back does the financial history go across?

That is a choice. Some destinations accept historic invoices, payments and trust transactions as records. Others start from opening balances, with older detail left in the read-only CosmoLex copy and in saved reports. Whichever is chosen, a complete trial load is run first so the trust and ledger figures can be agreed before the real cutover.

Do trust balances in CosmoLex have a place in SharePoint?

No. SharePoint does not keep trust ledgers. Trust records from CosmoLex 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, the firm’s accounts and intake records. They are exported from CosmoLex 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 CosmoLex 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

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

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