Verify Mailbox Integrity After Office 365 Migration

Completing an Office 365 migration is only one part of the project. Before users fully transition to the destination environment or the source is retired, administrators should review the migrated mailbox content, folder structure, supported mailbox items, access, and migration reports for unexpected differences.

Mailbox integrity verification focuses specifically on whether the selected mailbox data arrived in the destination as expected. It is different from broader post-migration validation, which may also include DNS, mail flow, Autodiscover, devices, and organization-wide cutover checks.

EdbMails Office 365 Migration Tool provides migration reports and repeat migration support that administrators can use alongside source-versus-destination checks to review mailbox-level results.

What Does Mailbox Integrity Mean?

Mailbox integrity means that the data selected for migration can be accounted for in the destination and remains usable in the expected structure. Verification should consider the migration scope, filters, supported item types, report results, and any changes made to the source while migration was in progress.

A practical integrity review normally checks:

• Expected mailbox folders and subfolders are present in the destination.
• Representative email messages and attachments open correctly.
• Calendar items, contacts, and other selected supported mailbox items are available.
• User-created folder hierarchy appears as expected.
• Skipped, failed, or excluded items shown in migration reports are understood and reviewed.
• Mailbox access and applicable permissions are tested separately where required.

Understand Expected Differences After Migration

Source and destination totals do not always have to be identical for a migration to be valid. Differences can occur because of the migration scope, date or folder filters, excluded folders, unsupported items, source mailbox activity during the migration window, or items reported as skipped or failed.

Mailbox size alone should not be used as the only integrity measure. Instead, compare the selected migration scope with EdbMails reports and perform targeted checks in both source and destination mailboxes. Any unexplained difference should be investigated before final sign-off.

Mailbox Integrity Validation Workflow

1. Review migration reports: Check mailbox-level status, migrated item results, warnings, errors, skipped items, and excluded folders.
2. Compare source and destination: Review expected folders and item counts where those values are available and relevant to the selected migration scope.
3. Inspect representative items: Open recent and older messages, attachments, calendar entries, and contacts from representative mailboxes.
4. Validate folder hierarchy: Confirm that user-created folders and nested folders appear in the expected locations.
5. Check access and permissions: Test mailbox access and verify applicable delegated or folder permissions separately.
6. Run a final incremental pass: Process new or changed source items before cutover when the project requires a repeat migration.
7. Record exceptions and sign-off: Document unresolved differences, accepted exclusions, and the validation result before retiring the source environment.

Using EdbMails Reports for Mailbox Integrity Verification

Office 365 migration reports provide a starting point for mailbox-integrity checks. Review the report information available for each migration job, including migration status, migrated item counts, excluded folders, timestamps, mailbox-level results, warnings, and errors.

Where multiple migration passes are used, cumulative and mailbox-level results can help administrators identify items that require another review. Reports should be read together with the configured migration scope because a successful status does not by itself confirm that every source item was selected for migration.

Compare Source and Destination Mailbox Results

Use a combination of report data and targeted mailbox checks rather than relying on a single number.

Validate Permissions and Mailbox Access Separately

Mailbox content integrity and mailbox permissions are related but should be verified as separate checks. If permissions are part of the migration scope, confirm the applicable Full Access, Send As, Send on Behalf, calendar, folder, or shared mailbox access after the content validation is complete.

For detailed checks, use the Office 365 mailbox permission validation guide. If a folder-level permission does not behave as expected, review the folder permission migration troubleshooting guidance rather than treating the issue as a mailbox-content failure.

Run a Final Incremental Migration When Required

Mailbox content can continue changing after the first migration pass. For projects that use repeat migrations, EdbMails can process new or changed items based on migration metadata retained from the previous run. Previously processed items are normally skipped when the same source, target, mapping, project information, and migration metadata are retained.

For the expected incremental behavior, repeat the migration from the same computer used for the earlier pass unless the project has been moved using the supported migration-metadata transfer process. Review the new report after the final pass and investigate any remaining warnings or failed items before cutover.

When Is Mailbox Integrity Verification Complete?

Before approving the mailbox-content portion of the migration, confirm that:

• The selected mailboxes and intended migration scope have been reviewed.
• Expected folders and representative mailbox items are present and accessible.
• Migration report warnings, skipped items, and failures have been investigated.
• Expected differences caused by filters, exclusions, or unsupported items are documented.
• Applicable mailbox and folder permissions have been checked separately.
• The final incremental migration, when required, has been completed and its report reviewed.
• Any remaining exceptions are recorded before migration sign-off.

Best Practices for Mailbox Integrity Verification

• Validate representative pilot mailboxes before applying the same acceptance process to a larger batch.
• Review migration reports after every migration pass rather than waiting until the final cutover.
• Use source-versus-destination checks for representative mailboxes and folders.
• Do not use mailbox size alone as proof that mailbox content is complete.
• Keep filters, exclusions, and mapping decisions documented so expected differences are easy to explain.
• Retain migration reports and validation records according to your organization's operational or compliance requirements.

Conclusion

Mailbox integrity verification should establish whether the mailbox data selected for migration can be accounted for in the destination and whether reported exceptions have been reviewed. Combining migration reports with targeted source-versus-destination checks, permission validation, and a final incremental pass where required gives administrators a more reliable basis for migration sign-off.

For broader post-migration checks such as mail flow, DNS, Autodiscover, and organization-wide cutover validation, use the dedicated Office 365 migration validation guidance rather than expanding mailbox-integrity checks beyond their intended scope.

---

Additional resources:

• Validate Office 365 mailbox migration
• Validate mailbox permissions after migration
• Troubleshoot folder permission migration
• office 365 archive mailbox to exchange guide
• office 365 public folder migration to office 365 guide
• Office 365 migration software