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

Data migration route

DocuWare to Server drives migration

DocuWare is a document management system, and Server drives are plain files on equipment the firm controls. Storage only has folders, so the move decides what of each document’s profile is kept in names and what in an index.

FromDocuWareDocument management
  1. Documents: Carried across
  2. Emails: Carried with mapping
  3. Notes: Carried with mapping
  4. Tasks: Confirmed in the analysis
  5. Templates: Confirmed in the analysis
  6. Intake: Confirmed in the analysis
ToServer drivesFiles
  1. Custom fields: Kept as a readable archive
Readable archiveNo place in Server drives
  • 1 carried
  • 2 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 Server drives

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

Records in DocuWare and their place in Server drives
RecordIn DocuWareIn Server drivesWhat is planned
DocumentsFiles stored in or linked from the systemHeldIn file cabinets, found by index fields. One document may contain several files.Has a placeFiles in folders, named and dated during the load.Carried across
EmailsEmails saved to matters or to the storeHeld in partAn email can be stored with its attachments as one document.Has a place in partAs .msg or .eml files in each matter’s correspondence folder.Carried with mapping
NotesFile notes, matter notes and contact notesHeld in partAnnotations and stamps are stored with the document, on layers over the file.Has a place in partAs a text or PDF file per matter, not as separate records.Carried with mapping
TasksTo-dos and workflow steps assigned to peopleTo be confirmedWorkflow tasks exist where workflow has been configured.No placeConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldIndex fields are defined separately for each file cabinet.No placeKept as a readable archive
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partPrecedents as Word files; merge fields tied to the old system stop working.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedNo placeConfirmed in the analysis

What the plans mean

Carried across
Server drives has a place for this kind of record. It is loaded there and checked against DocuWare.
Carried with mapping
Server drives 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
Server drives 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 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 DocuWare to Server drives 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 Server drives before anyone else is given access.

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. DocuWare is hosted by its maker and Server drives sit on equipment the firm controls. The data leaves a service that was backed up for the firm and arrives somewhere the firm must back up itself, so backup and access are arranged before the export is copied in. What DocuWare will release depends on its export tools, and that is confirmed in the analysis.

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

Some firms leave a practice or document system and keep their documents on a server drive, either as the working store or as the archive of a system being switched off. The files will arrive without the database that described them. Everything the firm wants to keep knowing about a document has to be put into its path, its name or an index file.

  1. Agree the tree and the names

    A fixed pattern is chosen, for example client name and number, then matter number and short description, then a standard set of subfolders. Document titles from the old system become file names. Where two documents share a title, a date or sequence number is added so nothing is overwritten.

  2. Budget the path length

    Share name, client, matter, subfolder and file name all count towards the 260 character limit that many Windows programs still apply. The pattern is tested against the firm’s longest client names and document titles before the load. Descriptions are trimmed by rule, never by cutting off the file extension.

  3. Dates have to be set deliberately

    A file written to the server today is dated today unless its modified date is set from the old system’s record. Document dates are how lawyers find things in a folder. Which date each file is to carry is agreed in the analysis, and the trial load checks a sample.

  4. Emails become message files

    Emails filed to matters in the old system are written out as .msg or .eml files in a correspondence folder, named by date, sender and subject so they sort in order. Attachments stay inside the message. Subjects with characters Windows forbids are cleaned, and long ones cut.

  5. Keep an index beside the files

    A spreadsheet or small database listing every document with its matter, author, original date, document type and new path is the only place the old system’s profile data survives. It lets someone find a document by something other than its name. What the index records, and who keeps it, is decided in the analysis.

More about moving into Server drives

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Server drives 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 Server drives. 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 Server drives 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 toServer drives

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 Server drives. 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

Server drives are 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.

A server drive does only what the firm and its IT provider make it do. Setting one up as a document store means building the share, deciding who can open which folders, and arranging the protections a document system would have supplied: backups, earlier versions and a way to recover a deleted folder. The filing rule is written down and taught.

What is agreed and set up

  • Share and top-level folders for clients, precedents and administration
  • Security groups and folder permissions, with restricted matters separate
  • Drive letter mapped for every user at sign-in
  • Backup schedule and shadow copies for earlier versions
  • Written naming rule for client, matter and document names
  • Read-only area for closed matters and archived system exports

Questions

DocuWare to Server drives: 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 Server drives?

Server drives store documents. Files in folders, named and dated during the load. 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 Server drives have no place for?

On this route that is custom fields. 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 Server drives?

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

Moving from DocuWare to Server drives?

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

We reply within one business day.