Email migration FAQ

MailSync copies email between a source and destination IMAP mailbox. Create the destination mailbox with your new provider first, then enter both servers’ connection details in MailSync. You can run an initial migration and refresh it later while preparing to move.

Create an account and verify your email. Save your source and destination mailbox details, buy credits, then queue the first sync. Check the destination mailbox before changing your domain’s email routing. Our migration guide explains each step.

No. You manage DNS and your email apps separately with your providers. MailSync handles IMAP email; plan a separate transfer for contacts, calendars, forwarding rules, signatures and other provider settings.

Yes. Queued syncs run in the background. Return to your migrations list or refresh the mailbox page to see its status and run history. You can cancel a queued sync before it starts; a running transfer cannot be stopped through the interface.

Yes. Use New batch to save up to 250 mailboxes with shared server settings, then select mailboxes and queue their syncs together. CSV import supports email and password columns. Each mailbox pair still needs its own credit; saving a batch does not start a migration or spend a credit.

Both servers must offer IMAP over a public IPv4 address and accept a mailbox password or app password. MailSync supports implicit SSL/TLS, normally on port 993, and required STARTTLS, normally on port 143. Custom ports are supported. Ask each provider for its IMAP hostname, username, port and encryption mode.

It may work if the provider permits IMAP and offers an app password. Use that app password rather than assuming your normal login password will work. OAuth-only accounts and IPv6-only servers are not currently supported. Compatibility depends on the account’s authentication settings, not just the provider’s name.

Confirm that both mailboxes exist, IMAP is enabled, credentials work and the destination has enough storage. Email visible only in a local computer folder is not available to an IMAP migration. Back up important mail and keep access to the old service until you have checked the results.

One £5 credit belongs to one source and destination mailbox pair and covers six successful runs: the initial migration plus five refreshes. Its first queued run assigns it permanently to that pair. Credits belong to the purchasing user and cannot be shared through team membership.

Buy four credits in the same checkout and receive one free: five credits for £20. Every complete group of four paid credits earns another free credit. Each bonus credit has the same six-successful-run allowance.

A queued run reserves one of the six runs. Failure, timeout or cancellation before execution restores that allowance. The credit stays attached to the same mailbox pair. Correct the issue and queue a new sync when ready.

Another credit unlocks the next six successful runs for that mailbox pair. You cannot move an assigned credit to a different pair by changing the source or destination identity.

Mailbox passwords are encrypted in storage and excluded from application logs and validation error sessions. The migration engine receives them through private temporary files rather than command-line arguments. You can remove saved passwords when the mailbox is idle; enter them again before another sync.

Leave verification enabled. It checks that the encrypted connection is to the expected server. If a sync reports a TLS error, check the hostname, encryption mode, port and provider’s certificate first. Disabling verification allows server impersonation even though the connection remains encrypted.

MailSync is provided by TSI Hosting Ltd. Visit the TSI Hosting website to learn about the company behind the service.