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

Data migration route

eDOCS to Dropbox migration

eDOCS is a server-based document management system, and Dropbox 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.

FromeDOCSServer
  1. Documents: Carried across
  2. Emails: Carried with mapping
  3. Notes: Confirmed in the analysis
  4. Tasks: Confirmed in the analysis
  5. Templates: Confirmed in the analysis
ToDropboxCloud
  1. Matters: Kept as a readable archive
  2. Custom fields: Kept as a readable archive
Readable archiveNo place in Dropbox
  • 1 carried
  • 1 mapped
  • 3 to confirm
  • 2 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from eDOCS to Dropbox

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

Records in eDOCS and their place in Dropbox
RecordIn eDOCSIn DropboxWhat 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.No placeA matter is a folder named by the firm’s convention.Kept as a readable archive
DocumentsFiles stored in or linked from the systemHeldFiles on document servers, each with a profile in the library’s SQL database.Has a placeFiles in folders; the folder path is the only index.Carried across
EmailsEmails saved to matters or to the storeHeldFiled from Outlook through the email filing module.Has a place in partAs .msg or .eml files filed in the matter folder.Carried with mapping
NotesFile notes, matter notes and contact notesTo be confirmedHas a place in partAs documents saved to the matter folder.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleTo be confirmedNo placeConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldProfile forms and the fields on them are designed for each library.No placeKept as a readable archive
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partPrecedents load as ordinary files in a precedents folder.Confirmed in the analysis

What the plans mean

Carried across
Dropbox has a place for this kind of record. It is loaded there and checked against eDOCS.
Carried with mapping
Dropbox 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.
Kept as a readable archive
Dropbox has no place for it. It is exported in a format that opens without eDOCS and handed to the firm as a read-only archive.

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 eDOCS to Dropbox 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 Dropbox before anyone else is given access.

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

Loading matter files into Dropbox is a matter of getting the tree right, since the tree is all there is. No field holds a matter number or a client name. The folder names carry that, so the naming rule is agreed first: what a client folder is called, what a matter folder is called, and which subfolders every matter gets.

  1. Team folders before files

    Team folders are shared with groups, and each group is given an editor or view-only role. The groups and the top-level folders are created before the load so that files arrive already restricted. Loading first and sharing afterwards leaves a period in which the wrong people can see everything.

  2. Keep paths under 260 characters

    Dropbox’s naming guidance asks for full paths shorter than 260 characters. Matter trees from document systems often exceed that once the client name, matter description and subfolders are joined. Long paths are measured early and cut back by rule, usually by trimming the matter description and keeping the number.

  3. Characters that get swapped

    On Windows, the desktop app replaces restricted characters in names with an underscore. A file called Smith v Jones: Affidavit becomes something slightly different on some machines. Names are cleaned before loading so that the file has one name everywhere and matches the index kept from the old system.

  4. Matter data has nowhere to go

    Parties, matter type, responsible lawyer, open and closed dates: none of it has a field here. If the firm is leaving a practice management system and keeping only documents, that data can be kept as an exported spreadsheet beside the folders, so they can still be read against it. Whether one is produced is decided in the analysis.

  5. History starts on loading day

    Version history in Dropbox begins when a file arrives. Earlier versions from the old system come across as separately named files in the matter folder, or stay behind. The firm sees a sample matter loaded with its earlier versions as named copies before choosing.

More about moving into Dropbox

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Dropbox 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 Dropbox. 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 Dropbox 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 toDropbox

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

Structure, permissions and handover

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

Beyond the load, a firm on Dropbox needs the account arranged so the files belong to the firm and not to individuals. That means a team plan with an administrator, groups that match how the firm works, and a decision about which folders sync to every computer. A written filing rule tells staff where each new matter folder goes.

What is agreed and set up

  • Team folders for clients, precedents and administration
  • Groups by team, each with an editor or viewer role
  • Which folders sync to PCs and which stay online-only
  • Rules for sharing links and folders with clients
  • A written naming rule for client and matter folders
  • Steps for removing a leaver without losing their folders

Questions

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

Dropbox stores documents. Files in folders; the folder path is the only index. 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.

What happens to records Dropbox has no place for?

On this route that is matters and custom fields. They are exported from eDOCS in formats that open without it, spreadsheets and PDFs, and handed to the firm as a read-only archive. You see the list before the move.

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

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

Moving from eDOCS to Dropbox?

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

We reply within one business day.