Data migration route
Dropbox to Clio Manage migration
Dropbox 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.
DropboxCloud- Documents: Carried across
- Emails: Carried across
- Notes: Carried across
- Templates: Carried with mapping
Clio ManageCloud- 3 carried
- 1 mapped
What moves
What moves from Dropbox to Clio Manage
Each row is a kind of record Dropbox holds, whether Clio Manage has a place for it, and what is planned. On this route three kinds of record carry across and one kind needs mapping.
| Record | What is planned | ||
|---|---|---|---|
| DocumentsFiles stored in or linked from the system | HeldFiles in folders, synced to desktops, with version history for a set number of days. | 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 where messages were saved into a folder 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 partDropbox Paper documents, where staff used them for notes. | Has a placeMatter notes and contact notes each have a template. | Carried across |
| TemplatesPrecedents, document templates and automation | Held in partPrecedents are kept as ordinary files in a folder. | 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 Dropbox.
- 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 Dropbox 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 Dropbox 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 Dropbox is kept running until the checks on Clio Manage are finished.
Where the data is now
Leaving Dropbox
Moving off Dropbox begins with a simple question that often has an awkward answer: whose account are the files in. A team space is one thing. Personal accounts sharing folders with each other are another, and the firm’s matter files may sit partly in an account that belongs to someone who has left.
Team space or personal accounts
On a team plan, team folders belong to the firm and an administrator can see them all. Outside one, each folder belongs to the person who created it and the others only have it shared to them. The analysis lists every account that owns matter folders, so that none is left behind when subscriptions are cancelled.
Collect from the account itself
Files marked online-only show in Explorer but are not on the disk. Copying the Dropbox folder from one computer can produce a tree that looks whole and is missing its contents. The files are taken from the Dropbox account itself, and one PC’s folder is used only to check the result.
Conflicted copies
When two people save the same file at once, Dropbox keeps both and adds the editor’s name and the words conflicted copy to one of them. Years of this leaves matter folders with near-duplicates. They are reported in the clean-up, and the firm decides whether to keep the later file, both, or review them by hand.
Paper docs need exporting
Dropbox Paper documents are not Word files. Each can be exported to .docx, Markdown or PDF, and on the current release of Paper that is done one document at a time. Where a firm kept file notes or checklists in Paper, they are counted early because the export is manual work.
Version history is a time window
Dropbox keeps earlier versions for a number of days set by the plan, not for a number of versions. Anything older has already gone. If earlier drafts matter for particular matters, they are pulled out while the window still covers them and before the plan is downgraded or cancelled.
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 Dropbox 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 Dropbox: 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 Dropbox, a final pass over a weekend picks up what changed since the trial. Dropbox 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 Dropbox 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 Dropbox 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
Dropbox to Clio Manage: what firms ask
Our files are in a partner’s personal Dropbox. Can they still be moved?
Yes, with the partner’s consent and access to that account. The shared folders are collected from the account that owns them, so nothing depends on what happens to be synced to one laptop. Personal folders mixed in with client folders are marked by the partner beforehand and left out.
Will the dates on our documents change?
The modified date of each file is recorded when it is collected and written to the destination where the destination allows it to be set. Some systems stamp every loaded document with the load date as its created date. The trial load shows which dates the new system displays, checked against a sample of old matters.
What about links we have sent to clients?
Shared links point at files in Dropbox, so they cannot be relied on once those files are removed or the account is closed. A list of active links and shared folders is produced before cutover. The firm then tells the clients concerned where their documents will be available afterwards.
Do documents from Dropbox 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 Dropbox have a place in Clio Manage?
On paper, yes: each kind of record Dropbox 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 Dropbox data is loaded into Clio Manage?
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 Dropbox 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.
Dropbox and Clio Manage are the names and marks of their owners, used here only to identify the two systems.
Moving from Dropbox 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.