Business email migration is the process of moving an organisation's mailboxes, old messages, shared mailboxes and domain settings from one email system to another. It involves four jobs: taking an inventory of mailboxes, preparing the DNS and MX change, copying old mail and syncing the final difference, and helping users settle in. Planned well, staff barely notice the switch.
Why companies change their email system
Behind most migration decisions is a build-up of frustration. Mailbox quotas keep filling up, the password for a shared mailbox is known by half the office, closing a leaver's access takes days, or fake emails sail through the filter. Some companies simply want to bring several domains and providers under one roof.
Once the decision is made, the real worry begins: "Will old emails disappear? Will mail stop arriving on the day? What happens to the accounts on our phones?" Those worries are justified. An unplanned migration really can mean lost mail, duplicated folders and a week of calls to the help desk. We cover the selection criteria in how to choose business email; this guide focuses on the migration itself.
The risks of an unplanned migration
Migration looks like a technical job, but its weakest link is often people. Most Turkish businesses have no in-house IT specialist to run it:
According to TÜİK, Türkiye's statistics office, only 15.2% of Turkish enterprises employed ICT specialists in 2026 (10.8% of those with 10-49 employees), and 31.7% of those recruiting ICT specialists reported difficulties in 2025. (TÜİK ICT Usage in Enterprises Survey, 2026)
The migration window is also a security gap. New passwords are sent to staff, "please verify your account" emails suddenly look normal, and attackers know it. According to the Microsoft Digital Defense Report 2025, more than 97% of identity attacks are password attacks, and phishing-resistant multi-factor authentication can stop over 99% of them. So if the new system offers multi-factor authentication, switch it on from day one.
There is a legal side too. If the new provider stores data abroad, that may count as a transfer of personal data outside Türkiye. According to the Turkish Data Protection Authority's page on transfers abroad, Article 9 of the KVKK, which governs such transfers, was amended by Law No. 7499 and the new rules have applied since 1 June 2024. A transfer to a country without an adequacy decision generally has to rely on an appropriate safeguard such as a standard contract, which must be notified to the Authority within five business days of signature. We cover the detail in KVKK cross-border data transfer; settle where your data will live, and review it with your legal adviser, before you commit to a move.
Migration approaches: which one suits you?
| Approach | How it works | Advantage | Watch out for |
|---|---|---|---|
| Cutover | All mailboxes move in one weekend; MX changes once | Short and clear | Suits small and mid-sized organisations; needs good testing |
| Staged | Departments move one after another | Spreads the risk | Needs routing and address book alignment between two systems |
| Coexistence | Old and new systems run in parallel for a while | Flexibility in large organisations | Complex; routing rules must be well documented |
For most SMEs with tens or a few hundred mailboxes, a cutover backed by a good pilot is the route with the fewest surprises. Mail is usually copied mailbox by mailbox over IMAP or with the import tools a provider offers; calendars and contacts often have to be moved separately.
Whichever approach you choose, keep the date away from busy periods such as month-end close, invoicing runs or a major bid deadline. Starting on a Friday evening and using the weekend for syncing and testing keeps Monday morning problems small. Write a rollback plan too: if something goes wrong, who switches MX back to the old system, and under what conditions?
Nine steps to a downtime-free business email migration
- Take an inventory. List every personal mailbox, shared mailbox, alias, distribution list, forwarding rule and mailbox size. Closing unused mailboxes at this stage reduces both the migration load and the new system's per-mailbox cost; when comparing proposals, see the business email pricing factors.
- Redesign shared mailboxes. Moving
accounts@orsales@with a shared password just carries the old problem across. We explain per-person permissions in shared mailbox management. - Confirm where data will be stored. Get the new system's data location, backup and retention terms in writing, and align archiving rules with your email archiving and data protection policy.
- Prepare DNS. Lower the TTL on your MX record a few days before the move so that the change spreads quickly on the day.
- Prepare authentication records. Before the first user sends mail from the new system, add it to SPF, publish the new DKIM key and start watching DMARC reports; otherwise the pilot users' mail may land in spam, in which case follow the steps for diagnosing emails that go to spam. See our SPF, DKIM and DMARC guide for detail.
- Run a pilot. Move a few users with different devices and habits first. Problems with phone set-up, signatures, folder structure and shared mailbox access surface here.
- Copy old mail in advance. Transfer the history of large mailboxes before migration day, so that only the final difference (the delta) is left to sync.
- Switch MX and sync the delta. Point the MX record to the new system, keep the old server accepting mail until the TTL has expired, then run the final sync.
- Plan the shutdown. Keep the old system read-only for a while and verify the remaining data; remove its entries from SPF when you end the contract and switch it off.
What to tell users on migration day
Send a short, one-page guide: the migration date, how to sign in, how to add the account on a phone and who to call if something goes wrong. Always include the line "we will never ask for your password by email". Warning the team about fake "verify your account" emails during migration week starts with the signs in how to spot phishing emails.
Turn the migration into an opportunity
Migration is the best moment to clean up access. Close mailboxes that still belong to former employees and forwarding rules nobody owns; for a lasting process, read offboarding email access. If the move is part of a wider cloud plan, weigh the budget against the items in cloud migration cost.
How we run email migrations at Digital Bridge
We treat migration as a small project rather than an overnight job:
- Discovery and needs analysis. Through our cloud migration and infrastructure consultancy we map mailboxes, domains, DNS records and shared mailbox use, then agree the approach and timetable with you.
- Security and compliance checks. With our cyber security consultancy we plan the SPF, DKIM and DMARC changes; with our data protection compliance service we settle data location and retention rules.
- Pilot and cutover. We move a small group first, fix what comes up, then complete migration day with the MX change and final sync. We write down how to roll back to the old system if something goes wrong, and test that plan before the move.
- Integration. Through our system integrations work we reconnect the mail settings of ERP, CRM, scanners, multifunction printers and other systems; a forgotten device that can no longer send invoice emails is a frequent post-migration problem. We explain how such connections work in API integration explained.
What changes when you move to Smart360
If you choose our own Smart360 family as the new system, there is nothing to install: the account opens as soon as payment is confirmed. Domains and DNS settings, users, departments and product access are managed from a single admin panel. Staff sign in with one identity (SmartID), and a leaver's access is closed in a single step; SmartMail generates mailbox passwords itself and stores them encrypted with AES-256-GCM, and those passwords are never handed out to staff.
Shared mailboxes you redesign during the move are opened to each person in SmartMail with nine separate permissions; delete and quarantine management are switched off for new assignments. Distribution lists, per-mailbox signatures and an audit log are set up in the same panel. The mobile app handles several company accounts at once, and each organisation's data is kept in its own database. If you also want to organise attachments and documents, SmartFiles works with the same identity.
Your next step
If you are setting up email on a domain from scratch, read how to set up email with your own domain; for the wider topic, see Business Email & Documents.
To get started, put your mailbox list, your domains and who uses each shared mailbox into one spreadsheet. Then get in touch via our contact page or call +90 552 380 25 25, and we will work out the approach, the rollback plan and the timetable together.