In the past few months, I have been working with some clients on moving their existing Small Business Server (SBS) systems over to the Microsoft cloud based Office 365 email system. There are a number of issues and possible gotchas in making this transition which will be discussed here. Note that this blog post is targeted to the small business community with existing SBS 2003, SBS 2008 or SBS 2011 deployments that are looking to move their email services to Office 365, while maintaining their existing network. We will not be considering Office365 migration method in this move as the costs and complexity of implementing this in a small business are prohibitive.
The pre-requisite when performing such a migration, is to plan and work out a migration path for email services. Questions to be considered are:
- Do we need to migrate all the old email data, or should some be archived?
- Are there old accounts that can be decommissioned?
- What distribution groups and contacts need to be migrated across?
- Are there any Send As and Send on Behalf of permissions that need to be addressed?
- Are there individual permissions on Calendars and Folders that need to be recreated?
- How will we move the old email data from Exchange on premises to Office 365?
Moving Email data from On-premises Exchange to Office 365
Central to the entire issue is retaining old emails and settings. There are a number of ways to move the data across to Office365.
- Export-Import. This method involves exporting the current emails to PST and re-importing them into Office 365 once Outlook has been configured.
- Migrationwiz.com is a fast and easy way to move mailboxes at a low cost.
- Office365 Migration wizard. This is a built in tool from Microsoft to help in performing a migration from on-premises Exchange. It requires an Azure subscription and the installation of the Directory Sync tool and has some tough pre-requisites for SMBs. The process is detailed on technet here – http://technet.microsoft.com/en-us/library/jj573653.aspx
One main drawback from using any method that does not synchronize the Office 365 platform to your existing Active Directory is dealing with the issue of Auto-Complete or Suggested Contacts. After the migration, it is quite likely that replies on old emails or emails sent using the stored contact information in Auto-Complete or Suggested Contacts will result in a Undeliverable error as follows:
#550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##
Create Users and Set up Domain in Office 365
In this step, you need to set up and recreate all the users, distribution groups, and domains to match what you have on-premises. In the public DNS, set the MX records to point to your on-premises Exchange until you are ready to receive emails at the Office 365 service. Ensure that the Autodiscover and other DNS services are set up properly.
Setting up the Outlook Profile
One of the main issues with setting up Outlook for Office 365 on an existing SBS domain is the existing autodiscover configuration set up for each user account. The following steps should be followed to ensure a simple, incident free set up of Outlook on Office 365.
- Log in to the PC as the user. The configuration is done per user.
- Update your PC with a the latest patches, especially Microsoft Office patches and Service Packs.
- Log in to the Office 365 portal using the users email address and assigned password.
Install software and connect it to Office 365
You will need to sign in to Office 365 again using the user’s credentials.
The Office 365 setup application will note that manual steps will be required (which involves setting up the Outlook profile as detailed here).
Once the set-up is completed, you will need to create 6 new registry entries. (thanks to https://gothamweb.com/esupport/index.php?/Knowledgebase/Article/View/133/26/outlook-2007-connecting-to-a-local-exchange-server-instead-of-hosted-exchange)
For Office 2007, the registry key is [HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\AutoDiscover]
For Office 2010, the registry key is [HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\AutoDiscover]
The six entries are all DWORD. (NOTE: all but one entry are set to 1)
They should be displayed among other entries like this.
Download and run the two AgileIT tools from http://www.agileit.com/news/office-365-autodiscover-xml-tool-released/. Just enter the domain name and click OK.
Now you can Add a new Outlook Profile from Control Panel-Mail (32-bit). You will see the existing Outlook Profile there, which can be kept as a backup, as you may need it later for export to PST purposes.
The local autodiscover settings that have been configured earlier will kick in and set up the account. You will need to log in using the Office 365 credentials.
You can also add the on-premises Exchange profile to this new profile, if you are planning to export the old email data or manually transfer information over to the office 365 account.
With smaller sites, this is a quick and easy way to manage your Office 365 migration. With larger installations, the Office 365 migration wizard using Azure and Directory Sync may be a more efficient method. In the end, it is up to the business owner, with advice from the IT consultant, to work out which method is preferred.
UPDATE: There is a really good article on how to use Azure Active Directory to handle password sync between your local AD and the new Office 365 AD – www.infostream.cc/dirsync-aadsync
11 thoughts on “Migrating Email from SBS Exchange to Office 365”
Another tool, that is very helpful when moving mailboxes from SBS 2008, is CodeTwo Office 365 Migration: http://www.codetwo.com/office-365-migration/
There are many tools out there that claim to do migrations. I have not tested this one, as it is a paid migration tool. I did try to use the free Outlook AutoConfig, but it did not work.
Thank you very much for sharing this information. Solving the problem was done in an instance.
Now one more problem to solve before upgrading from SBS2008 to Windows Server 2012 Essentials, moving our existing Sharepoint site to ? ? Skydrive pro but how?
Unfortunately, that is a bigger problem. Robert Crane [Office365 MVP] has an excellent post on this – http://blog.ciaops.com/2013/07/migrating-from-companyweb-to-office-365.html
Thanks so much for this info. I’ve been looking for a resolution to this issue for about a year now. These procedures finally fixed this annoying problem.
There’s no documentation about the AgileIT Autodiscover tools, and I’m seeing conflicting information out there. Do you have to run both? This seems unique to each local user profile, is there anyway to set this up once on each PC so any new profile will automatically use the new settings? I’m also seeing posts about from AgileIT about disabling SCP. Is this also required? Hoping for a smooth process and not an “all nighter”.
I have always run both.
Yes, they are unique to the user profile. I have not had the need to set this up for each PC, as the sites are generally not large.
I haven’t disabled SCP before.
Really good information, it provides the step by step guide to migrate Exchange 2003 Server to Office 365. I understand that how to migrate Exchange 2003 Public Folders to office 365. I found the good utility named LepideMigrator for Exchange ( http://www.lepide.com/exchangemigrator/ ) that helps to migrate any exchange server to office 365 without any interruption.
Since this is SBS, as with any Domain, there is Group Policy. Why not just use the GPO Templates for Office 2007/2010/2013 and set the AutoDiscovery settings versus doing it in the registry? Then you can set them on the OU and enable them when you are ready. Good article here: https://doubledit.co.uk/2014/10/21/controlling-autodiscovery-using-group-policy/
Yes, since this blog post was written, there have been other ways to set up Autodiscover on SBS. See this recent post – http://blog.powerbiz.net.au/sbs-2008/office-365-migrations/