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

Data migration route

OpenText eDOCS to Litify migration

OpenText eDOCS is a server-based document management system, and Litify is a cloud case management system. The move is matching each file in OpenText eDOCS to its case in Litify.

FromOpenText eDOCSServer
  1. Matters: Carried across
  2. Documents: Carried across
  3. Emails: 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
ToLitifyCloud
  • 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 Litify

Each row is a kind of record OpenText eDOCS holds, whether Litify 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 Litify
RecordIn OpenText eDOCSIn LitifyWhat 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 placeMatters, by case type.Carried across
DocumentsFiles stored in or linked from the systemHeldProfiled documents and their versions in an eDOCS library.Has a placeLoaded to the document component and attached to matters.Carried across
EmailsEmails saved to matters or to the storeHeldWhere the eDOCS email filing module was installed.Has a place in partShown on the activity timeline. How old email is loaded is confirmed in the analysis.Carried with mapping
NotesFile notes, matter notes and contact notesTo be confirmedTo be confirmedConfirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldThe profile form is configured by each firm.Has a placeCustom fields are created before loading.Carried with mapping
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partTemplates are rebuilt in Litify’s document generation.Confirmed in the analysis

What the plans mean

Carried across
Litify has a place for this kind of record. It is loaded there and checked against OpenText eDOCS.
Carried with mapping
Litify 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

Every document goes to the case it belongs to.

A case management system expects each document to sit on a case, usually in a category such as correspondence, medical records or court documents. OpenText eDOCS organises files its own way, by profile or by folder. So the move needs two rules: which case a file belongs to, and which category it goes in. The first comes from client and matter references or folder names. The second comes from a document type or a subfolder, and where neither exists the files arrive uncategorised and are marked as such.

Cases must exist in Litify before documents can be attached to them. If the system is already live, files are matched to its case list and the unmatched ones are reported. If it is new, the case list is created first. Dates, authors and file names are kept. Email comes across as message files. Where several versions of a document exist, the firm chooses between loading the latest and loading them all.

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. Litify 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 a firm into Litify is done inside a Salesforce environment that has been configured for that firm, normally by Litify or one of its implementation partners. The data work fits around that project. Old records are mapped to parties, roles, intakes and matters and loaded into the Salesforce objects behind them, and documents are loaded separately and attached.

  1. The design comes first

    Case types, stages and page layouts are decided during discovery, before any load. A load into a half-configured environment has to be repeated when a field changes. The data mapping is written against the agreed design and updated whenever the design moves, so the two stay in step.

  2. One party, many roles

    Contacts from the old system become parties, and each appearance on a matter becomes a role. Duplicate contacts turn into duplicate parties with their roles divided between them. Duplicates are merged before the load where they can be identified, since separating them afterwards means pointing every role at the right party again.

  3. Open enquiries load as intakes

    Leads and enquiries that have not signed belong in intakes, not matters. They are loaded with their source and status so that conversion reports start from a true position. Old declined enquiries are loaded only if the firm wants them for conflict checking, and are marked so they do not count as live.

  4. Documents load after records

    Files are loaded into the document component once the matters exist, because each one is attached to a matter record. Folder structure is set per case type beforehand. Large injury files with medical records and video take time to transfer, and that time is planned into the cutover weekend.

  5. Validation rules reject bad rows

    A configured environment enforces required fields and validation rules, and old data seldom satisfies all of them. Rows that fail are reported by the load. They are fixed in the source and run again, or the rule is relaxed for migrated records, and the firm decides which for each rule.

More about moving into Litify

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Litify on this route, which makes it repeatable: a load can be run again until it is right. The maker of Litify says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in OpenText eDOCS and checking each trial against OpenText eDOCS.

  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 Litify. 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 Litify 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 toLitify

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

Loaded data is not yet a working system. The maker of Litify runs or arranges the set-up of its product, so this is what has to be decided and put in place in Litify, whoever does the work, before people rely on it from the first day.

A Litify implementation is a configuration project on Salesforce, run by Litify or an implementation partner with the firm’s own project team. Discovery sessions with each department come first. The decisions that follow shape the system: what an intake asks, how a matter moves through its stages, who sees what, and which other systems are connected.

Set-up decisions in Litify

  • Define intake questionnaires and the rules for conversion
  • Set case types, matter stages and page layouts
  • Build matter plans that create tasks at each stage
  • Design document folders and generation templates per case type
  • Configure user roles and sharing for restricted matters
  • Decide on timekeeping, billing and accounting integrations

Questions

OpenText eDOCS to Litify: 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 Litify?

Litify stores documents. Loaded to the document component and attached to matters. 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 Litify?

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

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.

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 Litify are the names and marks of their owners, used here only to identify the two systems.

Moving from OpenText eDOCS to Litify?

Tell us what you are moving. You get a plan and a fixed price after the analysis.

We reply within one business day.