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

Data migration route

Clio Grow to OneDrive migration

Clio Grow is a cloud CRM and intake system, and OneDrive is cloud file storage. What moves is the files, plus a readable export of everything else the old system holds.

FromClio GrowCloud
  1. Documents: Carried across
  2. Templates: Carried with mapping
  3. Emails: Confirmed in the analysis
  4. Notes: Confirmed in the analysis
  5. Tasks: Confirmed in the analysis
  6. Billing: Confirmed in the analysis
ToOneDriveCloud
  1. Matters: Kept as a readable archive
  2. Contacts: Kept as a readable archive
  3. Calendar: Kept as a readable archive
  4. Custom fields: Kept as a readable archive
  5. Intake: Kept as a readable archive
Readable archiveNo place in OneDrive
  • 1 carried
  • 1 mapped
  • 4 to confirm
  • 5 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Clio Grow to OneDrive

Each row is a kind of record Clio Grow holds, whether OneDrive has a place for it, and what is planned. On this route one kind of record carries across, one kind needs mapping, five kinds have no place in OneDrive and are archived and four kinds are confirmed in the analysis.

Records in Clio Grow and their place in OneDrive
RecordIn Clio GrowIn OneDriveWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeld in partProspective matters, called opportunities on newer screens, each with a pipeline status.No placeA matter is a folder in one user’s drive.Kept as a readable archive
ContactsClients, other parties and referrersHeldPerson and company contacts; synced with Clio Manage where both are used.No placeKept as a readable archive
DocumentsFiles stored in or linked from the systemHeld in partDocuments prepared from templates and sent for signature during intake.Has a placeFiles and folders up to the service’s size and path limits.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partSaved message files (.msg or .eml) beside the matter’s documents.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a place in partAs documents, or as OneNote notebooks created through OneNote.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeld in partAppointments booked through Clio Scheduler or entered by hand, with reminders.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleTo be confirmedNo placeConfirmed in the analysis
BillingInvoices, payments and debtor balancesTo be confirmedNo placeConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldContact and matter custom fields, shared with Clio Manage.No placeKept as a readable archive
TemplatesPrecedents, document templates and automationHeldDocument templates, including PDF templates with signature fields.Has a place in partPrecedents load as ordinary Word files.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldIntake form templates and a pipeline grouped as Intake, Hired and Not hired.No placeKept as a readable archive

What the plans mean

Carried across
OneDrive has a place for this kind of record. It is loaded there and checked against Clio Grow.
Carried with mapping
OneDrive 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
OneDrive has no place for it. It is exported in a format that opens without Clio Grow 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

An export the firm can open without the system.

OneDrive holds files, and most of what Clio Grow holds is records. This route is therefore an export job. Each kind of record is written out in a format that opens without the system it came from: lists as spreadsheets, statements and invoices as PDFs, attachments as the files they were. The export is laid out in folders that make sense to someone who never used Clio Grow, by client or by year, with a short index file saying what is where.

Firms do this when a subscription is ending, when a system is being retired, or to meet a retention rule. The test of the result is whether a question can still be answered from it years later: what was this client invoiced, who signed this agreement and when. So the trial export is checked by asking those questions of it. Totals are agreed to the system’s own reports, and access to the folder in OneDrive is limited before the export is copied in.

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

Where the data is now

Clio Grow holds the part of the firm’s record that comes before a matter exists. Moving off it means deciding how much of that history is worth carrying: open leads certainly, lost leads perhaps, form answers and signed documents where they belong to people who became clients. Contacts and opportunities export as spreadsheets. Completed forms and documents are gathered separately.

  1. Hired matters live in two places

    Once a matter is converted, it exists in Clio Manage as well as in Grow, and the two copies stay in sync. If the firm’s Clio Manage data is also moving, loading both would create every client twice. We take converted matters from Clio Manage and use Grow only for what never left the pipeline.

  2. Your statuses, their three groups

    Pipeline columns are statuses the firm created, grouped under Intake, Hired and Not hired. A new intake tool will have its own stages, and each Grow status is mapped to one. The Not hired group is usually where the volume is. They can come across as contacts with a tag, without a pipeline record.

  3. Form answers and custom fields

    A question on an intake form can be mapped to a custom field on the contact or matter. During the analysis we go through each form template to see which questions were mapped, because that decides whether an answer travels as a field value with the record or has to be taken from the completed form.

  4. Fields shared with Clio Manage

    Custom fields are common to Grow and Clio Manage: creating, editing or deleting one in either product changes it in the other. A firm that is leaving Grow but staying on Clio Manage should not tidy up Grow’s fields on the way out, because the change follows through to its live matters.

