As you may or may not be aware, my personal email (with “vanity” domain) is hosted on Office 365. Yes, that business service which charges $6/month for Exchange, SharePoint and Lync Online. I have had it since they launched the small business and professionals plan.
Since then, Hotmail has gone from being the dull and boring email service no one wants to be associated with, to a beautiful and modern Outlook.com. While Hotmail always provided the ability to use custom domains, I never thought of using that option because it was not a great email service. For example, there was no easy way to connect to it from a desktop email client unless you use Outlook Express or Windows Live Mail. Outlook added a Hotmail Connector but it always felt like a hack. And of course, there’s mobile.
With Outlook.com, what’s nice is that it supports Exchange Active Sync out of the box. No connectors needed. No jumping through hoops. 2-way sync, push support and all that jazz. For free. I have been tempted to move my domain email to this combination except that my mailbox is fairly huge (5GB) and I was not sure if I will be able to move the entire thing and I was not even sure how long it would take.
So I did some quick experiments with my existing Hotmail account and realized that via IMAP, I am able to move my emails fairly quickly over Comcast’s speedy internet connection (and maybe a much better back-end on Outlook.com?). So, I decided to take the plunge and make the move.
I disconnected my email account from my domain on Office 365, “removed” the domain from Office 365’s management, added the same to Live Domains and set up my account there. With some small glitches here and there (my email was an alias on my existing Hotmail account, so I wasn’t able to add it as a new domain email account until I removed the alias), I was up and running with my new setup.
I used Outlook 2013 to connect to my Office 365 account (via normal “Exchange” connectivity) and Outlook.com account (via IMAP). I started moving emails by folders and realized most of the messages were showing up on the web fairly quickly. Except for two very large folders, I was done in a couple of hours. The large folders took a bit longer but not terribly so. Overnight, I was actually surprised that I was done with the email part. What remained was calendar and contacts, both of which created much pain.
I took it for granted that calendar can be moved as easily as email but I was in for an unpleasant surprise when I realized I was connected to Outlook.com via IMAP. That means, no calendar support. I saved the Office 365 calendar as an ics file (was not under “export” but under “save as” in Outlook 2013 – go figure) and imported it from the web. That was easy, except that the “save as ics” step did not save every single event! There was no obvious pattern in what was saved and what was omitted.
Another idea struck me: why not connect to Outlook.com via EAS in Outlook 2013 and then copy all calendar events from one account to the other? Great idea, except there is a massive bug in Outlook 2013’s EAS implementation which does not sync events if you mass-copy them on a calendar. If I did all 350-odd events one-by-one, it would have worked. But I was not in a mood to do that. So the workaround was to simulate an edit across all the events and that is easily achieved with marking them all as a new category. That seemed to trigger a forced sync and I started seeing the events show up on the web. What seemed to be missing was events that I had marked as private, or at least some of those private events. Again, the EAS bug comes to bite me because even after marking them all as normal sensitivity, I could not simulate a sync. At this point I kinda gave up on the sync and re-saved the calendar as ics and imported it from the web. Then, a sync happened that showed up in Outlook 2013. For all the stuff that was not correctly sync-ed, including some recurring events that ended up showing as one-time, I manually went to the web and added/updated.😦
As for contacts, I moved to Outlook.com as my “single source of truth” for contacts long time ago. I have been pretty happy with the arrangement especially because most of the contact manipulation (adding/updating/deleting) happens on mobile devices and with EAS, I am seconds away from always being up-to-date. Additionally, I have linked my Microsoft account to LinkedIn, Facebook and Twitter and as a result, I have the “master” address book under People on my Outlook.com account. However, there is no way for me to link that account with the new account I created. No sharing, no linking, no sync-ing, and that’s a pity. I was hoping that just like I link a Facebook, Twitter or LinkedIn account with Microsoft account, I could another Microsoft account too. Not to be. So I went for the next best option, which was to export and import. I could export my Outlook.com contacts as a csv but shockingly, when I tried to import, I got a generic error that seemed to indicate that there are some special characters in some phone or email fields somewhere in that csv file. No partial import, no specific error on specific records, nothing. An all or nothing which to me ended up with nothing. In the end, I had to go back to Outlook 2013 and with EAS, I was able to copy contacts from one account to the other.
Despite those multiple hiccups, I am glad to say I am done with the migration much sooner than I thought I would be and most importantly, there were no issues with the email migration. I was afraid of duplicates and missed emails neither of which happened.
I will monitor for a few days after which I am going to cancel my Office 365 paid account but a practical limitation I am facing now is that at work where I prefer to keep personal email limited to a tab in a browser, I won’t be able to see my current Hotmail account and the new custom domain account in a single browser window. With Office 365 account, I was able to because they don’t share the cookie, I suppose, but with both the accounts now running off Outlook.com back-end, I am unable to. It is a pain to have two browser windows open, one of which is an InPrivate window, but I am sure it is something I can get used to over time.
And to finish off, can I just say that Microsoft has made a big mistake calling their webmail service Outlook.com which is very close to their email client Outlook. Searching for solutions to the various problems I had almost invariably landed me on help pages for Outlook the program vs Outlook.com the service. It was quite frustrating.😦