Skip to content
NEWLAW.COM
+61 1300 495 281
Let’s talk

Data migration route

OpenText eDOCS to NetDocuments migration

OpenText eDOCS is a server-based document management system, and NetDocuments is a cloud one. The test of this move is whether profiles, versions and access rules survive it.

FromOpenText eDOCSServer
  1. Documents: Carried across
  2. Emails: Carried across
  3. Matters: Carried with mapping
  4. Custom fields: Carried with mapping
  5. Notes: Confirmed in the analysis
  6. Tasks: Confirmed in the analysis
  7. Templates: Confirmed in the analysis
ToNetDocumentsCloud
  • 2 carried
  • 2 mapped
  • 3 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from OpenText eDOCS to NetDocuments

Each row is a kind of record OpenText eDOCS holds, whether NetDocuments has a place for it, and what is planned. On this route two kinds of record carry across, two kinds need mapping and three kinds are confirmed in the analysis.

Records in OpenText eDOCS and their place in NetDocuments
RecordIn OpenText eDOCSIn NetDocumentsWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeld in partIn eDOCS, a matter is a value on the document profile, not a record of its own.Has a place in partAs a client and matter value with its workspace. Other matter details stay in practice management.Carried with mapping
DocumentsFiles stored in or linked from the systemHeldProfiled documents and their versions in an eDOCS library.Has a placeImported with profile values, folder, dates and access set per document.Carried across
EmailsEmails saved to matters or to the storeHeldWhere the eDOCS email filing module was installed.Has a placeLoaded as email items profiled to the matter.Carried across
NotesFile notes, matter notes and contact notesTo be confirmedNo placeFile notes are loaded as documents in the matter workspace.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleTo be confirmedTo be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldThe profile form is configured by each firm.Has a placeAs custom profile attributes, created in the repository before the load.Carried with mapping
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partLoaded as documents in a precedents cabinet or workspace. Automation is set up afresh.Confirmed in the analysis

What the plans mean

Carried across
NetDocuments has a place for this kind of record. It is loaded there and checked against OpenText eDOCS.
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.
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, versions and security, kept intact.

OpenText eDOCS and NetDocuments are related: they share a maker, or one is built on the other. Where a maker offers its own path between two of its products, that path is looked at first, and the analysis establishes what it carries and what it leaves. The points below apply wherever the two differ.

Between two document management systems the files are the easy part. What a firm has built in OpenText eDOCS is everything around them: the profile on each document, its version history, who can open it, which workspace it sits in. NetDocuments has its own model for each. Document types and custom profile fields are mapped one to one where they can be. Versions are loaded in order, so the latest in the old system is the latest in the new one.

Security is checked on its own. A restricted client or an information barrier must arrive restricted, so access groups are created in NetDocuments before any document is loaded, and a sample of restricted workspaces is tested with a user who should not see them. Document numbers are worth keeping, since they appear in footers and old emails. Where the new system assigns its own, the old number is stored as a searchable field.

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. NetDocuments 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

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

More about moving off OpenText eDOCS

Where it is going

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

More about moving into NetDocuments

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.

  1. Analysis

    We read what OpenText eDOCS 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.

  2. 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.

  3. Trial load

    A trial is loaded into NetDocuments 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.

  4. 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

Step 1 of 5: Start with the route

Moving fromOpenText eDOCS
Moving toNetDocuments

The route comes from this page. Four short steps follow. Nothing you send commits your firm to anything.

What happens after you send it

  1. A free first call

    We go through your answers with you and ask about anything they leave open.

  2. An analysis of what OpenText eDOCS 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.

  3. 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

OpenText eDOCS to NetDocuments: 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 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 OpenText eDOCS have a place in NetDocuments?

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 NetDocuments 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 NetDocuments?

Matters 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.

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.

How we do itDiscovery to rollout, step by step

OpenText eDOCS and NetDocuments are the names and marks of their owners, used here only to identify the two systems.

Moving from OpenText eDOCS 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.