Migrating to Office 365: Pitfalls to Avoid

In case you haven’t heard, the Office 365 administrative portal lets you initiate migrations directly from the web. This is a welcome addition to the Office 365 suite. However, there are a few important pitfalls you should be aware of.

After your migration completes, source mailboxes will be disconnected from Active Directory. This is a significant problem if you need to rollback, want to compare source and destination mailboxes, or intend to perform a multi-pass migration.

You also cannot control the migration process. There is no guarantee when the migration will start or how many computing resources will be allocated for it. This may have a significant impact on companies looking to migrate over a week end for example.

The migration process may require authentication changes (ex: integrated auth does not work). It may also require you to deploy an Exchange 2010 proxy. None of those are feasible when migrating from a hosted Exchange provider.

Your migration options are limited to Exchange and IMAP. With Office 365’s built-in tool, there is no support for migrating from Google Apps, GroupWise, POP, etc. If migrating from IMAP, realize that it takes extraordinary skill to handle all different flavors of IMAP.

Finally, the migration process requires you to deploy a trusted SSL certificate. That’s right, a self-signed certificate will not work. Trusted SSL certificates cost money. They also require the issuer to perform multiple identity verification checks which takes days.

We at MigrationWiz believe that we can help you address most if not all of those issues – get in touch today!

Leave a Reply

Be the First to Comment!

Notify of