Data migration route
SharePoint to Clio Manage migration
SharePoint is cloud file storage, and Clio Manage is a cloud practice management system. The move is about deciding which folder is which matter, then filing every document against it.
SharePointCloud- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Emails: Carried across
- Notes: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Custom fields: Carried with mapping
- Templates: Carried with mapping
Clio ManageCloud- 7 carried
- 2 mapped
What moves
What moves from SharePoint to Clio Manage
Each row is a kind of record SharePoint holds, whether Clio Manage has a place for it, and what is planned. On this route seven kinds of record carry across and two kinds need mapping.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | Held in partNo matter record as such; firms model matters as sites, libraries, folders or list rows. | Has a placeImported from a matters template, after contacts. | Carried across |
| ContactsClients, other parties and referrers | Held in partOnly if the firm keeps a contacts list in a SharePoint list. | Has a placePeople and companies, with related contacts linked to matters by a separate template. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldFiles in document libraries, with versions, columns and check-out. | Has a placeFiled under the matter; Clio scopes document migration separately from data. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partOnly messages saved into a library as .msg or .eml files. | Has a placeHeld as communications on the matter, with phone logs. | Carried across |
| NotesFile notes, matter notes and contact notes | Held in partOneNote notebooks and site pages, where the firm used them. | Has a placeMatter notes and contact notes each have a template. | Carried across |
| CalendarAppointments, court dates and deadlines | Held in partCalendar lists exist; most firms keep calendars in Outlook instead. | Has a placeCalendar events have a migration template. | Carried across |
| TasksTo-dos and workflow steps assigned to people | Held in partTask lists exist where a firm built them. | Has a placeTasks have a migration template. | Carried across |
| Custom fieldsFields and record types the firm added itself | HeldColumns and content types defined by the firm on libraries and lists. | Has a placeCreated first, then filled from the custom field templates. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | Held in partPrecedents as files; a library can offer document templates through content types. | Has a placeRebuilt as Clio document templates with its merge fields. | Carried with mapping |
What the plans mean
- Carried across
- Clio Manage has a place for this kind of record. It is loaded there and checked against SharePoint.
- Carried with mapping
- Clio Manage holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.
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
Folders become matters with documents.
Files in SharePoint are organised the way the firm’s people organised them: by client, by year, by lawyer, sometimes all three. Clio Manage wants every document on a matter. The analysis reads the folder tree and proposes a rule, for example that the second folder level is the matter, then lists every folder the rule does not fit. Those exceptions are the real work. A folder called Misc or Old Files has to be given a home by someone who knows the firm.
Folder names carry what a matter record should hold properly: client name, matter description, sometimes a file number. Where the names are consistent, matters and contacts can be created from them. Where they are not, the matter list is built first, in a spreadsheet the firm corrects, and the documents are loaded against it. File dates are preserved, so a document still shows when it was written and not when it was moved.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of SharePoint 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 SharePoint is kept running until the checks on Clio Manage are finished.
Where the data is now
Leaving SharePoint
No two firms’ SharePoint looks alike, because the firm or its IT provider designed it. One has a site per client, another a single library with a folder per matter, a third filed everything by column and has no folders at all. The move starts by reading that design, since the matter a document belongs to may be recorded in any of several places.
Find every site that holds files
Matter documents can be in the main document site, in the Files tab of a Teams channel, and in the separate sites that private channels create. An administrator’s site list is the starting point. Each library is then classed as matter files, firm administration or abandoned, and only the first two are scoped.
Columns hold what folders do not
Where a library uses columns for matter number, client or document type, that information is not in the file or its path. A copy taken through the sync app cannot be relied on to carry it. The column values are exported with each document so the destination can file by them, or they are written into the folder path.
Unique permissions need a report
Permissions can be broken at site, library, folder and file level, and after a few years they usually have been. Nobody can state from memory who may see what. A permissions report across the libraries shows which matters are restricted, and that list is carried into the security design of the new system.
Lists are data, not documents
A matter register, a deeds register or a conflict list kept as a SharePoint list is a table. It moves as records, by export to a spreadsheet and a mapping of its columns to fields, on a separate track from the files. Firms often forget these lists exist until the analysis turns them up.
Versions and checked-out files
Libraries keep major versions, and some keep minor drafts as well. The firm chooses how many come across. Files that someone checked out and never checked back in are a known trap: other people may see only an older copy, so these are found and checked in before the final collection.
Where it is going
Arriving in Clio Manage
Clio Manage is loaded through its migration templates, one spreadsheet per kind of record, imported in a fixed order with contacts first. Clio’s own migration guide is plain about the limit: balances come across, financial history does not. So a load into Clio is planned as records plus opening positions, with the old system kept for the history behind them.
Matters link by client name
The matters template ties each matter to its client by an exact match on first name, last name or company name. A client spelt two ways in the old system becomes two contacts, or a matter assigned to an unknown client. This is why contact clean-up is finished before the first trial load, not after it.
Decide the numbering scheme first
Clio numbers imported matters itself unless the account is set to manual numbering, in which case the old number is supplied in the template. That setting and the firm’s preferred scheme are decided before any matter is loaded. The Client Reference field is available for an old file number the firm still wants to see.
Balances, one line each
Under Clio’s standard migration, an outstanding balance arrives as one line per matter and a trust balance as one line per matter or contact. Past invoices, billed time, payments and trust transactions are listed as data that cannot be migrated. The trust total is reconciled against the old system’s closing report on the trial load.
Custom fields must exist
Matter and contact custom fields are created in Clio before their values are imported, each with a field type. Accounts set up for a particular practice area come with preconfigured fields and matter templates, which affects the mapping. We compare those with the old system’s fields and add only what is missing.
Rates and permissions by hand
Billable rates for users, clients and matters are not part of an import. Neither are user permissions or settings. They are entered in Clio during set-up from a schedule the firm confirms, and a sample of imported unbilled time is checked against that schedule before the trial load is signed off.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Clio Manage on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what SharePoint holds and how it is organised, then agree with you where each kind of record will sit in Clio Manage. Anything with no place there stays behind or is archived, and you see which before the move.
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.
Trial load
A trial is loaded into Clio Manage and checked against SharePoint: 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.
Cutover
There is no financial cutover on this route. After a short freeze on changes in SharePoint, a final pass over a weekend picks up what changed since the trial. SharePoint 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 SharePoint 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
What happens after you send it
- A free first call
We go through your answers with you and ask about anything they leave open.
- An analysis of what SharePoint holds
What is in it, how its records link, and where each piece would sit in Clio Manage. Anything with no place there comes across as a note or stays behind, and you see which before the move.
- 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 Clio Manage
Loaded data is not yet a working system. This is what NewLaw sets up in Clio Manage, beyond the migration, so that people can work in it from the first day.
Much of a Clio Manage set-up is firm-wide settings. The numbering scheme, practice areas, matter stages, billing preferences and trust accounts apply to everyone, so they are agreed once and early. Trust and accounting features are not the same in every country Clio sells in, so the firm’s own region is checked first. Document templates and custom fields follow. Email and document integrations are then installed for each user and tested on a real matter.
Set-up decisions in Clio Manage
- Matter numbering scheme, practice areas and matter stages
- Custom fields for matters and contacts, by practice area
- Document templates with merge fields, uploaded from Word or PDF
- Billing settings, user and client rates, and trust accounts
- Roles and permissions for each user
- Outlook add-in, Clio Drive and the accounting connection
Questions
SharePoint to Clio Manage: what firms ask
We only use Teams. Do we have anything in SharePoint to move?
Yes. The Files tab in every Teams channel is a folder in a SharePoint site, and each private or shared channel has a site of its own. If matter documents were dropped into channels, they are in SharePoint. Chat messages are stored differently and are a separate question from the files.
Can the new system keep our SharePoint columns?
It depends whether the destination has matching fields. Matter number and client usually map to the matter itself. Document type and author often have a home on the document profile. A column with nowhere to go is either written into the document’s name or description, or left behind, and the firm sees which before the move.
Should we move to SharePoint or to a legal document management system?
That is a decision about how the firm works, and it is the firm’s to make. What can be said plainly is that SharePoint arrives empty of legal structure: matters, filing rules and email filing are all designed and built. The analysis sets out what that build involves for the firm’s matter volume.
Do documents from SharePoint keep their folders and dates in Clio Manage?
Clio Manage stores documents. Filed under the matter; Clio scopes document migration separately from data. Each file is placed under the client and matter it came from, and created and modified dates are carried, so a document still shows when it was written. The trial load is checked by count and by opening a sample.
Does everything in SharePoint have a place in Clio Manage?
On paper, yes: each kind of record SharePoint holds has a place in Clio Manage. Whether every field fits is a separate question, and the analysis answers it field by field. Anything with no place comes across as a note or stays behind, and you see which before the move.
What has to be decided before SharePoint data is loaded into Clio Manage?
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.
Other routes
Other routes from SharePoint and into Clio Manage
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.
Choose your systems
Technology stack selection
Decide which practice management system your firm runs, with the evidence and the cost beside it.
About four weeks for a firm of about 15 people. Fixed price, set after a free first call.
Move your data
Data migration
Your data is cleaned up before anything moves, then a trial load is checked against the old system.
Fixed price, agreed after the analysis.
Set up your new system
Implementation
Your new system set up around the way your firm works: configuration, document automation and training.
A small firm of 1 to 10 users typically takes 4 to 8 weeks. A mid-sized firm of 10 to 50 users takes 8 to 16 weeks.
Put AI to work
AI advisory and enablement
A small group of your people learn to use an approved AI tool on real work, under written rules.
Two to four weeks for a small first group. Fixed price, set after a free first call.
SharePoint and Clio Manage are the names and marks of their owners, used here only to identify the two systems.
Moving from SharePoint to Clio Manage?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.