Data migration route
Worldox to NetDocuments migration
Worldox is a server-based document management system, and NetDocuments is a cloud one. The test of this move is whether profiles, versions and access rules survive it.
WorldoxServer- Documents: Carried across
- Emails: Carried across
- Matters: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Tasks: Confirmed in the analysis
NetDocumentsCloud- Notes: Kept as a readable archive
- 2 carried
- 3 mapped
- 1 to confirm
- 1 archived
What moves
What moves from Worldox to NetDocuments
Each row is a kind of record Worldox holds, whether NetDocuments has a place for it, and what is planned. On this route two kinds of record carry across, three kinds need mapping, one kind has no place in NetDocuments and is archived and one kind is confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | Held in partClient and matter exist as coded profile fields with descriptions, not as matter records. | Has a place in partAs a client and matter value with its workspace. Other matter details stay in practice management. | Carried with mapping |
| DocumentsFiles stored in or linked from the system | HeldOrdinary files on the network, named by an eight-digit Doc ID, each with a profile. | Has a placeImported with profile values, folder, dates and access set per document. | Carried across |
| EmailsEmails saved to matters or to the store | HeldOutlook messages and attachments are profiled and saved to cabinets like other documents. | Has a placeLoaded as email items profiled to the matter. | Carried across |
| NotesFile notes, matter notes and contact notes | Held in partEach profile has a comments field of up to 5,000 characters. | No placeFile notes are loaded as documents in the matter workspace. | Kept as a readable archive |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | To be confirmed | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldEach cabinet has its own profile form and field tables, set up by the firm. | Has a placeAs custom profile attributes, created in the repository before the load. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | Held in partPrecedents are kept as documents, often in a cabinet of their own. | Has a place in partLoaded as documents in a precedents cabinet or workspace. Automation is set up afresh. | Carried with mapping |
What the plans mean
- Carried across
- NetDocuments has a place for this kind of record. It is loaded there and checked against Worldox.
- 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 Worldox 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.
Worldox and NetDocuments are related: they share a maker, or one is built on the other. Where a maker offers its own path between two of its products, that path is looked at first, and the analysis establishes what it carries and what it leaves. The points below apply wherever the two differ.
Between two document management systems the files are the easy part. What a firm has built in Worldox 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.
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. NetDocuments 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
Leaving Worldox
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.
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.
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.
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.
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.
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.
Where it is going
Arriving in NetDocuments
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.
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.
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.
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.
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.
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.
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.
Analysis
We read what Worldox 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.
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.
Trial load
A trial is loaded into NetDocuments 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.
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
What happens after you send it
- A free first call
We go through your answers with you and ask about anything they leave open.
- An analysis of what Worldox 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.
- 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
Worldox to NetDocuments: 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 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 Worldox 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 Worldox data is loaded into NetDocuments?
Matters, 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.
Other routes
Other routes from Worldox and into NetDocuments
Other destinations from Worldox
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.
Choose your systems
Technology stack selection
Decide which practice management system your firm runs, with the evidence and the cost beside it.
About four weeks for a firm of about 15 people. Fixed price, set after a free first call.
Move your data
Data migration
Your data is cleaned up before anything moves, then a trial load is checked against the old system.
Fixed price, agreed after the analysis.
Set up your new system
Implementation
Your new system set up around the way your firm works: configuration, document automation and training.
A small firm of 1 to 10 users typically takes 4 to 8 weeks. A mid-sized firm of 10 to 50 users takes 8 to 16 weeks.
Put AI to work
AI advisory and enablement
A small group of your people learn to use an approved AI tool on real work, under written rules.
Two to four weeks for a small first group. Fixed price, set after a free first call.
Worldox and NetDocuments are the names and marks of their owners, used here only to identify the two systems.
Moving from Worldox 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.