A mail export can contain every message and still lose the structure that made the mailbox usable. Folder names may be flattened, nested paths may be rewritten, or empty folders may not appear at all. Before transferring a whole mailbox, make a simple record of its folder tree, inspect a small export, and import a representative sample into the destination. This gives you a chance to spot mismatches while the transfer is still small—and to check that the destination’s folders and messages match your expectations before continuing.
The useful bits
- Write down folder names and parent-child relationships before exporting.
- Inspect the export’s file names and structure; do not infer hierarchy from message counts alone.
- Import a small, representative sample and verify nested paths before moving the full mailbox.
Record the tree before changing anything
Start with a folder inventory while you can still see the original mailbox. Write each folder on its own line using a consistent separator, such as a forward slash, to show its parent. Record subfolders even when they currently contain few or no messages; they may still matter to your filing system.
Include the account or mailbox being transferred, and note any folders that are easy to confuse, such as two subfolders with the same name under different parents. If the mail service offers an export option, check whether it includes all folders or only selected ones. The exact controls depend on the service and account. Do not assume that a folder visible in the mailbox will be included automatically.
Mailbox: alex@example.com Inbox Projects Projects/Orchid Projects/Orchid/Invoices Projects/Willow Personal/Travel Archive/2023
Inspect the export before importing
An export’s format determines what evidence you can use to check its folder structure. Read the export tool’s description and inspect the downloaded files using a file viewer or archive utility. Look for folder names, nested directory paths, an index or manifest, and a clear association between messages and folders. A file named after a folder is not, by itself, proof that its parent-child relationship was preserved.
Formats vary: one export may represent folders as directories, while another may store messages and folder information in a container or index. Check the destination’s import instructions to confirm that it accepts the format and explains how it interprets folder paths. If the export contains only message files without usable folder information, plan to recreate folders separately if the destination allows it. Do not rename or reorganize the original export until you have a separate working copy.
- Can you identify each expected folder in the export?
- Are nested paths distinct from similarly named folders elsewhere?
- Does the destination say how it maps those paths during import?
Choose a useful small sample
A good trial is small enough to review, but varied enough to reveal mapping problems. Include at least one parent folder with a nested folder, a second branch with a similarly named folder if you have one, and messages that are easy to recognize. If empty folders are important, check whether the export or import process supports them; a message-based sample cannot prove that empty folders survive.
Keep a short sample record: the source path, the messages selected, and any expected subfolder. Avoid using sensitive mail if a non-sensitive representative sample will answer the same structural question. If you need to use real mailbox content, handle the export and destination according to your own organization’s access and retention practices.
Sample to transfer: Projects/Orchid — one identifiable message Projects/Orchid/Invoices — one identifiable message Projects/Willow — one identifiable message Expected destination paths: unchanged from the source
Import the sample and compare paths
Import the sample using the destination’s documented procedure. Folder and import controls differ between services, and availability can depend on role, plan, and account provisioning. If you are using BITTU Mail, its mail features include folders, but do not assume a particular import method or control is available for every account; confirm the supported process for your account before proceeding.
After import, compare the destination tree line by line with your source inventory. Open each sample folder and confirm that its recognizable message appears there, rather than only in the inbox, a parent folder, or a flattened folder with a combined name. Check that similarly named folders remain under the correct parents. If a folder is missing or a message landed elsewhere, pause. Adjust the import mapping or recreate the needed folders using the destination’s available controls, then repeat the sample before importing more.
- Confirm the parent folder exists.
- Confirm each nested folder appears beneath the intended parent.
- Confirm each sample message is in its expected folder, not merely searchable somewhere in the mailbox.
Verify the full transfer in manageable passes
Once the sample matches, transfer the remaining folders in batches that are practical for your tools and review time. Keep the source inventory and export intact until you have checked the result. After each pass, mark which paths were imported and look for unexpected duplicates, missing branches, or messages grouped into the wrong location.
Message counts can help flag a discrepancy, but they do not prove that hierarchy is correct: two folders can have the same total while containing different messages. Use folder paths and a few recognizable messages as the main checks. Search can help locate a message that seems missing, but finding it does not confirm it is filed in the right folder.
Completion check: [ ] Every recorded path has a matching destination folder [ ] Nested folders sit beneath the intended parents [ ] Sample messages and selected spot-check messages are filed correctly [ ] Any intentionally omitted or empty folders are noted
Keep a record of exceptions
Some transfers cannot reproduce the source exactly. A tool may omit empty folders, normalize folder names, or apply its own rules to separators. Record any differences you accept, and keep the source tree and export until you are satisfied that the destination is usable. If a mismatch remains, consult the export or import provider’s documentation rather than guessing at a file-format conversion.
A short inventory, a checked sample, and a final path review turn a potentially confusing migration into a sequence of verifiable steps. The key confirmation is not simply that messages arrived: it is that the destination’s nested folder tree matches the structure you meant to preserve.
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