Data migration route
Zoho WorkDrive to SharePoint migration
Zoho WorkDrive and SharePoint are both cloud file storage. The folders move as they are, and the work is in permissions, paths and links.
Zoho WorkDriveCloud- Documents: Carried across
- Emails: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
SharePointCloud- 1 carried
- 3 mapped
What moves
What moves from Zoho WorkDrive to SharePoint
Each row is a kind of record Zoho WorkDrive holds, whether SharePoint has a place for it, and what is planned. On this route one kind of record carries across and three kinds need mapping.
| Record | What is planned | ||
|---|---|---|---|
| DocumentsFiles stored in or linked from the system | HeldFiles in Team Folders and My Folders, including Zoho Writer, Sheet and Show documents. | Has a placeFiles in libraries, with columns and versions. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partOnly messages saved into a folder as files. | Has a place in partAs .msg or .eml files, with columns for sender and date if set up. | Carried with mapping |
| Custom fieldsFields and record types the firm added itself | Held in partLabels and Data Templates attach classification fields to files. | Has a placeColumns and content types on libraries and lists. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | Held in partPrecedents are kept as files, often in Zoho Writer format. | Has a place in partPrecedents as files; templates can be offered from a library. | Carried with mapping |
What the plans mean
- Carried across
- SharePoint has a place for this kind of record. It is loaded there and checked against Zoho WorkDrive.
- Carried with mapping
- SharePoint 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
Same folders, new home.
Copying folders from Zoho WorkDrive to SharePoint 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 SharePoint, 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.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Zoho WorkDrive 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 Zoho WorkDrive is kept running until the checks on SharePoint are finished.
Where the data is now
Leaving Zoho WorkDrive
WorkDrive is rarely a firm’s only Zoho product, and the move off it is cleaner when that is faced at the start. The documents are here. Client and matter records that explain them may be in Zoho CRM or another Zoho app. Collecting the files without the records that give them a matter number leaves a tree of folders to be matched by name.
Team Folders and My Folders
Team Folders are the firm’s and can be listed by an administrator. My Folders are each person’s private space, and matter drafts end up there more often than anyone admits. Staff are asked to move firm documents into the right Team Folder before collection, or to identify the personal folders that should be taken.
Writer, Sheet and Show documents
Documents created in Zoho’s editors are in Zoho formats. A destination built around Microsoft Word needs them converted to .docx, .xlsx or PDF on the way out. Merge fields, comments and tracked changes are where conversions go wrong, so a sample of the firm’s real precedents is converted and read before the full run.
Labels and Data Templates
If the firm classified documents with labels or Data Templates, that classification is stored in WorkDrive and not in the file. It has to be exported alongside each document. Where the destination has document types or profile fields, the values are mapped to them. Otherwise they are written into the file name.
Five roles to translate
Access in a Team Folder is by role: Admin, Organizer, Editor, Commenter or Viewer. Few destinations have the same five. The firm’s actual need is usually simpler, a list of who may open which matters, and that list is drawn from the role assignments and confirmed with a partner.
Unlimited versions, limited use
Zoho describes version history in WorkDrive as unlimited, so a long-lived precedent may have hundreds of versions. Bringing them all is seldom useful. The firm sets a rule, such as the latest version only for closed matters and the last few for open ones, before volumes are estimated.
Where it is going
Arriving in SharePoint
SharePoint will take a firm’s documents in almost any arrangement, which is the difficulty. The structure has to be chosen before the load: what a client is, what a matter is, and where security is applied. Changing it afterwards means moving every file again. Most of the effort goes into that design and into the columns that describe each document.
Site, library or folder per matter
A matter can be a site, a library within a client site, or a folder in one large library. Each choice has consequences for permissions, for search and for how a new matter is opened. The firm makes that decision, and the people who open matters every day should be part of it.
Columns are built before content
If documents are to carry matter number, client, document type or author as columns, those columns and any content types exist before loading, so each file can be tagged as it arrives. Tagging hundreds of thousands of documents afterwards is a second project that seldom gets finished.
The 400 character path
SharePoint limits the full decoded path, site and library and folders and file name, to 400 characters. A deep tree copied from a server drive under a long site name can cross it. Path lengths are calculated against the planned structure, not the old one, before any file moves.
Large libraries and the view threshold
A library can hold millions of files, but a view that tries to show more than 5,000 items at once runs into the list view threshold. One flat library with a folder per matter needs indexed columns and filtered views from the start, or views begin to fail as the library fills.
Security by library, not by file
Microsoft supports up to 50,000 unique permissions in a library and recommends staying under 5,000. Restricting matters one folder at a time reaches that sooner than firms expect. Restricted work is better grouped into its own site or library, so the permission is set once.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in SharePoint on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what Zoho WorkDrive holds and how it is organised, then agree with you where each kind of record will sit in SharePoint. 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 SharePoint and checked against Zoho WorkDrive: 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 Zoho WorkDrive, a final pass over a weekend picks up what changed since the trial. Zoho WorkDrive 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 Zoho WorkDrive 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 Zoho WorkDrive holds
What is in it, how its records link, and where each piece would sit in SharePoint. 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
SharePoint 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.
Making SharePoint work as a firm’s document store is a design and build job in its own right. The sites, libraries, columns and permission groups are created, a way of opening a new matter is put in place so the structure repeats itself, and the Outlook and Teams habits around it are agreed. Search is tested with real questions from fee earners.
What is agreed and set up
- Site and library structure for clients and matters
- Columns and content types for matter number and document type
- Permission groups, with restricted matters in their own libraries
- A repeatable way to create each new matter’s workspace
- Version history limits and retention labels for closed matters
- Views, indexed columns and search tested on loaded data
Questions
Zoho WorkDrive to SharePoint: what firms ask
We also use Zoho CRM for clients. Is that part of the same move?
It should be looked at together even if it is moved separately. The CRM is where client names, contact details and often matter references are held, and WorkDrive folders are usually named after them. Reading both lets each folder be tied to the right client and matter in the new system without guesswork.
Will our Zoho Writer precedents work in Word?
The text and most formatting convert. Automation does not carry over by itself: merge fields that pulled data from Zoho have to be rebuilt against the new system’s fields. Precedents are therefore handled as a small project of their own, starting with the documents the firm uses every week.
Can we keep WorkDrive for closed matters?
Yes, for as long as the subscription runs. The practical points are that at least one current staff member keeps an Admin role on each Team Folder, and that the closed matters are set to view only so nothing is filed there by habit after go-live. Both are checked at handover.
Do documents from Zoho WorkDrive keep their folders and dates in SharePoint?
SharePoint stores documents. Files in libraries, with columns and versions. 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 Zoho WorkDrive have a place in SharePoint?
On paper, yes: each kind of record Zoho WorkDrive holds has a place in SharePoint. 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 Zoho WorkDrive data is loaded into SharePoint?
Emails, custom fields 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 Zoho WorkDrive and into SharePoint
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.
Zoho WorkDrive and SharePoint are the names and marks of their owners, used here only to identify the two systems.
Moving from Zoho WorkDrive to SharePoint?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.