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

Data migration route

Worldox to SharePoint migration

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

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

What moves

What moves from Worldox to SharePoint

Each row is a kind of record Worldox holds, whether SharePoint has a place for it, and what is planned. On this route one kind of record carries across, five kinds need mapping and one kind is confirmed in the analysis.

Records in Worldox and their place in SharePoint
RecordIn WorldoxIn SharePointWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeld in partClient and matter exist as coded profile fields with descriptions, not as matter records.Has a place in partAs a site, library, folder or list row the firm designs; no built-in matter record.Carried with mapping
DocumentsFiles stored in or linked from the systemHeldOrdinary files on the network, named by an eight-digit Doc ID, each with a profile.Has a placeFiles in libraries, with columns and versions.Carried across
EmailsEmails saved to matters or to the storeHeldOutlook messages and attachments are profiled and saved to cabinets like other documents.Has a place in partAs .msg or .eml files, with columns for sender and date if set up.Carried with mapping
NotesFile notes, matter notes and contact notesHeld in partEach profile has a comments field of up to 5,000 characters.Has a place in partAs documents, or as rows in a notes list if one is built.Carried with mapping
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a place in partPossible as a list; no legal workflow built in.Confirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldEach cabinet has its own profile form and field tables, set up by the firm.Has a placeColumns and content types on libraries and lists.Carried with mapping
TemplatesPrecedents, document templates and automationHeld in partPrecedents are kept as documents, often in a cabinet of their own.Has a place in partPrecedents as files; templates can be offered from a library.Carried with mapping

What the plans mean

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

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

Worldox 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. SharePoint 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

Worldox documents are real files in real folders on the firm’s network, which makes them easy to reach and easy to misread. The folder path encodes the client and matter codes, the file name is a number, and the description users see is kept by Worldox, not in the file name. A move reads all three together, so each file arrives with its title, matter and author.

  1. File names are numbers

    Worldox numbers documents consecutively and uses the eight-digit Doc ID plus the extension as the file name. Copy a matter folder to another drive and you get files called 00123456.docx with no titles. The description, up to 128 characters, comes from the profile, and the migration names each file from it.

  2. The path is the profile

    Each cabinet has a base path, and the client, matter and document type chosen on the profile form decide the folder beneath it. Reading a path back gives the codes. The field tables give what the codes mean. Both are needed, because a folder called 004417 says nothing until the table says which client that is.

  3. Cabinets differ from one another

    A site can have up to 150 cabinets and each has its own set of fields. One may file by client and matter, another by department and year, and a legacy cabinet may hold documents kept from an earlier system for reference only. Every cabinet gets its own mapping.

  4. Versions, archive and legal hold

    Earlier versions of a document are kept and listed with it, and cabinets can have Archive and Legal Hold areas for documents moved out of the active tree. Whether each of these comes across is a scope question. The file counts in the analysis are split into current, versions, archived and held.

  5. Security lives in two places

    Access is set by Worldox administrators in WDADMIN, by cabinet and by folder, which is how ethical walls are built. Individual files can also be given their own security when profiled. The Windows permissions on the share do not tell the whole story, so restrictions are read from Worldox itself.

More about moving off Worldox

Where it is going

SharePoint will take a firm’s documents in almost any arrangement, which is the difficulty. The structure has to be chosen before the load: what a client is, what a matter is, and where security is applied. Changing it afterwards means moving every file again. Most of the effort goes into that design and into the columns that describe each document.

  1. Site, library or folder per matter

    A matter can be a site, a library within a client site, or a folder in one large library. Each choice has consequences for permissions, for search and for how a new matter is opened. The firm makes that decision, and the people who open matters every day should be part of it.

  2. Columns are built before content

    If documents are to carry matter number, client, document type or author as columns, those columns and any content types exist before loading, so each file can be tagged as it arrives. Tagging hundreds of thousands of documents afterwards is a second project that seldom gets finished.

  3. The 400 character path

    SharePoint limits the full decoded path, site and library and folders and file name, to 400 characters. A deep tree copied from a server drive under a long site name can cross it. Path lengths are calculated against the planned structure, not the old one, before any file moves.

  4. Large libraries and the view threshold

    A library can hold millions of files, but a view that tries to show more than 5,000 items at once runs into the list view threshold. One flat library with a folder per matter needs indexed columns and filtered views from the start, or views begin to fail as the library fills.

  5. Security by library, not by file

    Microsoft supports up to 50,000 unique permissions in a library and recommends staying under 5,000. Restricting matters one folder at a time reaches that sooner than firms expect. Restricted work is better grouped into its own site or library, so the permission is set once.

More about moving into SharePoint

How NewLaw runs it

Four steps, in this order.

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

  1. Analysis

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

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

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

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

Making SharePoint work as a firm’s document store is a design and build job in its own right. The sites, libraries, columns and permission groups are created, a way of opening a new matter is put in place so the structure repeats itself, and the Outlook and Teams habits around it are agreed. Search is tested with real questions from fee earners.

What is agreed and set up

  • Site and library structure for clients and matters
  • Columns and content types for matter number and document type
  • Permission groups, with restricted matters in their own libraries
  • A repeatable way to create each new matter’s workspace
  • Version history limits and retention labels for closed matters
  • Views, indexed columns and search tested on loaded data

Questions

Worldox to SharePoint: what firms ask

Can we just copy the Worldox folders to the new system?

The files will copy, but they will be named with eight-digit numbers and sit in folders named with codes. The descriptions, authors, document types and comments are in the profiles. A proper move pairs each file with its profile first, then names it and files it by matter in the destination.

Do our Doc IDs carry over?

The new system will give each document its own identifier. The Worldox Doc ID can be kept in a field or added to the document name, which is worth doing where the firm prints Doc IDs in document footers. Whether it is searchable afterwards depends on the destination and is confirmed in the analysis.

What about emails saved into Worldox?

They were saved with a profile in the same way as documents, so they move with the matter. In the destination they should arrive as emails, with sender and date readable, not as attachments nobody can sort. The trial load is where that is checked, on a sample of matters with heavy correspondence.

Do documents from Worldox keep their folders and dates in SharePoint?

SharePoint stores documents. Files in libraries, with columns and versions. 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 Worldox have a place in SharePoint?

Most of it does on paper. Tasks 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 SharePoint is kept as a readable archive, and you see which before the move.

What has to be decided before Worldox data is loaded into SharePoint?

Matters, emails, notes, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Tasks 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

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

Moving from Worldox to SharePoint?

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

We reply within one business day.