Data migration route
Outlook Data Files (.pst) to NetDocuments migration
Outlook Data Files (.pst) are contact and calendar data kept as files, and NetDocuments is a cloud document management system. Only files and their details have a place there, so this route carries the documents and archives the rest.
Outlook Data Files (.pst)Files- Documents: Carried across
- Emails: Carried across
- Custom fields: Carried with mapping
- Tasks: Confirmed in the analysis
NetDocumentsCloud- Contacts: Kept as a readable archive
- Notes: Kept as a readable archive
- Calendar: Kept as a readable archive
- 2 carried
- 1 mapped
- 1 to confirm
- 3 archived
What moves
What moves from Outlook Data Files (.pst) to NetDocuments
Each row is a kind of record Outlook Data Files (.pst) hold, whether NetDocuments has a place for it, and what is planned. On this route two kinds of record carry across, one kind needs mapping, three kinds have no place in NetDocuments and are archived and one kind is confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| ContactsClients, other parties and referrers | HeldThe owner’s Outlook contacts, if they were stored in or exported to the file. | No place | Kept as a readable archive |
| DocumentsFiles stored in or linked from the system | Held in partOnly as attachments on messages and other items. | Has a placeImported with profile values, folder, dates and access set per document. | Carried across |
| EmailsEmails saved to matters or to the store | HeldSent and received messages in the owner’s folder tree. | Has a placeLoaded as email items profiled to the matter. | Carried across |
| NotesFile notes, matter notes and contact notes | Held in partOutlook notes and journal entries, not matter file notes. | No placeFile notes are loaded as documents in the matter workspace. | Kept as a readable archive |
| CalendarAppointments, court dates and deadlines | HeldAppointments and meetings from the owner’s calendar. | No place | Kept as a readable archive |
| TasksTo-dos and workflow steps assigned to people | HeldOutlook tasks belonging to the owner. | To be confirmed | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | Held in partOutlook categories applied to items. | Has a placeAs custom profile attributes, created in the repository before the load. | 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 Outlook Data Files (.pst).
- 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 Outlook Data Files (.pst) 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
Only the documents have a place here.
NetDocuments is a document management system: it takes files and the details that describe them. Most of what Outlook Data Files (.pst) hold is not files. Entries, balances, settings and lists have no place in a document store, and the table above is short for that reason. What can move is any document Outlook Data Files (.pst) produced or stored: invoices as PDFs, signed agreements, attachments, exported reports. Each is filed under the client or matter it relates to.
The useful version of this job is often an archive. A firm retiring a system wants its records readable later without keeping the subscription or the old PC. The data is exported in open formats, spreadsheets and PDFs, and filed in NetDocuments in a workspace set aside for it, with access limited to the people who need it. That gives the firm one place to look, under the same retention rules as the rest of its documents.
With Outlook Data Files (.pst) the files are already on equipment the firm controls, so there is no export step: they are read where they are. Upload speed sets the pace for a large store. The originals stay in place, unchanged, until the firm has checked the copy in NetDocuments.
Where the data is now
Leaving Outlook Data Files (.pst)
Getting email out of PST files and onto matters is a matching problem. Reading the files is the easy part. Each one reflects a single person’s filing habits, the same message sits in several people’s files, and nothing in a message says which matter it belongs to. The rules for matching are agreed with the firm and tested on one fee earner’s mail first.
Find all of them
PSTs are not in one place. Outlook’s default folder is Outlook Files under each user’s Documents, older versions used a hidden AppData folder, and copies turn up on the server and on external disks. A search by file type across every machine and share produces the list, with owner, size and last-modified date.
One person’s folders, one person’s logic
If the owner filed by client or matter, folder names are matched to the matter list and whole folders are assigned. Where everything is in Inbox and Sent Items, messages are matched on the correspondent’s address and on matter references in the subject line. Whatever fits neither rule is reported as unmatched.
The same email many times over
A message sent to four people at the firm is in four PSTs, and again in the sender’s. Loaded as they stand, a matter receives five copies. Duplicate messages are merged before loading where they can be matched, so each appears once on the matter with all recipients shown.
Old formats and damaged files
PSTs from Outlook 2002 and earlier use an older format capped at 2 GB, and Microsoft does not support PSTs being used from a network share, so files kept that way are checked with particular care. Whether each file opens and reads in full is established in the analysis. Unreadable ones are named in the report.
More than mail in the file
Calendars, contacts and tasks are in there too. Old appointments are seldom wanted in the new system. Contacts often are, but a personal address book is full of duplicates of the firm’s client list. The firm decides per item type, and contacts are merged against existing records, not added beside them.
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 Outlook Data Files (.pst) hold 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 Outlook Data Files (.pst): 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 Outlook Data Files (.pst), a final pass over a weekend picks up what changed since the trial. Outlook Data Files (.pst) are 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 Outlook Data Files (.pst) 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 Outlook Data Files (.pst) 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
Outlook Data Files (.pst) to NetDocuments: what firms ask
Can every email be filed to the right matter automatically?
No. A good share can, where the owner kept matter folders or the firm puts a reference in its subject lines. The remainder is filed by correspondent to the client, or left in a searchable archive outside the matters. Each rule’s share is reported after the trial load, so the firm knows the result before committing.
Some of our PST files are password protected. Can they still be read?
The password is needed, and the person who set it is the one to ask. Where they have left and nobody recorded it, the file is listed as inaccessible. It is kept with the fall-back records should the password be found later, and the matters likely to be affected are noted from the file’s owner and dates.
Should we move the PSTs into Microsoft 365 instead of the practice system?
Those are two different aims. Importing into mailboxes or online archives gets the files off local disks and keeps the mail searchable by its owner. Filing to matters makes the mail part of the client file for everyone. Some firms do the first for all mail and the second for chosen fee earners.
Do documents from Outlook Data Files (.pst) 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 contacts, notes and calendar entries. They are exported from Outlook Data Files (.pst) 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 Outlook Data Files (.pst) data is loaded into NetDocuments?
Custom fields 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 Outlook Data Files (.pst) and into NetDocuments
Other destinations from Outlook Data Files (.pst)
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.
Outlook Data Files (.pst) and NetDocuments are the names and marks of their owners, used here only to identify the two systems.
Moving from Outlook Data Files (.pst) 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.