# Business Email Migration Guide: Moving Company Mailboxes Without Data Loss or Downtime

> How to migrate business email in 9 steps: inventory, MX and SPF/DKIM set-up, a pilot and a final delta sync, so company mail moves with no loss or downtime.

Source: https://digitalbridge.com.tr/en/blog/email-migration-guide.html
Publisher: Digital Bridge Teknoloji (https://digitalbridge.com.tr)
Topic: Business Email & Documents
Published: 2026-10-04 · Updated: 2026-10-28

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.

## Key takeaways

- Business email migration moves mailboxes, old messages, shared mailboxes and domain DNS settings to a new system.
- In 2026 only 15.2% of Turkish enterprises employed ICT specialists (TÜİK), so a migration should be planned as a project.
- For SMEs with tens or a few hundred mailboxes, a single cutover backed by a good pilot brings the fewest surprises.
- Lowering the MX record's TTL in advance and keeping the old server open for a while prevents lost mail.
- If SPF, DKIM and DMARC are not updated before the first message is sent, migrated mailboxes' mail may land in spam.

## Why do 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](https://digitalbridge.com.tr/en/blog/business-email-how-to-choose.html); this guide focuses on the migration itself.

## What are the risks of an unplanned email migration?

Email migration looks like a technical job, but its weakest link is often people. Most Turkish businesses have no in-house information technology (IT) specialist to run it:

> According to TÜİK, Türkiye's statistics office, only **15.2%** of Turkish enterprises employed information and communication technology (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](https://veriportali.tuik.gov.tr/tr/press/58021))

The email 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](https://blogs.microsoft.com/on-the-issues/2025/10/16/mddr-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](https://digitalbridge.com.tr/en/blog/multi-factor-authentication-business.html), switch it on from day one.

Email migration has a legal side too. If the new provider stores data abroad, that may count as a [cross-border transfer](https://digitalbridge.com.tr/en/glossary.html#cross-border-data-transfer) of personal data outside Türkiye.

According to the [Turkish Data Protection Authority's page on transfers abroad](https://www.kvkk.gov.tr/Icerik/2053/Yurtdisina-Aktarim), Article 9 of Law No. 6698 on the Protection of Personal Data (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](https://digitalbridge.com.tr/en/blog/kvkk-cross-border-data-transfer.html); settle where your data will live, and review it with your legal adviser, before you commit to a move.

## Which email migration approach 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 (Internet Message Access Protocol) or with the import tools a provider offers; calendars and contacts often have to be moved separately.

Whichever migration 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?

## How do you migrate business email? Nine steps with no downtime

1. **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](https://digitalbridge.com.tr/en/blog/business-email-pricing-factors.html). Add any personal Gmail accounts used on the company's behalf; that move is covered in [using Gmail for business email](https://digitalbridge.com.tr/en/blog/using-gmail-for-business-email.html).
2. **Redesign shared mailboxes.** Moving [shared mailboxes](https://digitalbridge.com.tr/en/glossary.html#shared-mailbox) such as `accounts@` or `sales@` with a shared password just carries the old problem across. We explain per-person permissions in [shared mailbox management](https://digitalbridge.com.tr/en/blog/shared-mailbox-management.html).
3. **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](https://digitalbridge.com.tr/en/blog/email-archiving-data-protection.html) policy.
4. **Prepare DNS.** Lower the TTL (time to live, how long the record is cached) on your Domain Name System (DNS) MX (mail exchanger) record a few days before the move so that the change spreads quickly on the day.
5. **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](https://digitalbridge.com.tr/en/blog/emails-going-to-spam-fix.html). See our [SPF, DKIM and DMARC guide](https://digitalbridge.com.tr/en/blog/spf-dkim-dmarc-explained.html) for detail. According to [Google's email sender guidelines](https://support.google.com/a/answer/81126?hl=en), since 1 February 2024 anyone sending more than 5,000 messages a day to Gmail accounts must set up SPF, DKIM and DMARC.
6. **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.
7. **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.
8. **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.
9. **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

On email migration day, send users 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](https://digitalbridge.com.tr/en/blog/how-to-spot-phishing-emails.html).

### Turn the migration into an opportunity

An email 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](https://digitalbridge.com.tr/en/blog/offboarding-email-access.html). If the move is part of a wider cloud plan, weigh the budget against the items in [cloud migration cost](https://digitalbridge.com.tr/en/blog/cloud-migration-cost.html).

## How we run email migrations at Digital Bridge

At Digital Bridge we treat email migration as a small project rather than an overnight job:

- **Discovery and needs analysis.** Through our [cloud migration and infrastructure consultancy](https://digitalbridge.com.tr/en/consultancy/cloud-migration-infrastructure-consultancy.html) 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](https://digitalbridge.com.tr/en/consultancy/cyber-security.html) we plan the SPF, DKIM and DMARC changes; with our [data protection compliance](https://digitalbridge.com.tr/en/consultancy/data-protection-compliance.html) 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](https://digitalbridge.com.tr/en/technology-hardware/system-integrations.html) 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](https://digitalbridge.com.tr/en/blog/api-integration-explained.html).

## What changes when you move to SmartMail from the Smart360 family?

If you choose [SmartMail business email](https://digitalbridge.com.tr/en/smart360/smartmail.html) from our own [Smart360](https://digitalbridge.com.tr/en/smart360.html) family as the new system, there is no server to install: the account opens as soon as payment is confirmed, initial configuration is guided by the Smart360 team, and your old mail is migrated into SmartMail and analysed free of charge during the initial setup. 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 document management](https://digitalbridge.com.tr/en/smart360/smartfiles.html) works with the same identity, and an attachment that arrives in SmartMail can be saved to a SmartFiles area in one click. Plan details are on SmartMail.com.tr; to buy SmartMail, use the [Smart360 purchase page](https://smart360.com.tr/satin-al?urun=smartmail).

## Your next step

If you are setting up email on a domain from scratch, read [how to set up email with your own domain](https://digitalbridge.com.tr/en/blog/set-up-email-with-your-domain.html); for the wider topic, see [Business Email & Documents](https://digitalbridge.com.tr/en/blog/topic/kurumsal-eposta.html).

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](https://digitalbridge.com.tr/en/contact.html) or call 0850 346 41 09, and we will work out the approach, the rollback plan and the timetable together.

## Frequently Asked Questions

### Will we lose emails during the migration?

Not if it is planned properly. Loss usually happens when the old server is switched off immediately after the MX change, because some sending servers keep using the old record for a while. Keeping the old server open until the TTL expires and then syncing the final difference removes that risk. Remember that calendars and contacts often need moving separately.

### How long does an email migration take?

It depends on the number of mailboxes, total data size, the number of shared mailboxes and forwarding rules, and whatever the pilot uncovers. When most of the history is copied before migration day, the disruption users notice is usually limited to the short period while the MX change spreads. Set a firm timetable only after the inventory is done.

### Do we have to move every old email?

No, but the decision should be written down. Some organisations move the last few years into the new mailboxes and keep older mail in a read-only archive. A retention policy that sets how long each type of correspondence is kept, in line with tax, commercial and data protection obligations, stops this becoming a personal choice.

### What happens to email accounts on our phones?

Because the server address and sign-in details change, accounts on phones and computers must be added again. Rather than leaving it to each user, prepare a one-page guide with screenshots and test it with the pilot group. Having the help desk ready during migration week means most calls are resolved on the first day.

### What does the cost of a business email migration depend on?

The main cost drivers are the number of mailboxes, the total volume of data to move, the number of shared mailboxes and forwarding rules, whether calendars and contacts move too, and reconfiguring systems such as ERP or multifunction printers that send mail. The new system's per-user subscription is a separate line. Any quote given before the inventory is done is largely a guess.

### Will our emails land in spam after the move?

They can if the new system is not added to SPF, the DKIM signature is not published or DMARC alignment breaks. Update all three records before the first user sends from the new system, remove the old system from SPF only when you shut it down, and monitor DMARC reports for the first few weeks. Large providers such as Google have required these records since 2024 from anyone sending more than 5,000 messages a day.

### How long does an MX record change take to spread?

How quickly an MX record change spreads depends on the record's TTL value, because servers across the internet keep the old record cached until that period ends. Lowering the TTL a few days before the move therefore makes the change on migration day spread quickly. Until it has spread, keep the old server accepting mail, then sync the final difference.
