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

Data migration route

DocuWare to NetDocuments migration

DocuWare is a document management system, and NetDocuments is a cloud one. The test of this move is whether profiles, versions and access rules survive it.

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

What moves

What moves from DocuWare to NetDocuments

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

Records in DocuWare and their place in NetDocuments
RecordIn DocuWareIn NetDocumentsWhat is planned
DocumentsFiles stored in or linked from the systemHeldIn file cabinets, found by index fields. One document may contain several files.Has a placeImported with profile values, folder, dates and access set per document.Carried across
EmailsEmails saved to matters or to the storeHeld in partAn email can be stored with its attachments as one document.Has a placeLoaded as email items profiled to the matter.Carried across
NotesFile notes, matter notes and contact notesHeld in partAnnotations and stamps are stored with the document, on layers over the file.No placeFile notes are loaded as documents in the matter workspace.Kept as a readable archive
TasksTo-dos and workflow steps assigned to peopleTo be confirmedWorkflow tasks exist where workflow has been configured.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldIndex fields are defined separately for each file cabinet.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
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedNo placeConfirmed 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 DocuWare.
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.
Kept as a readable archive
NetDocuments has no place for it. It is exported in a format that opens without DocuWare 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, versions and security, kept intact.

Between two document management systems the files are the easy part. What a firm has built in DocuWare 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.

How DocuWare is run at the firm is settled at the start of the analysis, because its maker’s own material does not settle it. The usual arrangement is assumed here. Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of DocuWare depends on its export tools and on what its maker provides on request, and that is confirmed during the analysis, before a date is set. The subscription to DocuWare is kept running until the checks on NetDocuments are finished.

Where the data is now

DocuWare is organised for retrieval by index, so an export is a set of documents plus a table of index values, one table per file cabinet. There may be no folder structure at all. The move turns index fields into whatever the destination files by, which for a legal system means deriving a client and matter for every document from fields that were designed for something else.

  1. Each file cabinet stands alone

    Every file cabinet has its own index fields. An invoices cabinet might have supplier, date and amount, while a correspondence cabinet has a matter number and document type. Each is mapped separately, and some, such as supplier invoices, may belong with the accounts system’s records and not in the matter files at all.

  2. One document, several files

    A DocuWare document can hold up to 999 files clipped together: a scanned letter, a Word reply, an email with attachments. Most destinations store one file per document. The plan says whether a clipped set becomes one merged PDF, a group of related documents or a folder.

  3. Scans are PDF/A, the rest native

    Paper scanned through DocuWare is stored as PDF/A, while Office and PDF files are kept in their original format. Scanned items depend on a full-text index to be searchable. If the destination will not run its own text recognition, the text has to travel with the file, which is checked on a sample.

  4. Storage changed at version 7

    On-premises systems that began on version 6 or earlier have documents in two layouts: older ones with an XML header file and numbered file names, newer ones with index data in the database and file names that are GUIDs. The route for extraction is chosen in the analysis with both layouts in mind, so that nothing depends on guessing which one a document uses.

  5. Document trays

    Items that were scanned or imported but never indexed sit in users’ document trays, outside every file cabinet. Users are asked to store or delete them before the freeze. Whatever is left is listed by user, so nothing is lost by oversight.

More about moving off DocuWare

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 DocuWare 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 DocuWare: 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 DocuWare, a final pass over a weekend picks up what changed since the trial. DocuWare 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 DocuWare 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 fromDocuWare
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 DocuWare 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

DocuWare to NetDocuments: what firms ask

Our DocuWare has no folders. How will documents be filed in the new system?

From the index. If a file cabinet has a matter or client number field, documents are filed by it. If it has only names or dates, the values are matched to the matter list and the unmatched are reported. Document type fields usually become folders or categories in the destination.

Can stamps and annotations be kept?

DocuWare keeps annotations and stamps as layers over the file, not inside it. To keep an approval stamp visible elsewhere, it has to become part of a PDF copy, and whether DocuWare can produce that copy in bulk is confirmed in the analysis. The firm chooses, for each file cabinet, whether to take the original, the stamped copy, or both.

Do documents from DocuWare 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.

What happens to records NetDocuments has no place for?

On this route that is notes. They are exported from DocuWare 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 DocuWare data is loaded into NetDocuments?

Custom fields are carried with mapping, so each mapping is agreed with you first. Tasks, templates and intake records 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

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

Moving from DocuWare 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.