Data migration route
Google Drive to NetDocuments migration
Google Drive 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.
Google DriveCloud- Documents: Carried across
- Emails: Carried across
- Templates: Carried with mapping
NetDocumentsCloud- 2 carried
- 1 mapped
What moves
What moves from Google Drive to NetDocuments
Each row is a kind of record Google Drive holds, whether NetDocuments has a place for it, and what is planned. On this route two kinds of record carry across and one kind needs mapping.
| Record | What is planned | ||
|---|---|---|---|
| DocumentsFiles stored in or linked from the system | HeldUploaded files plus Google Docs, Sheets and Slides, which are not files until exported. | 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 messages saved to Drive as files; mail itself is in Gmail. | Has a placeLoaded as email items profiled to the matter. | Carried across |
| TemplatesPrecedents, document templates and automation | Held in partPrecedents kept as files or as Google Docs that staff copy. | 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 Google Drive.
- 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.
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 Google Drive, 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 Google Drive 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 Google Drive is kept running until the checks on NetDocuments are finished.
Where the data is now
Leaving Google Drive
Two things set a move off Google Drive apart from a move off any other drive. Much of the content is in Google’s own formats and has to be converted on the way out. And ownership is personal unless the firm used shared drives, so the files for one matter can be scattered across the accounts of everyone who ever worked on it.
Docs, Sheets and Slides convert
A Google Doc has no file behind it. On the way out it is saved as Word or PDF, a Sheet as Excel. The document’s revision history stays in Google, and links from one Doc to another still point back there. How layout, comments and suggestions come through is checked on a sample. The firm picks the output format per document type.
My Drive files belong to people
Every file in My Drive has one owner. A matter folder shared across the firm can contain files owned by six different accounts, some of them former staff. An administrator can transfer a user’s files to a new owner, and that is done for leavers before their accounts are touched.
Shortcuts are not the file
A shortcut in a matter folder points to a file stored somewhere else, often in another person’s drive. Copied naively it arrives as an empty pointer. Shortcuts are resolved to the real document during collection, and where the target can no longer be reached the gap is reported.
Names Windows cannot hold
Drive lets two files in one folder share a name, and Windows does not. Windows and SharePoint also refuse certain characters in names. Both are looked for in the analysis. Duplicated names are numbered and refused characters replaced by an agreed rule before loading, with the changes listed against the original names.
Old versions of uploads expire
For an uploaded file such as a PDF or Word document, Drive may delete an earlier version after 30 days or once there are 100 newer ones, unless someone marked it Keep forever. Earlier drafts the firm assumes are there may not be. What exists is counted in the analysis.
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 Google Drive 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 Google Drive: 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 Google Drive, a final pass over a weekend picks up what changed since the trial. Google Drive 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 Google Drive 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 Google Drive 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
Google Drive to NetDocuments: what firms ask
What happens to our Google Docs when we move to a system that uses Word?
Each Doc is converted to a Word file, or to PDF where it is a finished document that should not change. Documents with heavy tables, drawings or linked Sheets are the ones checked by eye on a sample. The originals stay in Google, read only, until the firm is satisfied.
Some matter files are owned by people who have left. Are they lost?
Not if the account still exists, even suspended. A Workspace administrator can transfer its files to a current user, and that is done first. Where an account was deleted some time ago its My Drive files are gone, and the analysis will show the affected matters by the gaps in their folders.
Do we move Gmail and Calendar as well?
They are separate from Drive and are scoped separately. A firm can keep Google Workspace for mail and calendar and move only its matter files into a practice or document system. If emails need to sit on matters, the question is which mailboxes and labels are filed, and that is answered in the analysis.
Do documents from Google Drive 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.
Does everything in Google Drive have a place in NetDocuments?
On paper, yes: each kind of record Google Drive holds has a place in NetDocuments. 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 Google Drive 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 Google Drive 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.
Google Drive and NetDocuments are the names and marks of their owners, used here only to identify the two systems.
Moving from Google Drive 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.