An Office 365 migration is not always an easy task. In this article we look at what can go wrong when migrating to Office 365. Knowing What to avoid at all costs when Migrating to Office 365 is very important to know.

7 things to avoid when Migrating to Office 365

1. Checking the requirements

Some organizations are all too eager to jump into an Office 365 migration without doing their due diligence around their Office 365 requirements. For example, you may find computers are not running the supported versions of Office to connect to Office 365 and will require an upgrade, or there may be underlying issues with the current Exchange or Active Directory infrastructure which cause the migration to fail.

2. Check compliance

If you are in an industry which is highly regulated, check there are not rules or laws prohibiting the storage of mail and documents in cloud based systems. Also ensure that you meet any compliance in regards to retention of records. If you need to keep all mail for a certain amount of years, you need to ensure it is migrated to Office 365 and that your plan will support that amount of storage.

3. Impacting existing business products

Understanding your current environment and how Office 365 will impact it is crucial to a successful migration. If you have custom in house or 3rd party add-ins for Exchange, these may not be supported in Office 365. Or perhaps you have users or devices that rely on certain versions of Office applications which do not support Office 365. Perhaps you have systems and services configured for mail which will need updating for Office 365. Not identifying these things before a migration could cause a lot of headaches afterwards.

4. Inadequate Internet bandwidth

Many organizations run into this once they begin the migration and find the speed of their Internet, combined with the amount of mail being migrated makes the process incredibly slow or causes a bottleneck on their Internet connection. Some see the issue post migration when all of their staff connect their Outlook clients to their Office 365 mailbox and start running other cloud based Office 365 products as well. Use the recommended Microsoft tools to ensure you have the appropriate bandwidth to migrate to and run Office 365

5. Choosing the wrong migration strategy

Choosing the right migration for your organization is critical. Review the different migration options and assess them against your current infrastructure, and understand the limitations of each option. For example, a cutover migration may seem like the best solution but if you do not have adequate bandwidth it could take too long to complete. Or you may decide to perform an IMAP migration, but understand this does not migrate Calendar, Contact and Tasks.

6. Staff disruptions

Make sure you keep your staff advised and informed about upcoming changes and disruptions.Provide staff training prior to any changes to reduce the amount of support calls you may receive post migration. Provide staff with clear instructions for any tasks you need them to perform.

7. Timing the cutover

When it comes time to redirect your mail-flow to your new Office 365 environment, the last thing you want to do is schedule the cutover for Monday afternoon and bear the brunt of angry staff all asking you why they are not receiving email. Usually the best time for a cutover is Friday afternoon but it could be different for your organization. Also ensure to adjust the TTL on your DNS records to speed up the change and resync any mail from your old system post cutover.

Considering Migrating to Office 365?
Speak to the experienced team at Stanfield IT on 1300 910 333