Data migration route
Server drives to Google Drive migration
Server drives are plain files on equipment the firm controls, and Google Drive is cloud file storage. The folders move as they are, and the work is in permissions, paths and links.
Server drivesFiles- Documents: Carried across
- Emails: Carried with mapping
- Notes: Carried with mapping
- Templates: Carried with mapping
Google DriveCloud- Billing: Kept as a readable archive
- 1 carried
- 3 mapped
- 1 archived
What moves
What moves from Server drives to Google Drive
Each row is a kind of record Server drives hold, whether Google Drive has a place for it, and what is planned. On this route one kind of record carries across, three kinds need mapping and one kind has no place in Google Drive and is archived.
| Record | What is planned | ||
|---|---|---|---|
| DocumentsFiles stored in or linked from the system | HeldFiles in folders; path, name and dates are the only description. | Has a placeAny file type, stored as uploaded or converted to Google formats. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partMessages dragged from Outlook into matter folders as .msg files. | Has a place in partAs .eml or .msg files in the matter folder; not as Gmail messages. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | Held in partFile notes kept as Word documents or text files in the matter folder. | Has a place in partAs a Doc or Word file in the matter’s folder. | Carried with mapping |
| BillingInvoices, payments and debtor balances | Held in partCopies of invoices saved as PDFs; no ledger. | No place | Kept as a readable archive |
| TemplatesPrecedents, document templates and automation | Held in partA precedents folder of Word templates, with or without macros. | Has a place in partPrecedents load as files; the load does not rebuild Word automation in Docs. | Carried with mapping |
What the plans mean
- Carried across
- Google Drive has a place for this kind of record. It is loaded there and checked against Server drives.
- Carried with mapping
- Google Drive 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
- Google Drive has no place for it. It is exported in a format that opens without Server drives 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
Same folders, new home.
Copying folders from Server drives to Google Drive sounds like a drag and drop, and for a few gigabytes it is. For a firm’s whole document store the trouble is in the detail. The two stores have different limits on path length and different rules about characters in file names. Files open on someone’s desk during the copy are skipped. Modified dates are reset unless the copy is made with a tool that preserves them. Each of these is checked on a trial copy first.
Permissions and links do not travel. Who can see which folder is set up again in Google Drive, and it is a good moment to replace access granted to individuals over the years with groups. Shared links sent to clients stop working when the old store is switched off, so the live ones are listed and reissued. Documents that point at other documents by path, common in spreadsheets, are found and reported. The final pass copies only what changed since the trial.
With Server drives the files are already on equipment the firm controls, so there is no export step: they are read where they are. Upload speed sets the pace for a large store. The originals stay in place, unchanged, until the firm has checked the copy in Google Drive.
Where the data is now
Leaving Server drives
Moving off a server drive is a job of interpretation. The files copy easily. Working out which matter each folder belongs to does not, because the tree was built by many hands over many years and the naming changed with every new secretary. The analysis reads the tree, proposes rules for matching folders to matters, and shows the firm what the rules fail to place.
The folder tree is the index
Each matter folder is matched to a matter in the new system by the client name and matter number in its path. Some match exactly. Others say only Smith or Old files 2011. The unmatched folders are listed with their size and last-modified date, and the firm assigns them, archives them or leaves them.
Paths past 260 characters
Windows has long limited a full path to 260 characters, and deep matter trees routinely pass it. Such files exist but Explorer and Word may refuse to open or copy them. They are counted in the analysis and shortened to suit the destination’s own limit.
Permissions do not travel with files
Who may open the Partners folder or a restricted matter is set in Windows permissions on the server. A copy of the files should not be assumed to carry any of that. The permissions on each top-level and matter folder are reported before the move and rebuilt as groups or matter security in the new system.
Folders another system owns
The same drive often holds the document store of a practice management or accounting system, in folders with coded names. Those files are indexed in that system’s database and mean little without it. They are moved through the system that owns them, and kept out of the loose-file scan.
What accumulates over twenty years
Server drives collect shortcuts, temporary Word files, copies named Final v3 and whole duplicated matter folders. Exact duplicates are identified and reported. The firm sets the rule for near-duplicates, since only a person can say whether Final or Final v3 is the one that went to court.
Where it is going
Arriving in Google Drive
Putting a firm’s matter files into Google Drive means choosing shared drives over personal ones and then deciding how many shared drives there should be. That second decision is driven by Google’s limits and by who is allowed to see what, since access is granted mainly at the level of the whole shared drive.
Shared drives, not My Drive
Files loaded into a shared drive belong to the firm and remain when the person who loaded them leaves. Anything loaded into someone’s My Drive belongs to that person. Matter files therefore go to shared drives, and My Drive is left for personal working papers.
One drive cannot hold everything
Google caps a shared drive at 500,000 items, counting folders, shortcuts and anything in the trash, and at 100 levels of nested folders. A firm with twenty years of matters can pass the item cap in a single drive. The split is planned up front, commonly by practice group, or by open and closed matters.
Membership is the main control
Every member of a shared drive can see all of it unless a Manager restricts a particular folder. Matters that only certain people may open are simpler to protect in a shared drive of their own. The firm supplies the list of restricted matters and partners’ private folders before the drives are created.
The daily upload limit
Each user can upload 750 GB to Drive in 24 hours, and then has to wait. For a large document set that limit sets the shortest time the load can take. The total size is measured in the analysis, so the firm knows before the freeze whether its documents fit inside a weekend.
Keep Office files as Office files
Word and Excel files can be stored in Drive as they are or converted to Google formats. Unless the firm asks otherwise they are loaded unconverted, so court documents and automated precedents arrive as they left. The firm decides afterwards which templates are worth rebuilding as Google Docs.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Google Drive on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what Server drives hold and how it is organised, then agree with you where each kind of record will sit in Google Drive. 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 Google Drive and checked against Server drives: 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 Server drives, a final pass over a weekend picks up what changed since the trial. Server drives are 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 Server drives 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 Server drives holds
What is in it, how its records link, and where each piece would sit in Google Drive. 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
Structure, permissions and handover
Google Drive 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.
A Drive set-up for a law firm is a small number of deliberate choices made in the Workspace Admin console and then left alone. Which shared drives exist, who manages each, whether staff may share outside the firm, and whether people work from the browser or from Drive for desktop. Staff also need to be shown where a new matter folder goes.
What is agreed and set up
- Shared drives by practice group, with a naming pattern
- Managers and member access levels for each shared drive
- External sharing rules set in the Admin console
- Drive for desktop on PCs that need Explorer access
- A standard subfolder set copied into every new matter
- Transfer of leavers’ My Drive files as a standing procedure
Questions
Server drives to Google Drive: what firms ask
Our folders are a mess. Do we have to tidy them before the move?
No, and it is better not to rename things by hand beforehand. The analysis works from the tree as it stands and proposes matching rules. Staff time is better spent on the short list of folders the rules cannot place, and on deciding what is old enough to archive without filing it to a matter.
Will the dates on our documents be kept?
The modified date on each file is read from the server and passed to the new system where it accepts a document date. Created dates on a server are less reliable, because copying files between drives in the past can have changed them. The trial load compares document dates on sample matters against the old folders.
Can staff keep using the S: drive after go-live?
For reading, yes: the drive is kept read only as the fall-back record. Not for filing. If people can still save to the old drive, some will, and within a month the firm has two places to look for every document. The drive is switched to read only at cutover.
Do documents from Server drives keep their folders and dates in Google Drive?
Google Drive stores documents. Any file type, stored as uploaded or converted to Google formats. 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 Google Drive has no place for?
On this route that is billing records. They are exported from Server drives 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 Server drives data is loaded into Google Drive?
Emails, notes 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 Server drives and into Google Drive
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.
Server drives and Google Drive are the names and marks of their owners, used here only to identify the two systems.
Moving from Server drives to Google Drive?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.