Moving every message at once makes small problems harder to spot: a folder may be skipped, dates may look different, or an attachment may not come through as expected. A limited test gives you a chance to compare the source and destination while the scope is still manageable. Choose a sample that reflects how you actually use email—not just a handful of recent messages—and agree in advance on what “worked” means. Then check the results before deciding whether to continue, adjust the method, or pause for help.
The useful bits
- Choose samples that cover different folders, message ages, formats, and attachment types.
- Record what you expect before transferring, then compare the destination against that record.
- Resolve unexplained gaps or duplicates before moving a larger set.
Set a boundary for the test
Decide which account, date range, or selected folders will form the trial. Keep the boundary clear enough that you can tell which messages belong in the test and which do not. If you are moving a shared or work mailbox, coordinate with the people responsible for it before changing settings or starting a transfer.
Use a copy or selection process that leaves the source intact, if your provider and migration method allow it. Do not assume every transfer method preserves the original or supports a reversible test. If you cannot tell whether the method will alter source mail, stop and check its documentation or ask the provider before proceeding.
Pick a sample that represents real use
A test made only of recent inbox messages can miss the cases that tend to reveal mismatches. Include a few messages from the inbox and from folders you rely on, such as sent mail, archive, or a project folder. If you use nested folders, include one of those too. Choose messages from different periods and include both read and unread items.
Cover different message shapes: a plain reply, a long conversation, a message with a visible sender name, and one with an attachment you can safely verify. If folder names contain punctuation or non-English characters, include one. Avoid using sensitive messages unless necessary; a representative sample does not need to expose more private information than the migration requires.
Test set: Inbox—recent reply and unread message; Sent—message with recipients; Archive—older conversation; Project/Notes—message with an attachment; one folder with punctuation in its name.
Write down what should arrive
Before transferring, make a compact inventory: folder name, approximate message count for the selected sample, and a few identifying details for messages you will inspect. Useful details include the subject, sender, date, read state, and whether an attachment is present. Do not rely on subject alone; conversations can contain several messages with similar subjects.
Also decide what counts as a mismatch. For example, you might require that each selected folder appears, chosen messages can be found, attachments open, and dates and sender details are sensible. Exact counts may vary if the transfer method handles duplicates, conversations, or excluded items differently, so record the method’s stated limits rather than treating every count difference as proof of failure.
Run only the limited transfer
Follow the instructions for the migration method you have chosen and keep its scope to the sample. Do not expand the selection midway just because the initial transfer seems quick. If the method reports skipped, failed, or unsupported items, save those details for review instead of dismissing them.
If you connect a mail app to BITTU Mail using IMAP, the published incoming settings are mx1.bittuicloud.com on port 993 with SSL/TLS. Never accept a certificate warning. For sending through that app, use the same host on port 465 with SSL/TLS or port 587 with STARTTLS, authentication, and the full mailbox address as the username. Do not use port 25. These connection settings do not, by themselves, guarantee that a particular migration tool can copy folders or preserve every message property.
Compare the destination carefully
Check each selected folder in the destination and search for the messages in your inventory. Open a sample rather than relying only on a folder count. Compare sender and recipient details, dates, conversation contents, read state, and attachment names. Open an attachment only if it is safe and appropriate to do so; a successful transfer is not a guarantee that an attachment is safe.
Look for duplicate messages, missing folders, unexpected folder placement, altered display names, or dates that appear shifted. Check a sent message in the destination’s sent area if your method is supposed to preserve that placement. A message appearing in search is useful evidence, but it does not confirm that every folder or property transferred correctly.
Decide whether to continue
If the sample matches your expectations, save the inventory and the migration settings so you can repeat the same approach. Move the remaining mail in manageable groups if the tool permits, checking its status and reviewing results between groups. A successful small test reduces uncertainty; it cannot guarantee that a larger transfer will have no new issues.
If something is missing or changed, pause. Confirm that the message was included in the selection, check the migration method’s exclusions and folder-mapping rules, and repeat a narrower test after correcting the cause. Keep the source available until you have reviewed the broader move and are confident that important mail is present in the destination.
- Before scaling up: folders checked; sampled messages found; dates and sender details reviewed; attachments accounted for; errors and duplicates understood.
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