Data migration route
OpenText eDOCS to SharePoint migration
OpenText eDOCS is a server-based document management system, and SharePoint 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
- Matters: Carried with mapping
- Emails: Carried with mapping
- Custom fields: Carried with mapping
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Templates: Confirmed in the analysis
SharePointCloud- 1 carried
- 3 mapped
- 3 to confirm
What moves
What moves from OpenText eDOCS to SharePoint
Each row is a kind of record OpenText eDOCS holds, whether SharePoint has a place for it, and what is planned. On this route one kind of record carries across, three kinds need mapping 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. | Has a place in partAs a site, library, folder or list row the firm designs; no built-in matter record. | Carried with mapping |
| DocumentsFiles stored in or linked from the system | HeldProfiled documents and their versions in an eDOCS library. | Has a placeFiles in libraries, with columns and versions. | Carried across |
| EmailsEmails saved to matters or to the store | HeldWhere the eDOCS email filing module was installed. | Has a place in partAs .msg or .eml files, with columns for sender and date if set up. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a place in partAs documents, or as rows in a notes list if one is built. | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | Has a place in partPossible as a list; no legal workflow built in. | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldThe profile form is configured by each firm. | Has a placeColumns and content types on libraries and lists. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a place in partPrecedents as files; templates can be offered from a library. | Confirmed in the analysis |
What the plans mean
- Carried across
- SharePoint has a place for this kind of record. It is loaded there and checked against OpenText eDOCS.
- 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.
- 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.
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 SharePoint 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 SharePoint 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. SharePoint 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 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 OpenText eDOCS 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 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 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
OpenText eDOCS to SharePoint: 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 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 OpenText eDOCS have a place in SharePoint?
Most of it does on paper. Notes, tasks and templates could not be confirmed from the two products’ own material, so those are checked in the analysis. Anything that turns out to have no place in SharePoint is kept as a readable archive, and you see which before the move.
What has to be decided before OpenText eDOCS data is loaded into SharePoint?
Matters, emails and custom fields 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 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.
OpenText eDOCS and SharePoint are the names and marks of their owners, used here only to identify the two systems.
Moving from OpenText eDOCS 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.