More about moving off Clio Grow

Where it is going

Before anything is loaded into OneDrive, the firm has to say whose OneDrive it is. Every drive has one owner and disappears with that person’s account unless someone acts. That suits an individual’s working papers. For the firm’s shared matter files the same question usually leads to a SharePoint library with OneDrive as the way people sync it.

  1. Whose drive holds the files

    Loading the Clients folder into the principal’s OneDrive ties every matter to that one account. If the firm wants that, the owner’s manager and a secondary owner are set in Microsoft 365 so access is not lost on a departure. Otherwise the files go to a SharePoint library and each person syncs it.

  2. A 400 character path limit

    The full path, folders and file name together, cannot exceed 400 characters in OneDrive. Document systems that file by client, matter, category and long descriptive titles produce paths over that. Each one is flagged before loading, and the firm approves how it will be abbreviated.

  3. Characters and names that fail

    OneDrive refuses names containing " * : < > ? / \ or |, names with leading or trailing spaces, and files beginning with ~$. Emails saved with their subject as the file name are worth checking first, because subjects often contain colons. Names are cleaned before loading and logged.

  4. Do not sync the whole archive

    Microsoft recommends syncing no more than 300,000 items in total and warns that performance suffers beyond it. A firm’s full matter history is often larger. Open matters are set to sync and closed ones are left in the cloud, reachable from the browser when someone needs an old file.

More about moving into OneDrive

How NewLaw runs it

Four steps, in this order.

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

  1. Analysis

    We read what Clio Grow holds and how it is organised, then agree with you where each kind of record will sit in OneDrive. 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 OneDrive and checked against Clio Grow: 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 Clio Grow, a final pass over a weekend picks up what changed since the trial. Clio Grow 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 Clio Grow 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 fromClio Grow
Moving toOneDrive

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 Clio Grow holds

    What is in it, how its records link, and where each piece would sit in OneDrive. 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

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

OneDrive needs little building and a fair amount of policy. The settings that matter to a law firm are in the SharePoint and Microsoft 365 admin centres: who may share outside the firm, how long a leaver’s drive is kept, and what syncs to laptops. Staff are shown the difference between their own drive and the firm’s shared libraries.

What is agreed and set up

  • External sharing limits for OneDrive set by an administrator
  • Retention period and secondary owner for leavers’ drives
  • Known folder redirection decided for Desktop and Documents
  • Sync app deployed with Files On-Demand turned on
  • Version history limits set for all users’ drives
  • Guidance on what belongs in OneDrive and what in SharePoint

Questions

Clio Grow to OneDrive: what firms ask

We are keeping Clio Manage. What actually needs to move?

Less than firms expect. Clients and matters that were converted are already in Clio Manage. What has to move is the open pipeline, plus the intake forms, document templates and booking pages, which are rebuilt in the new intake tool. Lost leads are optional, and the firm decides how far back to go.

Should leads we never signed come across?

It depends on what the firm does with them. If old enquiries are used for conflict checks or marketing, they are worth loading as contacts with their source and outcome. Where nobody has looked at them in years, an exported spreadsheet kept on file is enough, and the new system starts cleaner.

What happens to signed engagement letters?

A signed document for a client who was hired belongs on that client’s matter. Where the conversion to Clio Manage did not carry it, we collect it from Grow and file it to the matter in the destination. Signed documents for people who never became clients are archived with the export, not loaded.

Does billing history from Clio Grow move into OneDrive?

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 Clio Grow before the plan is fixed. Billing records with no place in OneDrive are kept as reports and invoice copies.

What happens to records OneDrive has no place for?

On this route that is matters, contacts, calendar entries, custom fields and intake records. They are exported from Clio Grow 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 Clio Grow data is loaded into OneDrive?

Templates are carried with mapping, so each mapping is agreed with you first. Emails, notes, tasks and billing records 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

Clio Grow and OneDrive are the names and marks of their owners, used here only to identify the two systems.

Moving from Clio Grow to OneDrive?

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

We reply within one business day.