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

Data migration route

eDOCS to SmartAdvocate migration

eDOCS is a server-based document management system, and SmartAdvocate is a cloud case management system for personal injury work. The move is matching each file in eDOCS to its case in SmartAdvocate.

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

What moves

What moves from eDOCS to SmartAdvocate

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

Records in eDOCS and their place in SmartAdvocate
RecordIn eDOCSIn SmartAdvocateWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeld in partClient and matter are fields on the document profile, set up per library.Has a placeCases by case type, with master and member relationships.Carried across
DocumentsFiles stored in or linked from the systemHeldFiles on document servers, each with a profile in the library’s SQL database.Has a placeDocuments page, by category and subcategory.Carried across
EmailsEmails saved to matters or to the storeHeldFiled from Outlook through the email filing module.Has a placeEmails are attached to cases.Carried across
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeConfirmed 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 itselfHeldProfile forms and the fields on them are designed for each library.Has a place in partConfirmed in the analysis for each field with no standard home.Carried with mapping
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partTemplates are rebuilt with SmartAdvocate merge codes.Confirmed in the analysis

What the plans mean

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

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

An eDOCS library is usually long-lived. Many have come through several upgrades and more than one owner of the product. Moving off one means reading the SQL database and the document servers together, and it means dealing with what a long life leaves behind: retired users, superseded profile forms, and documents converted from the systems that came before it.

  1. Three parts, read together

    The library’s metadata is in a SQL database, the files are on one or more document servers, and the full-text index is separate. The database says which stored file belongs to which document and version. The database and the file stores are taken at the same point in time, and the trial load checks each profile against its file.

  2. Profile forms changed over time

    The profile form a document was saved with decides which fields it has. Firms redesign forms, add document types and retire others over the years. A document from 2006 may have fields that are no longer on the form. The analysis reads the fields present across the whole library, not only today’s form.

  3. The records management module

    Where the records module is in use, the library also holds information about retention and sometimes about paper files. Those are not documents, and a document system chosen for matter files may have no place for them. They are identified early so the firm can decide where its retention rules will be kept after the move.

  4. Names the product has had

    Staff may call the system Hummingbird, DM, OpenText or eDOCS depending on when they joined. It is the same product line. Old document references, macros and footers can use any of those names, which matters when searching the firm’s precedents for hard-coded links back to the library.

More about moving off eDOCS

Where it is going

SmartAdvocate keeps injury detail in structured fields and screens, so mapping counts for more than usual: the more precisely the old data is placed, the more of those screens are filled on the first day. Parties, incidents, insurers, providers and bills are loaded to their own screens, and the vendor’s implementation team runs conversions into it.

  1. Map to fields, not notes

    The case summary, dashboards and settlement screen read from structured fields. Injury details, insurance limits and provider bills dumped into a note leave those screens empty. The mapping takes each old field to its SmartAdvocate counterpart, and only what truly has no counterpart is loaded as a note.

  2. Case types and statuses

    Cases are loaded against case types and statuses that drive WorkPlans and reports. These are agreed with the firm before the trial load, and old statuses are translated to the new list. A status with no match is not guessed at. It is listed, and someone who knows the files decides.

  3. Document categories

    Documents are searched by category, subcategory, sender, recipient and date as well as by folder. The old system’s folders are translated into categories on the way in. Files that arrive uncategorised can still be found by description, but they fall outside the category views staff are trained to use.

  4. Working with the vendor’s conversion

    SmartAdvocate’s implementation team converts client data into the system and trains staff through its own classes. The firm’s side of that is supplying a clean source, checking the converted cases against the old system, and deciding what to do with the exceptions. Independent help is used on those tasks.

  5. Choosing Server or Cloud

    The firm decides before loading whether it will run the Server edition on its own Windows server or use the hosted Cloud edition. Either way the data load is the same. What differs is who looks after backups, updates and remote access afterwards, and that is settled with the firm’s IT provider.

More about moving into SmartAdvocate

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in SmartAdvocate on this route, which makes it repeatable: a load can be run again until it is right. The maker of SmartAdvocate 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 eDOCS and checking each trial against eDOCS.

  1. Analysis

    We read what eDOCS holds and how it is organised, then agree with you where each kind of record will sit in SmartAdvocate. 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 SmartAdvocate and checked against 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 eDOCS, a final pass over a weekend picks up what changed since the trial. 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 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 fromeDOCS
Moving toSmartAdvocate

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 eDOCS holds

    What is in it, how its records link, and where each piece would sit in SmartAdvocate. 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 SmartAdvocate

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

Setting up SmartAdvocate is a matter of deciding how much of its detail the firm will use from the start. Case types, statuses and WorkPlans come first because they drive everything else. Templates follow. The vendor trains staff through its own classes, and the decisions below are best made before the first of those.

Set-up decisions in SmartAdvocate

  • Choose the Server or Cloud edition with IT
  • Define case types, statuses and staff roles
  • Build WorkPlans and Automated Procedures for each case type
  • Convert letters and forms into templates with merge codes
  • Install the Outlook plugin and agree email filing habits
  • Set up intake screens, lead sources and dashboards

Questions

eDOCS to SmartAdvocate: what firms ask

NetDocuments now owns eDOCS. Do we have to move?

NetDocuments has stated that there is no planned end of life for eDOCS and that it will keep supporting the on-premises platform. So the timing is the firm’s own decision. A firm that does move chooses its destination for its own reasons, and the migration is planned the same way whichever system that is.

How do document numbers and versions come across?

Each eDOCS document has a number and one or more versions, all recorded in the library database, and versions can be extracted one by one. A new system issues its own identifiers. The old document number is kept as a reference field or in the name where the firm still quotes it.

Do documents from eDOCS keep their folders and dates in SmartAdvocate?

SmartAdvocate stores documents. Documents page, by category and subcategory. 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 eDOCS have a place in SmartAdvocate?

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 SmartAdvocate is kept as a readable archive, and you see which before the move.

What has to be decided before eDOCS data is loaded into SmartAdvocate?

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

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

Moving from eDOCS to SmartAdvocate?

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

We reply within one business day.