This article describes how to upgrade your current Microsoft® Exchange environment to a later Exchange version.
Only the following email clients can safely upgrade to a newer Exchange version:
- Outlook® 2016
- Outlook 2013
- Outlook 2010
- Mac® Mail
Note: Exchange does not support Outlook 2007 and older with later Exchange versions. Users on Outlook 2003 or 2007 must upgrade to Outlook 2010 or later.
The migration includes everything from your current Exchange environment, including the following items:
- Exchange mailboxes
- Email data
- Exchange contacts
- Distribution lists
Before migrating to a later Exchange version, consider the following information and perform the following tasks.
Although we do not anticipate any issues with the migration, we recommend that you back up your data before the migration. You can back up your data by performing a Personal Storage Table (PST) export with Outlook.
Note: The process does not migrate corrupt data.
Our hosted Exchange environment offers public folders with the following limitations:
There is a limit of 25 folders with a maximum size of 250 megabytes per folder, including the root folder.
Exchange administrators must use the control panel to manage public folders.
The environment disables public folder administration actions such as creating, editing, or moving public folders in Outlook for Exchange users.
You cannot use user permissions such as granting read, edit, or delete access.
The spam handling in Exchange 2013 and later differs from Exchange 2007 and 2010. Exchange mailboxes no longer use the quarantine manager, and any spam messages sent to users go to the junk or spam folder.
The domain quarantine still receives spam messages for other Exchange addresses such as contacts, distribution lists, public folders, and resources. You can set a user's spam to go to the domain quarantine, but only an administrator can access this quarantine manager.
You can contact Support to schedule an Exchange upgrade at any time. You can request this migration through Support via ticket, chat, or phone call.
This section provides answers to questions that you might have about the Exchange 2016 migration.
In most cases, you do not need to change your Mail Exchange (MX) records because they should already point to our environment. You can review our MX record details in the article Set up DNS records for Cloud Office email.
No. This type of migration requires all users to migrate at the same time because our environment allows the domain to reside in only one Exchange environment.
The reconfiguration prompt occurs in the following situations:
- The user is using Outlook 2010 or 2013.
- Autodiscover set up the user's profile.
- The Autodiscover CNAME points to autodiscover.emailsrvr.com, and Autodiscover configured the profile.
There is no downtime during the migration—the system delivers mail without interruption. Users can send and receive email normally throughout the migration process.
The following items can affect the length of your migration:
Total size of attachments
Number of mailboxes on the domain
Provisioning delays in our Exchange environment. See the System Status Page for notice on this type of issue.
Note: You cannot estimate the length of time a migration will take because of the variance in the preceding items.
Yes, you must reconfigure all mobile devices, except for some Blackberry® devices. Blackberry® Enterprise Server 5 is not compatible with Exchange. For Blackberry devices with software version 10.0 and later using ActiveSync, you don't need to perform reconfiguration.
For all ActiveSync devices, you can either update the existing settings or remove the account and add it again.
Yes, but you should not make any changes to your domain. Making changes to the target migration domain during the migration causes issues.
Updated 7 months ago