A mailbox migration can finish with different message counts on the two sides even when nothing important has gone missing. One view may include spam or deleted mail while another excludes it; a destination may also combine folders, skip duplicates, or apply filters. Comparing only the grand totals makes these differences look like failures. A more reliable check uses the same folder scope on both sides, records counts consistently, and investigates a mismatch only after you know what each count includes. This method helps you separate ordinary counting differences from signs that messages need attention.
The useful bits
- Compare matching folders and equivalent message scope, not just mailbox totals.
- Record excluded folders, duplicate handling, and filters before interpreting a difference.
- Investigate a mismatch when it remains unexplained and specific messages cannot be accounted for.
Agree on what a count means
Before comparing anything, decide whether you are counting messages in folders, conversations, or another view. These are not necessarily the same measure: a conversation view may group related messages, while a folder count may treat each message separately. Use the same type of count at the source and destination wherever possible.
Also set a common scope. Decide whether to include Inbox, Sent, Drafts, Archive, Trash, Spam, and custom folders. If one side excludes a folder, note that rather than treating its messages as missing. Take both counts after the migration activity you are checking has stopped or settled, and record when the comparison was made.
Match folders before totaling
Make a simple mapping from each source folder to its destination counterpart. Names may differ, and a migration may put messages from several source folders into one destination folder. Compare mapped folders individually; do not assume that similarly named folders contain the same set of messages.
Include nested folders in the mapping. For example, a source folder called Projects/Orion may appear under a different parent on the destination. If a folder has no counterpart, mark it as unmapped and find out whether its contents were intentionally combined, excluded, or not transferred. Only add folder counts into a mailbox total if you know the counting method does not count the same message twice across views.
Source: Inbox 120; Sent 45; Projects/Orion 18 Destination: Inbox 118; Sent 45; Projects/Orion 20 Check: compare the two Inbox messages and two project-folder messages before deciding whether the overall total is short.
Check duplicates and folder moves
A message can appear more than once in a mailbox, for example when copies were filed in different folders. Some migration processes preserve those copies; others may recognize duplicates and keep one. A folder move can also reduce one count and increase another without changing the mailbox’s overall message set.
For each discrepancy, ask whether the same message exists elsewhere on the destination and whether duplicate handling was expected. Compare recognizable message details such as sender, subject, and date, then open the message when needed. These details help locate a candidate; they are not by themselves proof that two copies are identical.
Look for filters and exclusions
A difference may come from rules or migration settings that skip, redirect, or file certain messages. Review the settings and instructions used for the migration, including any stated exclusions and duplicate policy. Check whether the source or destination view is filtered by a search, unread status, date range, or selected folder; a filtered view is not a full-folder count.
Keep intentional exclusions separate from unexplained gaps. If Spam or Trash was deliberately omitted, record its source count and the decision. If a rule sent a message to another folder, locate it there before calling it missing. Do not change filters simply to make totals match; first understand what they are doing.
Use a repeatable comparison sheet
A small table prevents memory and assumptions from driving the investigation. For every mapped folder, write down the source count, destination count, difference, and any known explanation. Use the same count definition and folder scope throughout. Mark folders that are excluded, combined, or affected by duplicate handling.
Then sample the folders with differences. Look for messages that should be present based on the migration scope and check whether they appear in another destination folder. In BITTU Mail, folders and search can help you inspect messages, but the available controls can depend on account provisioning and role; do not assume a particular migration or counting tool is built in.
- Confirm the comparison uses the same message-versus-conversation measure.
- Map every included source folder to a destination folder or document its exclusion.
- Check filters, duplicate handling, and messages filed elsewhere.
- Record the comparison time and repeat the same method after any correction.
Know when a mismatch merits attention
Investigate when a difference remains after scope, folder mapping, filters, and duplicate handling are accounted for—especially if you can identify a message that was included in the migration but cannot find it in any destination folder. Also follow up on a folder that has no documented mapping or an exclusion whose reason is unclear.
You can confirm the comparison is resolved when each included folder has either matching counts or a recorded explanation, and sampled messages with differences can be accounted for. If a message still cannot be located, keep its identifying details and the folder comparison notes, then ask the migration administrator or relevant support contact to review the specific gap. A matching grand total alone is not confirmation: one folder can be short while another contains extra or duplicated messages.
About this guide
Prepared with AI assistance for the BITTU Mail editorial library. Check important details against your original messages and current account settings. Product access depends on your role, plan and provisioning state. Provider interfaces and requirements can change.
View current plans · Security information · Suggest a correction