Moving mail does not have to mean removing it from the account where it lives. A safer approach is to copy a small, clearly defined group first, confirm that the destination contains the expected messages and usable attachments, and keep the source intact until those checks pass. This guide explains how to prepare, copy, verify, and only then consider cleanup. The exact labels and steps vary between mail apps, so use your app’s copy or move controls carefully and check what action they will perform before you confirm.
The useful bits
- Copy selected messages first; do not delete or move the source during the initial transfer.
- Compare the expected and received message counts, then open messages and attachments at the destination.
- Keep the source copy until you have confirmed the transfer and know how you can recover from an error.
Decide exactly what belongs in the transfer
Start with a defined scope rather than selecting everything at once. You might choose a project folder, a date range, or a set of messages from a particular sender. Record the source folder and the number of messages you intend to copy. If your selection includes several folders, note each folder separately so you can check them independently.
Check whether the destination already contains some of the same mail. Duplicate messages can make a total count misleading, and two apps may group or display folders differently. Decide where the copied messages should go before starting. If preserving folder organization matters, plan a matching destination folder where your mail app allows it.
Prepare both accounts without risking the source
Make sure you can sign in to both accounts and identify which one is the source and which is the destination. In the mail app, check the account names before acting; similar display names can make it easy to copy in the wrong direction. Do not share passwords or one-time codes with anyone while setting up access.
If you use a mail app with IMAP, BITTU Mail’s published incoming server is mx1.bittuicloud.com on port 993 with SSL/TLS. Its outgoing server uses the same host on port 465 with SSL/TLS or port 587 with STARTTLS, with authentication and the full mailbox address as the username. Never use port 25 for a mail app, and do not accept a certificate warning. Settings and availability may depend on the account and app.
Copy a small batch and leave the original alone
Choose a small, recognizable batch first. Use the mail app’s copy operation if available, and confirm that it says copy rather than move. A move may remove the message from its source folder after transferring it; that is not the safe first step. App behavior varies, so pause at any confirmation screen and read the wording.
Wait for the app to finish synchronizing before judging the result. Avoid repeating the copy immediately if messages do not appear: the app may still be working, or the destination folder may not be the one you expected. Check the destination account and folder directly.
Example: copy the messages in a source folder called “Project notes” to a destination folder you create for the same purpose. If the source selection contains 12 messages, write down 12 as the expected count. The number is just an example; use the count for your own selection.
Verify the copy, not just the folder name
Compare the destination count with your recorded source count for the same selection. If they differ, do not clean up the source. Check whether the app is still synchronizing, whether you copied only a subset, and whether duplicates or existing destination messages affect the count. Counts are a useful check, not proof that every message is complete.
Open several copied messages at the destination, including the oldest and newest in the batch if those are relevant. Confirm that the sender, recipient, date, subject, and message body look right. Open attachments that matter and confirm they load and can be read. A paperclip icon or attachment filename alone does not establish that the file opens correctly.
Use a deliberate check before expanding the transfer
If the first batch passes, repeat the same copy-and-check process for the remaining selections. Keep a brief record of which folders or groups are done and which still need review. If a count is short, an attachment will not open, or a message body looks incomplete, stop and investigate that specific batch before proceeding.
For especially important mail, consider preserving a separate backup using a method supported by your mail app or organization. Do not assume that a successful copy is an independent backup, or that every provider offers the same recovery options.
- Source folder and expected message count recorded.
- Destination account and folder confirmed.
- Received count compared with the intended selection.
- Representative messages opened; important attachments opened.
- Source messages remain available until all checks pass.
Clean up only after you are satisfied
Once you have checked the destination, decide whether you still need the source copy. Keeping both copies may be the simplest choice. If you choose to remove source messages, do so only after confirming the destination selection and understanding how deletion works in your app; deletion and synchronization behavior can vary.
If anything is uncertain, leave the source intact and ask the relevant mail provider or workspace administrator for help. A cautious transfer is complete when the intended messages are present at the destination, important content and attachments open there, and you have made an informed decision about the originals—not merely when a progress indicator disappears.
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