Skip to content

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

general

Moving Lab Email to Microsoft 365? Plan Records Retention First

11/10/2026

The migration plan has a cutover date, a pilot group, and a quote for the mailbox moves. What it doesn't have yet is an answer to the question the records officer raised at kickoff: when someone requests a toxicologist's email from four years ago, where will it be, and who decided how long it stays?

Lab email is usually an agency record, and government email retention rules apply to it whether it sits on an aging Exchange server or in Microsoft 365. A migration is the best chance you'll get to set those rules deliberately. Configure retention after the move and you risk losing messages you were required to keep, or keeping messages long past the date your schedule says they should go.

At a glance

  • Agree on what you keep and for how long with your records officer and counsel before a single mailbox moves.
  • Build Microsoft Purview retention policies and labels in the new tenant first, then test that they apply to migrated mail.
  • Decide what happens to PST files, old archives, and active holds, and write each decision down.

Lab email is usually a public record

Messages between analysts, investigators, prosecutors, and defense counsel often document how a case was handled. Many state records laws treat that correspondence as an agency record, and your state archives or records office publishes retention schedules that say how long each type must be kept. Your agency may add its own policy on top.

The same email can surface through more than one door. Discovery requests, subpoenas, public records requests, and accreditation reviews all ask for messages, sometimes years after a case closes. Some messages must be kept for a set period. Others should be deleted once that period ends, so the lab doesn't hold and produce more than the schedule requires. Your records officer and counsel decide which schedules apply. The migration team's job is to make the system carry out those decisions.

Government email retention starts with decisions

Before anyone opens the Purview portal, sit down with the records officer, counsel, the quality manager, and lab leadership, and work through the main categories of mail. You don't need a perfect taxonomy. You need a short list people can follow and a system can enforce.

  • Casework correspondence
    • Typical owner: Section supervisors
    • Retention decision: Period set by the applicable schedule, often tied to case closure
    • How it's enforced: Retention label applied by users or automatically
  • Quality and accreditation records
    • Typical owner: Quality manager
    • Retention decision: Period required by your quality system and accrediting body
    • How it's enforced: Label on a shared mailbox or Teams site
  • Administrative and personnel mail
    • Typical owner: Lab administration and HR
    • Retention decision: Agency schedule for administrative records
    • How it's enforced: Retention policy on the relevant mailboxes
  • Vendor and instrument support
    • Typical owner: Evidence and LIMS administrator
    • Retention decision: Life of the instrument plus a set period
    • How it's enforced: Label or policy on a support mailbox
  • Routine and transitory messages
    • Typical owner: Each user
    • Retention decision: Shortest period the schedule allows
    • How it's enforced: Default retention policy for all mailboxes

Write the periods into the table from your actual schedules. The point is a shared decision that the technology then follows.

Retention policies and labels do different jobs

Microsoft Purview gives you two tools. Retention policies apply the same settings to whole locations, such as every mailbox in the lab. Retention labels apply to individual items, so one email about an active case can be kept longer than the routine mail around it. Labels can be applied by users, set as defaults, or applied automatically (depending on licensing), and they follow an item if it moves within the tenant.

Both can retain content, delete it, or retain and then delete it. Microsoft's rules for conflicts are worth knowing before you design anything: retention wins over deletion, the longest retention period wins, and eDiscovery holds take precedence over both. Labels also support disposition review, so a person can approve the deletion of sensitive records instead of letting them expire quietly.

Most labs end up with a baseline policy for all mailboxes plus a few labels for records that need special handling. Keep the label list short. Staff will use three well-named labels and ignore fifteen.

Holds and departing staff

Some mail will already be under a legal hold when the migration starts. Bring those mailboxes to counsel before they move, confirm how the hold will be preserved in the new tenant, and keep the old copy intact until counsel agrees the new one is in place.

Departing staff need a plan too. When an analyst leaves, their mailbox may still hold records the schedule requires you to keep. Microsoft 365 can convert a deleted user's mailbox into an inactive mailbox that keeps its content, but only if a retention policy or label that retains content is applied before the account is deleted. Microsoft recommends using Microsoft 365 retention for this and describes Litigation Hold as the older approach. Build the step into your offboarding so it happens every time.

PST files, archives, and the old system

The mail on the server is only part of the record. Many labs also have PST files on file shares and laptops, a separate email archive fed by journaling, and old mailboxes kept for staff who left years ago. Each needs a decision before cutover.

PST files. Microsoft's import service preserves the original sent and received dates, so retention settings that count from those dates treat a ten-year-old message as ten years old. A policy that deletes mail after a set number of years can remove older imported messages soon after they arrive. Set and test retention before you import anything.

Journaling archives. If a third-party archive has captured mail for years, decide whether to migrate its contents into Microsoft 365 or keep it read-only until its records reach the end of their retention periods. Either can work. Someone has to own the old system until it is retired.

Former employees. Mailboxes kept for people who left need the same treatment as current ones, and some may already be under a hold.

Keep the old system available, read-only and secured, until you've confirmed the records arrived and the policies apply to them.

Tenant type and testing

For many government agencies, the first question is which Microsoft cloud the lab belongs in. Microsoft's Government Community Cloud (GCC) serves U.S. federal, state, local, and tribal governments, with a validation process before an environment is set up. Its service description covers how GCC differs from commercial Microsoft 365, including the background screening Microsoft requires of staff who can access customer content, which adds a CJIS check in states that participate in Microsoft's CJIS program.

Settle the tenant type with your agency and your state's CJIS Systems Agency first, because moving a mailbox from one tenant type to another later is a second migration.

Then test before the bulk move. Migrate a pilot group, check that policies and labels show up on their mail, apply a label to a sample message, and run a content search the way a records request would. Confirm that an inactive mailbox is created when a test account is deleted. Fix what fails and test again.

Document the decisions

Write down each decision as you make it: the categories, the schedules they map to, who approved them, how each is enforced, what happened to PST files and archives, and how holds were carried across. Store the record with your quality documentation.

When a records request or an assessor's question arrives two years from now, that document lets someone other than the original team explain why the system keeps what it keeps. Review it whenever your schedules or your accreditation requirements change.

Settle retention while the plan is still on paper

Retention planned at the start is far easier than retention added after cutover, and it spares the lab a records problem that is hard to fix once the old server is gone. Decide what you keep, build the policies, test them on real mail, and move the mailboxes after that.

At CTP, we plan lab migrations with records, retention, and holds treated as design decisions from the first meeting. Read how we approach Microsoft 365 migration for forensic laboratories, or see our broader work with forensic and crime laboratories.

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