Data migration route
Outlook Data Files (.pst) data to Microsoft SQL Server
Outlook Data Files (.pst) are contact and calendar data kept as files, and Microsoft SQL Server is a database on a server the firm runs. This is not a move to a new working system: the route writes out what Outlook Data Files (.pst) hold and keeps it readable and open to queries.
Outlook Data Files (.pst)Files- Contacts: Exported in full
- Notes: Exported in full
- Calendar: Exported in full
- Tasks: Exported in full
- Documents: Exported with mapping
- Emails: Exported with mapping
- Custom fields: Exported with mapping
Microsoft SQL ServerServer- 4 carried
- 3 mapped
What moves
What moves from Outlook Data Files (.pst) to Microsoft SQL Server
Each row is a kind of record Outlook Data Files (.pst) hold, whether Microsoft SQL Server has a place for it, and what is planned. On this route four kinds of record carry across and three kinds need mapping.
| Record | What is planned | ||
|---|---|---|---|
| ContactsClients, other parties and referrers | HeldThe owner’s Outlook contacts, if they were stored in or exported to the file. | Has a placePeople and companies, with their roles on each matter. | Exported in full |
| DocumentsFiles stored in or linked from the system | Held in partOnly as attachments on messages and other items. | Has a place in partAs files in folders with an index table; storing files in the database is possible. | Exported with mapping |
| EmailsEmails saved to matters or to the store | HeldSent and received messages in the owner’s folder tree. | Has a place in partAs message files with an index table, or as rows of header fields. | Exported with mapping |
| NotesFile notes, matter notes and contact notes | Held in partOutlook notes and journal entries, not matter file notes. | Has a placeRows of text linked to matters and contacts. | Exported in full |
| CalendarAppointments, court dates and deadlines | HeldAppointments and meetings from the owner’s calendar. | Has a placeRows of appointments and key dates; nothing displays them as a calendar. | Exported in full |
| TasksTo-dos and workflow steps assigned to people | HeldOutlook tasks belonging to the owner. | Has a placeRows with assignee, due date and status. | Exported in full |
| Custom fieldsFields and record types the firm added itself | Held in partOutlook categories applied to items. | Has a placeAs added columns, or a table of field names and values. | Exported with mapping |
What the plans mean
- Exported in full
- Microsoft SQL Server has a place for this kind of record. It is loaded there and checked against Outlook Data Files (.pst).
- Exported with mapping
- Microsoft SQL Server 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
Not a new system. A complete copy the firm can query.
Writing Outlook Data Files (.pst) out to Microsoft SQL Server is not a migration into a new working system. Nobody will open a matter there on Monday morning. The aim is a complete, faithful copy that can be queried and reported on after the old system is gone. So the rules change. Nothing is cleaned or merged unless the firm asks, because an archive should show the records as they were. Every table and field is carried, including those a new system would have had no place for.
What makes an archive usable is the description that goes with it. The export is delivered with a plain account of each table: what it holds, how it joins to the others, what the codes mean. Record counts and financial totals are agreed to the reports in Outlook Data Files (.pst) as at the export date, so the archive can stand as the record. Documents are exported beside the data with a table linking each file to its matter. Access is restricted, since the archive holds everything the live system did.
Both ends are on equipment the firm controls, so the work is done on the firm’s own network with its IT provider. Disk space for a second full copy is checked first. The original in Outlook Data Files (.pst) stays untouched until the copy in Microsoft SQL Server has been checked.
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 Microsoft SQL Server
There are two ways to put a retired system into SQL Server, and they suit different firms. The old system’s own database can be restored as it is. Or the data can be loaded into a new set of tables designed to be read by people. The first is quicker and harder to use. Which suits is worked out in the analysis, and the choice is the firm’s.
Restored copy or rebuilt schema
Where the old practice system already kept its data in SQL Server, a backup can be restored onto a new server. The tables keep the vendor’s names and codes, which can be cryptic, and reading them takes someone who knows that product’s database. A rebuilt schema uses plain names such as Matter and TrustTransaction.
No screens come with it
A database has no matter screen. Someone has to ask it questions in SQL or through a reporting tool. Saved views can be set up for the things the firm will really look up: a matter with its parties, its ledger, its time entries and its list of documents. Which are worth having is agreed in the analysis.
Documents sit beside the database
Files are normally kept in folders on the same server, with a table recording each document’s matter, title, dates and path. Storing the files inside the database is possible but makes it far larger. On the Express edition, the cap on database size rules that out for most firms’ document stores.
The edition follows the size
A firm’s tables may fit within the Express limit once documents are kept outside the database. A long trust and time history at a larger firm may not. The size of the source data is measured in the analysis, and the edition is chosen from that figure with the firm’s IT provider.
Backups and a test restore
An archive that is never backed up is one disk failure from gone. Backups belong to the firm’s IT provider: a full one once the load is finished, and a schedule if anything is still being added. It is worth restoring one to a second machine as a test, because a backup that has never been restored is only a hope.
How NewLaw runs it
Four steps, in this order.
This route produces an archive, not a working system, so the steps are about completeness and proof.
Analysis
We read what Outlook Data Files (.pst) hold, table by table, and agree with you what the copy in Microsoft SQL Server must be able to answer later. Everything Outlook Data Files (.pst) hold is in scope unless you take it out.
Clean-up, if you want it
An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.
Trial export
The data is written to Microsoft SQL Server as a trial and checked against Outlook Data Files (.pst): record counts, totals where Outlook Data Files (.pst) hold money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.
Final export
After the last day of work in Outlook Data Files (.pst), the export is run a final time and checked again. There is nothing to go live. Outlook Data Files (.pst) are kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.
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 Microsoft SQL Server. 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
Structure, permissions and handover
Microsoft SQL Server is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.
Standing up SQL Server as an archive is IT work shared with the firm’s provider. A server or instance is chosen, logins are created for the few people who need to read the data, and nobody is given rights to change it. Views and a handful of reports are built for the common questions, and the IT provider owns the backup routine.
What is agreed and set up
- Server, instance and edition agreed with the IT provider
- Read-only logins and roles for named staff
- Views for matter, ledger, time and document look-ups
- Backup schedule and who tests a restore
- Plain names and descriptions for tables and columns
- Excel or Power BI connected for reporting
Questions
Outlook Data Files (.pst) to Microsoft SQL Server: 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.
Does the copy in Microsoft SQL Server hold documents from Outlook Data Files (.pst)?
In part. As files in folders with an index table; storing files in the database is possible. What Microsoft SQL Server can hold is written out once its mapping is agreed, and the rest is kept beside the data as files that open without Outlook Data Files (.pst).
Does everything in Outlook Data Files (.pst) have a place in Microsoft SQL Server?
On paper, yes: each kind of record Outlook Data Files (.pst) hold has a place in Microsoft SQL Server. 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) are written out to Microsoft SQL Server?
Documents, emails and custom fields are exported with mapping, so each mapping is agreed with you first. The firm also decides who may open the archive and how long it is kept.
Other routes
Other routes from Outlook Data Files (.pst) and into Microsoft SQL Server
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 Microsoft SQL Server are the names and marks of their owners, used here only to identify the two systems.
Moving from Outlook Data Files (.pst) to Microsoft SQL Server?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.