Thus far we've discussed what Microsoft BPOS is and why one of our clients, Eagle Environmental, found BPOS to be the solution of choice for them. Now, I'd like to spend some time discussing how we proceeded through the migration from their POP server to BPOS.
Eagle's migration took place in three basic steps.
- Preparation
- Email Migration
- 3. Communicator Installation
Preparing for a migration to BPOS is extremely important. If you don't have your "ducks in a row," you will likely run into issues that affect your business operations. In my opinion, the most important aspect of the preparation is making sure you are in control of your DNS. SMBs often don't manage their own Domain Name Service (DNS) and such was the case with Eagle. Utilizing BPOS requires a couple of DNS changes to ensure that email is delivered correctly. Because having DNS records set up incorrectly will cause email delivery failure, it is vital that the records be changed just before the migration begins. When you are not in control of your DNS records, you are at the mercy of whomever is in control of the records. In Eagle's case, their ISP controlled the records and so our first step in preparation was to get control of the DNS. Completing this process proved exactly why it was so important. Everything considered, it took about 6 weeks to work with Eagle's ISP and get the DNS control away from them and into our hands. Now if this was not done before the actual migration, Eagle would've experienced email delivery issues for the whole 6 weeks. Now if you are in a position where you cannot get control of your DNS, there are some workarounds but ideally, you will be in control.
The next step in preparation was getting a list of email boxes that will need to be set up. This is typically just a user list but you must also consider general mailboxes such as info@yourdomain.com or sales@yourdomain.com. In Eagle's case, they had one general email box and a box for an old employee that they still wanted delivery for.
Finally, just before the actual migration, we made a backup of every users mailbox. If you host your own Exchange server now and are moving to Exchange online, this step is not necessary. In Eagle's case, though, they were using a POP server and the only copy of the emails were in the users' mailboxes.
With the above information in hand and backups of the mailboxes, we were ready to move forward to the email migration from Eagle's POP server to Exchange Online.
The first step was to purchase the licensing through Eagle's Microsoft Customer Portal (this requires a Windows Live ID so if you don't have one already, you will need to get one). Once the licenses are bought, we opened Eagle's Administration Portal and added the users who needed mailboxes.
The next step was to make the DNS changes as discussed above. The DNS changes tell the computers along the internet how they should route incoming email. Since Eagle's email would not be going to the Microsoft hosted Exchange server instead of their ISP's POP server, we had to let the internet know.
After completing the DNS changes, we began the long process of uploading the backed up mailboxes on the users' computers to the new Exchange Online mailboxes. WARNING!!! The upload process can take a LONG time. Eagle had some users with mailbox sizes of several gigabytes. They connect to the internet via a T1 line and with all of the data being uploaded from the users mailboxes, the pipes got quite backed up. We knew this would be an issue so we started the process during a long weekend. If you don't have a long weekend to work with, be sure you utilize as much down time as you can as the process may take a couple of days depending on your mailbox sizes and internet bandwidth.
During this process, we first loaded the Microsoft Single Sign-on application onto the user's machine, updated the settings for Outlook to tell it how to connect to the hosted Exchange server (this can be done automatically by the Single Sign-on application which creates a new Outlook profile or manually which retains the existing profile), and used Outlook to import the mailbox backup. Oh, and we waited... and waited... and waited... while the mailboxes were uploaded.
The final phase was to configure users' smartphones to connect to Exchange Online and finally, to add Office Communicator to the user's machines and allow the Single Sign-on application to configure it. We did the Communicator part several days after the mailbox upload as it seemed a good idea to make sure everyone's emails were functioning properly and all the user's were adjusted to the change.
Overall the process of migrating Eagle Environmental to Microsoft BPOS went very well. We hit a few hiccups along the way but there was nothing that was not easily overcome. Eagle didn't experience any significant downtime and everyone has accepted the changes enthusiastically.