Email archive vs backup: which one lets a client inventory years of email?

Archives and backups do different jobs

An email archive exists to keep and find mail; a backup exists to restore it. A journaling archive captures a copy of each message as it is sent or received, indexes it and holds it under a retention policy, so a message survives even when the user deletes it. A backup takes snapshots of mailboxes on a schedule, keeps a set number of restore points and then rolls older ones off.

For an MSP, the difference decides a practical question that clients rarely ask until it matters: can this company show years of complete email history, or only what happened to be in mailboxes on the nights the backup ran?

Microsoft 365 tenants add a third pattern. Retention policies and litigation hold, configured in Microsoft Purview, keep content in place inside the tenant rather than in a separate archive. Configured well, that behaves more like an archive than a backup; configured loosely, it covers only some mailboxes or expires on a schedule nobody remembers setting.

How to tell them apart in a client tenant

How far back email history usually goes, and what breaks it

The start date of journaling or the retention policy sets the floor, but several events quietly cut history short:

• Platform migrations. Moving from on-premises Exchange or Google Workspace to Microsoft 365, or between tenants after an acquisition, often brings only recent mail across.
• Archive vendor changes. Switching archiving providers without migrating the old journal leaves earlier years in a contract that eventually lapses.
• License reclaim. Removing a departed user's license can delete the mailbox unless an inactive-mailbox hold or archive covers it.
• Retention policies set to delete. A policy written to cut storage costs may purge mail older than a fixed age across the whole tenant.
• PST sprawl. Years of mail exported to PST files on file shares or laptops exist, but outside any index or policy.

A client whose journal began a decade ago and survived two migrations has a very different record from one whose history starts at the last tenant move.

What makes years of email valuable

Email is where much of a company's decision-making is written down: pricing exceptions, customer escalations, vendor negotiations, project approvals and the reasons behind them. AI developers training agents to handle real business work need exactly those threads, in context, with outcomes. Email becomes far more useful when it links to other systems, such as the CRM opportunity it moved, the support ticket it resolved or the statement of work it negotiated.

Insurance clients are a good example: much of an underwriter's reasoning travels by email alongside the formal file, which is why underwriting notes and the surrounding mail are often inventoried together.

Export and retention realities

Exports from archives are generally possible but rarely instant. They can be throttled, charged by volume or delivered in a vendor-specific format, so read the archive contract's exit and export terms and the vendor's current documentation rather than assuming. For an inventory, no export is needed at all: message counts, date ranges, mailbox counts and policy settings are enough.

Rights and privacy come next. Whether work email is company property depends on employment policies and contracts, which the page on whether work emails are company property covers. Mailboxes also hold personal messages, client confidential information and third parties' personal data. Where correspondents are in the EU, the GDPR can apply even to a US company that offers services to or monitors people there. Data ownership can also be split in other ways, as with franchise systems where the franchisor may host the domain. De-identification and redaction requirements are agreed with the company before any work begins.

This is general information, not legal, tax or financial advice. Confirm with the client's own counsel before changing retention or export settings.

How an MSP spots a client with a strong email record

• Journaling or a tenant-wide retention policy has been running for several years without a gap
• Inactive mailboxes of former employees are retained, not deleted on license reclaim
• Earlier platforms were migrated into the archive rather than abandoned
• The archive contract is current and someone knows its export terms
• Headcount reached 50+ full-time employees at peak (contractors excluded), with a multi-year operating history
• Email sits alongside other systems with history, such as a CRM, ticketing tool and shared drives
• An owner or executive could authorize a license and the company created the mail itself, not on behalf of clients

A client that ticks most boxes is worth a conversation. The enterprise email archive introduction checklist goes deeper on this record type.

Pitfalls MSPs see

• Treating a backup product as the archive, then discovering at an inventory that only recent months are complete.
• Letting an archive subscription lapse during a cost review, which can end access to the oldest years.
• Migrating tenants and leaving the old journal in a vendor nobody pays anymore.
• Running retention policies that delete, configured years ago for storage reasons and never revisited.
• Exporting mail for anyone outside the company before an agreement exists. A partner never exports, uploads or describes client records.

When to raise it with the client

Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company, paid only after the buyer pays and SourceX receives its fee. No reward is guaranteed. The page for managed service providers covers client consent and MSP agreements in more detail.

Next step

Check one client's journal start date and inactive-mailbox settings this week. If the history runs deep, register as a partner and add the client through the referral form, or send the owner your referral link to sourcex.si/apply.