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

Data migration route

eDOCS to Lawmatics migration

eDOCS is a server-based document management system, and Lawmatics is a cloud CRM and intake system. Lawmatics is built around people and enquiries, so the contact list leads this move, and the table shows what else has a place.

FromeDOCSServer
  1. Matters: Carried across
  2. Documents: Carried with mapping
  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
ToLawmaticsCloud
  • 1 carried
  • 3 mapped
  • 3 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from eDOCS to Lawmatics

Each row is a kind of record eDOCS holds, whether Lawmatics 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.

Records in eDOCS and their place in Lawmatics
RecordIn eDOCSIn LawmaticsWhat 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 placeLoaded from CSV with a status of PNC, Hired or Lost and a pipeline stage.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 place in partFiles and folders on each matter, added by upload or API, not by the spreadsheet import.Carried with mapping
EmailsEmails saved to matters or to the storeHeldFiled from Outlook through the email filing module.Has a place in partEmails reach a matter through mail sync from a connected mailbox.Carried with mapping
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeNotes on matters, contacts and companies.Confirmed 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 placeMatter, contact and company fields. A field must exist before data is imported into it.Carried with mapping
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partDocument and email templates are rebuilt with Lawmatics merge fields.Confirmed in the analysis

What the plans mean

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

Mostly a contact list, cleaned before it lands.

Lawmatics is built for contacts, leads and the conversations around them. What eDOCS can offer it first is a list of people and companies, and sometimes a history that can be attached as notes. Whether anything else it holds has a place depends on what Lawmatics keeps besides contacts, and the table above shows that kind by kind. What has no place stays where it is or is archived.

A contact list taken from a system that was never a CRM needs work before it is useful. Names are split or joined differently, the same client appears under several spellings, and there is no record of who agreed to be contacted. The list is cleaned and de-duplicated, matched against what Lawmatics already holds, and loaded with a source tag, so the firm can tell these contacts from the ones that came through intake.

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

Lawmatics takes matters, contacts and companies from CSV files, and its API accepts notes, tasks, appointments, files, time entries and invoices. It is an intake and client relationship system, so a firm arriving from full practice management has to decide what it is for. People and matters load well. There is no general ledger, and years of billing history have no natural home.

  1. Contacts and matters load separately

    The import expects two spreadsheets: one for contacts or companies with no case, such as referrers and other lawyers, and one for matters. A matter import creates the matter and its primary contact together. Every matter has exactly one primary contact, so joint clients are loaded as one primary and one relationship.

  2. Set up before loading

    Owner, stage, practice area, source and campaign are matched by name. A value on the spreadsheet that does not match one in Lawmatics exactly creates a new one, which is how a firm ends up with two spellings of the same practice area. Users, pipelines, practice areas and marketing sources are set up first, and custom fields must exist before data is loaded into them.

  3. Statuses and matter numbers

    Each imported matter must be PNC (potential new client), Hired or Lost, with open and closed handled as sub-statuses the firm creates. The case number is a system field assigned by an auto-numbering pattern and cannot be edited by hand afterwards. Whether old matter numbers can be loaded into it, or belong in a custom field, is tested in the trial load.

  4. Duplicates are matched by email

    With Match Contacts by Email switched on, a contact whose email already exists is skipped or updated, never doubled. Names and phone numbers are not checked. Matters are not deduplicated at all, so two rows with one email create two matters on one contact. Clean-up therefore happens in the spreadsheet, and automations are switched off for every load.

  5. What has no place

    There is no general ledger. The Time & Billing module holds time entries, expenses, invoices and a trust account with a running balance per matter, and past invoices are entered as already sent and then marked paid. A firm that needs its full accounting history keeps the old system read only or carries the books in an accounting package.

More about moving into Lawmatics

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Lawmatics on this route, which makes it repeatable: a load can be run again until it is right.

  1. Analysis

    We read what eDOCS holds and how it is organised, then agree with you where each kind of record will sit in Lawmatics. 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 Lawmatics 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 toLawmatics

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

Loaded data is not yet a working system. This is what NewLaw sets up in Lawmatics, beyond the migration, so that people can work in it from the first day.

In Lawmatics the design comes before the data. The pipeline stages, practice areas, custom fields and relationship types decide what the import can hold, and the forms and automations decide what the firm’s intake looks like from the first day. If a practice system sits behind it, the field mapping between the two is part of the same job.

Set-up decisions in Lawmatics

  • Pipelines and stages for intake and for open matters
  • Practice areas, sub-statuses, relationship types and the matter numbering pattern
  • Custom fields on matters, contacts and companies
  • Intake forms, booking links and e-signature document templates
  • Follow-up automations, with marketing sources and campaigns
  • Mail and calendar sync, user roles and practice system integration

Questions

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

In part. Files and folders on each matter, added by upload or API, not by the spreadsheet import. The structure in eDOCS is mapped to what Lawmatics offers and you see the mapping before the load. File dates are carried.

Does everything in eDOCS have a place in Lawmatics?

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

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

Documents, 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

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

Moving from eDOCS to Lawmatics?

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

We reply within one business day.