Skip to content

New: How We Design Technology - our seven-layer architecture model, explained in full. See the architecture

general

Email Retention Policy: What Small Firms Should Keep and Delete

11/15/2026

A former client's attorney sends a letter asking your firm to preserve every communication about a project that wrapped up four years ago. You start looking. Some of the project lead's email sits in his old mailbox, which became a shared mailbox when he left. Some is in a PST file on a laptop in the supply closet. And some is gone, removed by a cleanup rule someone set up years ago to save storage.

An email retention policy answers that kind of request before it arrives. It says what the firm keeps, for how long, who decided, and when things get deleted. The policy only works if the system enforces it, because people's memories and inbox habits won't hold up when a client, auditor, or court asks for records.

At a glance

  • Retention periods come from legal, regulatory, contractual, and business needs. Counsel and the owners of each record type set them, and IT puts them into practice.
  • A good policy covers deletion as well as keeping. Holding everything forever adds cost, review time, and exposure.
  • Microsoft 365 can enforce retention automatically, including for shared mailboxes and departed employees, for the content it holds.

Why "keep everything" and "delete when full" both fail

Many small firms land in one of two habits. The first is keeping everything. It feels safe, but every extra year of email adds to what has to be searched and reviewed in a dispute, and to what's exposed if an account is compromised. The FTC's guide to protecting personal information advises businesses to keep only what they need, for only as long as it's necessary, and to dispose of the rest properly.

The second habit is deleting by convenience: auto-cleanup rules, mailboxes removed when someone leaves, and staff who empty folders to stay under a quota. That approach works until a client asks for the correspondence behind a deliverable, or an auditor asks for approvals from three years back.

A written policy replaces both habits with decisions. The FTC recommends a written records retention policy that identifies what has to be kept and how it's secured, and that works for a 25-person firm as well as a large company.

Who decides how long

IT can tell you what Microsoft 365 is able to keep and delete. The periods themselves belong to your attorney, your accountant, and the leaders who own each kind of record. Common drivers include:

  • Tax and financial rules. The IRS ties record keeping to the period during which a return can be examined. Three years is the general rule, employment tax records should be kept at least four years, and some situations call for longer. The IRS also notes that insurers or creditors may require you to keep records longer than it does.
  • Client contracts. Engagement letters and service agreements may set retention periods, or require you to return or destroy client data when the work ends.
  • Professional standards. Accounting, legal, engineering, and design firms often answer to licensing boards or professional bodies with their own record expectations.
  • Business value. Proposals, project histories, and warranty-period correspondence can matter long after any legal requirement ends.

Collect those requirements, write down where each one came from, and let the longest applicable period drive each category. A list of years copied from someone else's firm can be wrong for yours in either direction.

Build your email retention policy around record types

Retention gets simpler when you stop thinking about "email" as one thing. Group messages and files by what they are, then assign a period and an owner to each group.

  • Client engagement records
    • Examples: Engagement letters, deliverables, key project decisions
    • Who sets the period: Partners and counsel, guided by contracts and professional rules
    • How it's enforced: Retention labels on client folders, or a policy on project mailboxes and sites
  • Financial and tax
    • Examples: Invoices, payment approvals, payroll messages
    • Who sets the period: Controller and outside accountant, guided by IRS rules
    • How it's enforced: Retention policy on finance mailboxes and sites
  • Personnel
    • Examples: Offer letters, benefits, employee matters
    • Who sets the period: HR and employment counsel
    • How it's enforced: Labels applied to HR content
  • Routine correspondence
    • Examples: Scheduling, vendor updates, internal notices
    • Who sets the period: Operations leadership
    • How it's enforced: A default policy that deletes after a set period
  • Legal matters
    • Examples: Anything relevant to a dispute or claim
    • Who sets the period: Counsel
    • How it's enforced: A legal hold that pauses deletion until released

Most firms need only a handful of categories. A short policy people understand will be followed more closely than a long one nobody reads.

How Microsoft 365 enforces it

Microsoft Purview gives you two tools. A retention policy applies the same settings across a location, such as every mailbox or a group of SharePoint sites. A retention label applies settings to individual items like an email, document, or folder, and the label travels with the content if it moves elsewhere in your tenant. Labels can also start the clock from an event, such as the end of an engagement, and can route items to a person for review before deletion. You can use both together.

Each setting can keep content for a period, delete it after a period, or keep it and then delete it. When settings conflict, Microsoft applies clear rules: retention takes precedence over permanent deletion, and the longest retention period wins. That protects you from a cleanup policy quietly removing something another policy is meant to keep.

A few details matter for email. Retention policies for Exchange cover mail in user mailboxes and shared mailboxes, along with calendar items that have an end date. Contacts aren't covered. Teams chats are stored separately and need their own retention policies. Which retention features you can use depends on your Microsoft 365 subscription, so check the licensing requirements before you design around a specific capability.

Departed employees and shared mailboxes

Departures are where small firms lose the most email. Converting a former employee's mailbox to a shared mailbox is a common shortcut, and retention policies do apply to shared mailboxes. Decide deliberately how long those converted mailboxes stay and who can open them.

Microsoft also offers inactive mailboxes. If a mailbox is covered by a retention policy or hold when the user's account is deleted, it becomes an inactive mailbox. Its contents stay subject to that retention and remain available to eDiscovery searches, and the Exchange Online license goes back into your pool. The retention policy or hold has to be in place before the account is deleted, so build this into your offboarding steps rather than discovering it afterward.

Legal holds pause the schedule

When a dispute or investigation is reasonably anticipated, counsel may instruct the firm to preserve relevant records. At that point, normal deletion stops for the people and content involved. In Microsoft 365, a hold keeps content even if a retention policy would otherwise delete it, and the hold stays in place until counsel releases it.

Make sure your process reaches beyond the hold itself. Pause offboarding deletions for anyone involved, and tell the right people not to clean up their mailboxes or folders. Write down when the hold started, what it covers, and who approved its release.

PSTs, personal email, and other places email hides

Retention policies govern content inside Microsoft 365. A PST file on a laptop or external drive sits outside them, and so does a copy of client email forwarded to someone's personal account. Those copies can't be found by a retention search, won't be deleted on schedule, and are easy to lose.

Find existing PST files and either bring the content into Microsoft 365 or dispose of it under the policy. Ask staff to stop creating new ones. Turn off automatic forwarding to outside addresses, and make clear that client work stays in firm accounts.

Write it down and revisit it

Your written policy can be short. Cover the record categories, the period and owner for each, how Microsoft 365 enforces it, how legal holds work, and what happens to a mailbox when someone leaves. Add a review date and revisit it when contracts, services, or regulations change.

Then confirm the system matches the paper. Run a test search, check that departed employees' mail is where the policy says it should be, and make sure every policy in Purview traces back to a documented decision.

At CTP, we help small and mid-size firms turn retention decisions into Microsoft 365 settings they can explain to a client or auditor, with each choice written down. Learn more about our collaboration work for small and mid-size businesses, or schedule a conversation about what your firm keeps today.

Sources and further reading

Ask about something important for you.

Curious about our take on an industry or technology topic? Let us know.

Contact Us