Ideally, finding an old client email or attachment should take a quick search, not a hunt through several folders..
However, large amounts of historical information are spread across various mailboxes, public folders, and exported files with meaningless titles. So all of this valuable data exists, but may be very difficult to locate.
And of course people receive a lot of emails. Microsoft’s June 2025 analysis of anonymised Microsoft 365 activity found that the average worker in its data received 117 emails a day.
There are some relatively straightforward measures to improve searchability of archived data though, starting with considering what information users may want to find.
What you’ll learn:
- Find Out What Is Worth Keeping
- Move Public Folders to the Right Home
- Give Old Emails Useful Labels
- Test Search With Real Questions
- Keep Access and Retention Under Control
- Make the Archive Easy to Use
- Wrapping It Up
Find Out What Is Worth Keeping
Identify all existing stores of email data. This will include any shared mailboxes, Public Folders and exported email data.
Many of these will contain valuable historical information. However others will contain large volumes of unneeded or duplicated emails, notifications, and attachments.
List all sources, identifying the owner, approximate time period, location, and reason for retaining. Also ask users what types of historical information they may want to refer back to, and what information they may know about those emails.
Categorise into broad groups, for example:
- Emails beneficial to retain in a ‘live’ mailbox
- Historical information to be retained and made easily searchable, such as closed jobs, quotes, sign-offs
- Data to be reviewed to see if subject to any retention requirements
- Duplicates and other information potentially suitable for deletion
Obviously, deletion would need sign-off from the people responsible for the records.
Move Public Folders to the Right Home
Public folders can be used to store information accessible to others, but are not recommended by Microsoft to act as an extension of users’ mailboxes. Microsoft recommends Exchange In-Place Archiving for mailbox archiving and SharePoint Online for document sharing and collaboration.
So depending on the nature of the information in each Public Folder, it may be appropriate to retain it as a ‘live’ mailbox, or move closed jobs and similar to another location, potentially next to other related documents.
If the intention is to make information available more widely, such as closed jobs, teams could migrate public folders to SharePoint. It would be beneficial to decide how best to group them, such as by client, prior to migration.
Whichever option is chosen, it’s worthwhile migrating some sample data and checking the level of detail retained. As well as the obvious content of the email and any attachments, you’ll want to retain information such as sender, all recipients, and sent and received times. It’s also a good idea to include examples with a large number of attachments or non-standard naming.
Once migrated, make sure to check individual items and confirm the number of attachments, not just rely on comparing total numbers.
Give Old Emails Useful Labels
Exported emails may have little information in their filename to indicate the contents.
As far as possible you’ll want to retain information about the original email, and additionally apply other properties. These could be anything useful to the business, for example client, job, job number, type of document. Users may want to locate an amendment agreement, and know the associated job, but not who originally emailed it to them.
Don’t create too many similar properties, as it will be easy for users to apply inconsistently. So decide on a reasonable number of options, ensure all users understand how to apply them, and aim to apply the same to any associated information.
Of course it’s also beneficial to be able to search details within the email itself. This may be particularly useful if, for example, the original sender is no longer employed by the business.
Test Search With Real Questions
One of the key benefits of migrating the data is to allow users to search.
Prior to making available to all users, compile a list of examples they may wish to search for, such as a particular quote, sign off, or attached document. Get some users to try and locate these, using various options to return relevant results, such as from, received date, any added properties, or terms within the body. And then locate the required email and open any attachment.
Be aware of the limitations of SharePoint search, and any properties that may need adding to allow a particular search. It can also take some time before recently added information returns in search results.
Some types of files may also prove more difficult to search than others, so check the relevant types.
Where searches fail to return the required result, investigate the cause and rectify before completing the remaining migration.
Keep Access and Retention Under Control
You’ll want to restrict access to certain data as appropriate.
So determine what users require access to prior to configuring permissions to each location. As with any information stored in SharePoint, users will only be able to see search results for items they have permission to access. It’s therefore important to check searches as a relevant user, rather than relying on an account with extensive access rights.
You’ll also want to consider any retention periods applicable. Existing settings may well not apply to data once moved to a new location, so discuss with relevant parties and configure accordingly. Microsoft 365 allows various options for both Exchange and SharePoint.
It would be sensible to complete this prior to deleting existing locations.
Make the Archive Easy to Use
Designate an individual or individuals responsible for each area. Ideally they would know what information is appropriate to store in each area, the properties to apply, and who to raise issues with.
Provide guidance to other users to encourage them to continue adding information appropriately. This could be as simple as showing an example of an email, including attachments and applied properties.
Decide at what point further emails should be added, and who is responsible for ensuring this is done, for example all final sign-offs when completing a job.
Periodically review the range of options available to apply, adding new ones or removing obsolete ones.
The goal is to help staff find the records they need without asking someone else where they were filed.
Wrapping It Up
An email archive becomes valuable when people can find the right record and understand why it matters.
Provided appropriate information is retained in a suitable format and location, with useful properties, and users are aware of how to effectively search, this can be a very useful repository of historical data.





