Data migration route
Dropbox to NetDocuments migration
Dropbox is cloud file storage, and NetDocuments is a cloud document management system. The move adds structure the folders never had: a client, a matter and a document type for every file.
DropboxCloud- Documents: Carried across
- Emails: Carried across
- Templates: Carried with mapping
NetDocumentsCloud- Notes: Kept as a readable archive
- 2 carried
- 1 mapped
- 1 archived
What moves
What moves from Dropbox to NetDocuments
Each row is a kind of record Dropbox holds, whether NetDocuments has a place for it, and what is planned. On this route two kinds of record carry across, one kind needs mapping and one kind has no place in NetDocuments and is archived.
| 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 placeImported with profile values, folder, dates and access set per document. | 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 placeLoaded as email items profiled to the matter. | Carried across |
| NotesFile notes, matter notes and contact notes | Held in partDropbox Paper documents, where staff used them for notes. | No placeFile notes are loaded as documents in the matter workspace. | Kept as a readable archive |
| TemplatesPrecedents, document templates and automation | Held in partPrecedents are kept as ordinary files in a folder. | Has a place in partLoaded as documents in a precedents cabinet or workspace. Automation is set up afresh. | Carried with mapping |
What the plans mean
- Carried across
- NetDocuments has a place for this kind of record. It is loaded there and checked against Dropbox.
- Carried with mapping
- NetDocuments 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
- NetDocuments has no place for it. It is exported in a format that opens without Dropbox 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
Folders go in. Profiled workspaces come out.
A document management system asks questions of every file that a folder never did: which client, which matter, what type of document, who wrote it. Coming from Dropbox, the answers have to be worked out from where a file sits and what it is called. The analysis reads the folder tree, proposes how its levels map to client, matter and folder in NetDocuments, and lists what does not fit. Those exceptions go to the firm as a spreadsheet to correct.
Not everything should move. Shared drives collect installers, duplicates, personal files and working copies ten versions deep. The firm decides what is in scope by folder, by age or by file type, and the rest is left where it is or archived. File dates are preserved. Paths too long for NetDocuments, characters it does not allow and files that will not open are reported before the load. The copy can be repeated, so the final pass picks up only what changed.
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 NetDocuments 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 NetDocuments
Loading into NetDocuments means every document arrives with a profile. The cabinet, its profile attributes and the client and matter lookup tables are built first. Documents are then imported with an instruction file that says, line by line, which file gets which client, matter, author, document type, folder and access. Preparing that file from the old system’s data is most of the work.
Lookup tables before documents
Client and matter are validated attributes, with matter the child of client. A value missing from the lookup table cannot be used to profile a document. The tables are loaded from the practice management system first, closed matters included, and each matter is flagged open or closed so old ones stay out of pick lists.
Workspaces come from the profile
A workspace shows whatever is profiled to its matter. So the question is not where to put a folder tree but how to profile each file. Old folder names are often turned into a document type attribute, or kept as a workspace folder, and the mapping decides which for each one.
Import files are unforgiving
The import file is comma-separated text, and NetDocuments itself warns that opening one in Excel can strip leading zeros from numbers and alter dates. A matter number of 00123 that becomes 123 will not match its lookup value. The files are kept as plain text from start to finish and are not opened in a spreadsheet.
Folder limits and depth
A folder can hold any number of documents but no more than 500 subfolders. Deep trees copied from a file server also work against the way the system is searched. Where a matter arrives with hundreds of nested folders, the plan flattens them and keeps the lost path in the document name or an attribute.
Security at the right level
Access can be set on the cabinet, by profile value, on a workspace or on a single document. Restricted matters are best carried as workspace or profile-based security, so that new documents pick it up. Document-by-document access lists copied from an old system are loaded only where the restriction was real.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in NetDocuments 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 NetDocuments. 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 NetDocuments 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 NetDocuments. 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 NetDocuments
Loaded data is not yet a working system. This is what NewLaw sets up in NetDocuments, beyond the migration, so that people can work in it from the first day.
Beyond the load, NetDocuments has to be designed: how many cabinets the firm needs, which profile attributes every document must carry, and what a new matter’s workspace looks like on its first day. After that it is connected to the practice management system so client and matter lists stay current, and ndOffice and the email filing tools are set up for each person, with training on profiling.
Set-up decisions in NetDocuments
- Cabinet design: one for the firm, or several by purpose
- Profile attributes, lookup tables and the client and matter hierarchy
- Workspace layout with default folders, filters and saved searches
- User groups, cabinet membership and security for restricted matters
- A feed of new clients and matters from practice management
- ndOffice, ndMail and Outlook filing on every desk, with training
Questions
Dropbox to NetDocuments: 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 NetDocuments?
NetDocuments stores documents. Imported with profile values, folder, dates and access set per document. 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.
What happens to records NetDocuments has no place for?
On this route that is notes. They are exported from Dropbox 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 Dropbox data is loaded into NetDocuments?
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 NetDocuments
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 NetDocuments are the names and marks of their owners, used here only to identify the two systems.
Moving from Dropbox to NetDocuments?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.