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

Data migration route

Outlook Data Files (.pst) to SharePoint migration

Outlook Data Files (.pst) are contact and calendar data kept as files, and SharePoint is cloud file storage. What moves is the files, plus a readable export of everything else the old system holds.

FromOutlook Data Files (.pst)Files
  1. Documents: Carried across
  2. Contacts: Carried with mapping
  3. Emails: Carried with mapping
  4. Notes: Carried with mapping
  5. Calendar: Carried with mapping
  6. Tasks: Carried with mapping
  7. Custom fields: Carried with mapping
ToSharePointCloud
  • 1 carried
  • 6 mapped
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Outlook Data Files (.pst) to SharePoint

Each row is a kind of record Outlook Data Files (.pst) hold, whether SharePoint has a place for it, and what is planned. On this route one kind of record carries across and six kinds need mapping.

Records in Outlook Data Files (.pst) and their place in SharePoint
RecordIn Outlook Data Files (.pst)In SharePointWhat is planned
ContactsClients, other parties and referrersHeldThe owner’s Outlook contacts, if they were stored in or exported to the file.Has a place in partOnly as rows in a list built for the purpose.Carried with mapping
DocumentsFiles stored in or linked from the systemHeld in partOnly as attachments on messages and other items.Has a placeFiles in libraries, with columns and versions.Carried across
EmailsEmails saved to matters or to the storeHeldSent and received messages in the owner’s folder tree.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 partOutlook notes and journal entries, not matter file notes.Has a place in partAs documents, or as rows in a notes list if one is built.Carried with mapping
CalendarAppointments, court dates and deadlinesHeldAppointments and meetings from the owner’s calendar.Has a place in partPossible as a list; usually left in Outlook.Carried with mapping
TasksTo-dos and workflow steps assigned to peopleHeldOutlook tasks belonging to the owner.Has a place in partPossible as a list; no legal workflow built in.Carried with mapping
Custom fieldsFields and record types the firm added itselfHeld in partOutlook categories applied to items.Has a placeColumns and content types on libraries and lists.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 Outlook Data Files (.pst).
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.

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

An export the firm can open without the system.

SharePoint holds files, and most of what Outlook Data Files (.pst) hold is records. This route is therefore an export job. Each kind of record is written out in a format that opens without the system it came from: lists as spreadsheets, statements and invoices as PDFs, attachments as the files they were. The export is laid out in folders that make sense to someone who never used Outlook Data Files (.pst), by client or by year, with a short index file saying what is where.

Firms do this when a subscription is ending, when a system is being retired, or to meet a retention rule. The test of the result is whether a question can still be answered from it years later: what was this client invoiced, who signed this agreement and when. So the trial export is checked by asking those questions of it. Totals are agreed to the system’s own reports, and access to the folder in SharePoint is limited before the export is copied in.

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

Where the data is now

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.

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

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

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

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

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

More about moving off Outlook Data Files (.pst)

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 Outlook Data Files (.pst) hold 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 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.

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

Step 1 of 5: Start with the route

Moving fromOutlook Data Files (.pst)
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 Outlook Data Files (.pst) 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

Outlook Data Files (.pst) to SharePoint: 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 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 Outlook Data Files (.pst) have a place in SharePoint?

On paper, yes: each kind of record Outlook Data Files (.pst) hold has a place in SharePoint. Whether every field fits is a separate question, and the analysis answers it field by field. Anything with no place comes across as a note or stays behind, and you see which before the move.

What has to be decided before Outlook Data Files (.pst) data is loaded into SharePoint?

Contacts, emails, notes, calendar entries, tasks and custom fields are carried with mapping, so each mapping is agreed with you first. 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

Outlook Data Files (.pst) and SharePoint are the names and marks of their owners, used here only to identify the two systems.

Moving from Outlook Data Files (.pst) 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.