Microsoft: Avoid Manual BPOS to Office 365 Cloud Migrations
Microsoft’s policy of not letting its BPOS customers migrate to the Office 365 cloud suite until it says so has some cloud service providers chafing. And some are looking at manual migrations as a way to cut the line. But not so fast: Microsoft is strongly advising BPOS users not to take the manual route to Office 365, for fear of a cloud service disruption.
The relevant Microsoft Online Services blog post, which went live Aug. 7, 2011, went largely unnoticed until All About Microsoft’s Mary Jo Foley took notice. But hopefully it isn’t too late for Microsoft cloud partners.
Microsoft says of the dangers of being too hasty:
We have received a number of Support calls from customers and partners who have tried to migrate their data from BPOS to Office 365 by themselves. Please be aware that if you attempt a manual migration, e-mails sent to your domains will be returned to sender as undeliverable until Support can delete your domain from BPOS and you can re-create in Office 365. This e-mail outage could last as long as 24 hours (possibly longer if many customers are asking Support to delete their domains at the same time as you).
But if you’re “an expert in Exchange server migrations, comfortable with PowerShell scripts, and just can’t wait a couple of months,” that blog entry has the steps necessary for a manual migration. But Foley’s blog entry contains an anecdote from a user whose Microsoft-guided migration went horribly awry, leaving his domain unable to send or receive e-mail for eight days.
The implication: If Microsoft can’t do it right, how can you hope to? Microsoft hopes to have all its BPOS customers on the Office 365 cloud by September 2012, so stay tuned for updates.