Data migration route
OpenText eDOCS to Google Drive migration
OpenText eDOCS is a server-based document management system, and Google Drive is cloud file storage. Storage only has folders, so the move decides what of each document’s profile is kept in names and what in an index.
OpenText eDOCSServer- Documents: Carried across
- Emails: Carried with mapping
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Templates: Confirmed in the analysis
Google DriveCloud- Matters: Kept as a readable archive
- Custom fields: Kept as a readable archive
- 1 carried
- 1 mapped
- 3 to confirm
- 2 archived
What moves
What moves from OpenText eDOCS to Google Drive
Each row is a kind of record OpenText eDOCS holds, whether Google Drive has a place for it, and what is planned. On this route one kind of record carries across, one kind needs mapping, two kinds have no place in Google Drive and are archived and three kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | Held in partIn eDOCS, a matter is a value on the document profile, not a record of its own. | No placeA matter is a folder inside a shared drive. | Kept as a readable archive |
| DocumentsFiles stored in or linked from the system | HeldProfiled documents and their versions in an eDOCS library. | Has a placeAny file type, stored as uploaded or converted to Google formats. | Carried across |
| EmailsEmails saved to matters or to the store | HeldWhere the eDOCS email filing module was installed. | 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 | To be confirmed | Has a place in partAs a Doc or Word file in the matter’s folder. | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | No place | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldThe profile form is configured by each firm. | No place | Kept as a readable archive |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a place in partPrecedents load as files; the load does not rebuild Word automation in Docs. | Confirmed in the analysis |
What the plans mean
- Carried across
- Google Drive has a place for this kind of record. It is loaded there and checked against OpenText eDOCS.
- 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.
- Confirmed in the analysis
- We could not confirm this from the two products’ own material, so it is checked against your data before the plan is fixed.
- Kept as a readable archive
- Google Drive has no place for it. It is exported in a format that opens without OpenText eDOCS 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
Profiles flatten into folders and an index.
A document management system knows things about a file that a folder cannot hold: its profile, its versions, who may open it. Moving from OpenText eDOCS to Google Drive flattens that. Client and matter become folder levels. Document type may become a subfolder. Versions become separate files with a suffix, or only the latest is kept. Each of these is a choice the firm makes before the export, and the result is tested on a sample of real matters.
What the folders cannot carry goes into an index: a spreadsheet listing every exported file with its document number, author, dates, type and original location. With it, a document cited by number in an old email can still be found. Access restrictions do not transfer by themselves. Restricted workspaces are exported to separate folders, and permissions are set on those in Google Drive before anyone else is given access.
OpenText eDOCS runs on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. Google Drive is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.
Where the data is now
Leaving OpenText eDOCS
The first step for a firm that describes its system as OpenText is to confirm which product and version is installed. If it is eDOCS, the move is from an on-premises library whose profiles are in SQL and whose files are on document servers. If it is one of OpenText’s other content platforms, the structure is different and the analysis starts from that product’s own model.
Confirm the product first
OpenText’s catalogue is wide. eDOCS, Documentum and its other content management products are separate systems, and a plan written for one does not fit another. The version shown in the client’s About box, or the names of the server components, settles it in a few minutes and saves planning for the wrong system.
Paperwork may still say OpenText
Licences, support agreements and server names at a firm will carry the OpenText name for years after the sale. For migration purposes what matters is who can grant access to the library database and document servers today. That is normally the firm’s own IT team or its hosting provider, since the system runs on their equipment.
Old integrations point at the library
Practice management systems, scanning tools and Word macros were often wired to open or save documents in the library by document number. When the library is retired those links break. The analysis lists every integration found, so each one can be redirected to the new store or removed.
Web client and offline copies
Lawyers may have worked through the browser client, or kept documents offline on a laptop with the Attaché tool. Anything checked out and never checked back in exists only on that machine. A report of checked-out documents is run before the freeze, and people are asked to check their documents in.
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 OpenText eDOCS holds 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 OpenText eDOCS: 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 OpenText eDOCS, a final pass over a weekend picks up what changed since the trial. OpenText eDOCS 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 OpenText eDOCS 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 OpenText eDOCS 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
OpenText eDOCS to Google Drive: what firms ask
Is OpenText the same thing as eDOCS?
For most law firms, yes. eDOCS was OpenText’s document management product for legal, and people named the system after the vendor. It was sold to NetDocuments in January 2026 and is now simply eDOCS. OpenText also makes unrelated content platforms, so the installed product is confirmed before any planning is done.
Does the change of owner affect how we get our data out?
No. An eDOCS library runs on servers the firm or its host controls, and the documents and their database are there whoever owns the product. Extraction needs read access to the SQL database and the document servers, which the firm’s own IT team arranges.
Do documents from OpenText eDOCS 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 matters and custom fields. They are exported from OpenText eDOCS 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 OpenText eDOCS data is loaded into Google Drive?
Emails are carried with mapping, so each mapping is agreed with you first. Notes, tasks and templates are confirmed in the analysis. The firm also decides which closed matters and how many versions of a document are in scope.
Other routes
Other routes from OpenText eDOCS and into Google Drive
Other destinations from OpenText eDOCS
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.
OpenText eDOCS and Google Drive are the names and marks of their owners, used here only to identify the two systems.
Moving from OpenText eDOCS 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.