When most mailboxes have copied but a few have failed, keep a separate record for each address. For a small company moving twenty mailboxes, a useful result is a list of completed addresses, unresolved errors and the person checking each archive.
TrekMail supports bulk import from a CSV file for moving multiple business mailboxes. The file lists source mailboxes and their matching destinations. First create the recipients in TrekMail, check access to the old mail, and make sure there is enough storage for the archive.
Separate a row's progress from the whole project
Imagine that eighteen addresses in a twenty-mailbox move have completed their jobs and two still show errors. Keep the eighteen successful rows identifiable while you investigate the other two. “The batch failed” is too broad a description: it encourages people to repeat work without knowing which mailbox needs attention.
For each unresolved row, record the source, intended destination, visible error, and last action you took. An authentication error points you towards the source credentials and accepted login method. A capacity problem points towards the destination and account storage. A formatting issue in the uploaded file is different from either. Check the concrete error before replacing settings that worked for other people.
Group shared causes without losing the individual addresses. If several failing rows use the same source server, inspect their common connection settings. If only one account fails, compare the username and its access requirements with the working examples. The comparison is a way to focus the investigation; it does not prove that every mailbox at that provider permits the same authentication method.
Keep the successful destinations available for inspection. Their owners can check familiar folders and attachments while you resolve the remaining errors. That does not mean the whole company is ready for delivery cutover. It means the project can distinguish copied archives, archives already checked by owners, and addresses still awaiting attention. Those are useful, separate states in your own handover notes.
Build the list and check access
Prepare a source-to-destination list. Each row should make clear who owns the mailbox, where mail is copied from, and where it should go. Don't rely on similar names. A former employee and their replacement may have different addresses with the same display name.
Create destination mailboxes and estimate their size. Check both individual mailbox capacity and the account's available storage. One employee's large archive can materially change the total.
Find out which credentials the old provider accepts for a direct IMAP connection. Being able to sign in through a browser does not prove that this access works. In particular, a username-and-password import should not be assumed compatible with Microsoft 365's interactive sign-in.
Prepare the CSV and inspect the preview
A CSV is a table stored as text. Get the column layout and sample from the current bulk migration guide so source addresses and destinations are not confused.
The file contains access details for old mailboxes. Share it only with the person carrying out the move and remove the working copy when finished. Do not attach the completed file to a general project discussion.
Upload the CSV and review the preliminary checks. These can reveal formatting errors, unsuitable destinations, and duplicate rows. A valid table does not mean every source server has accepted the credentials. That is checked when the relevant job runs.
Batch size depends on the plan. Follow the limit shown for the specific account. The number of CSV rows doesn't tell you how many mailboxes will copy simultaneously or when the migration will finish.
Run a small pilot group
Choose a few different mailboxes: a small one, one with a large archive, and one with custom folders. Test the settings you intend to use for the rest.
Pay particular attention to folder selection. If only inboxes are copied, employees may find that sent messages or project archives are missing. The selected mode and its result need to match your requirements.
After the pilot, ask owners to find familiar messages, open attachments, and check their folders. Record issues before the larger run. Fixing one shared setting now is easier than investigating discrepancies across the whole company later.
Make a retry a specific action with a clear result
Before repeating a failed row, write down what has changed. Perhaps the source account now has a suitable app password, or the destination has enough free storage. Repeating the same request without resolving its cause can produce another error without teaching you anything. Avoid uploading a new full-company file simply because it is the most convenient copy of the spreadsheet.
Check the relevant job and current destination first. A row that once showed an error may have copied some correspondence before stopping. Understand the existing state and the migration tool's behavior before starting additional work. Do not delete a destination archive to make the numbers look simpler. You still need to explain which source folders and period were selected and what remains to be copied.
After the retry, return to the same row and record its new status. Have the owner carry out the same content checks used in the pilot, including an older attachment and a recognizable sent conversation. A successful job status and an owner's successful check should be separate entries. Neither should be inferred from the other.
When you hand the project over, identify the unresolved addresses explicitly and name who will follow up. Give employees their new login instructions through the agreed account process, not through the CSV containing old access details. Keep the former provider available until archive differences and later arrivals are reconciled. A useful handover tells a colleague exactly what they can trust today and which mailbox still needs work tomorrow.
Turn the batch into a handover list
- For each destination, record the source address, job status and one check by its owner. An address looking correct in the CSV does not prove its messages arrived.
- Investigate failed rows before retrying them. Check credentials, source access and space; do not rerun every successful mailbox just because the batch has an error.
- Keep the previous service available until the group is reconciled. Give staff the new sign-in details separately from the archive-copy report.
Provide new TrekMail sign-in details through the agreed process. Importing message history does not preserve employees' old passwords. Transfer contacts and calendars separately if needed.
Use the migration overview to plan the delivery change. The handover is ready when each person knows where new mail arrives and which old messages still need attention.