Connect with us

For PC

Office 365 Migration Performance And Best Practices

Published

on

Office 365 Migration

If you are planning to move your organization’s email to the manager user account of Office 365, you can make use of the Office 365 migration. Keep in mind that you can only migrate a maximum of 2000 mailboxes located in your on-premises Exchange organization to the Office 365, through the use of a cutover migration option. With best practices in 365 migration, you should be able to avoid issues such as network performance factors, and mitigation performance factors.  The following are some top best practices you should stick with.

Best Practices for Improved System Performance

Data extraction can be a very intensive task, for this reason, you should monitor your system performance through a pilot migration test. If the system indicates that it is busy, Microsoft recommends that you should avoid any form of aggressive migration schedule for the specific system to avoid slow service availability issues.

You may want to enhance source system performance by simply adding some hardware resources and by moving tasks and users to other servers that are not involved in migration, to reduce the load system.

Best Practices for Backend Tasks

Some backend tasks are running during the migration process. Though one of the best practices for Microsoft platform migration planning, is to perform any migration after hours, it is quite common to notice migration conflicts with some maintenance tasks such as data backup running on-premises servers.

The best way to handle this situation is to review other systems that might be running during the migration process. Experts do recommend that you should perform migration only when there are no other resource-intensive tasks are running. Make sure you perform an exchange store maintenance plus backup solutions if you are using the on-premise exchange.

The Throttling Policy

It is very important to protect an organization’s email systems through throttling policy that will normally set a limit to how fast and how much of an organization’s data can be extracted from the system within a specific period of time.

The best practice for this is to conduct the verification on your organization’s throttling policy, that has been deployed for your email system. For instance, Google Mail has a limit on the total amount of data that can be extracted within a specific period. Depending on the existing version of Throttling Policy, Microsoft Exchange has a policy that restricts the IMAP access over the HTTP Protocol access, for security reasons. To check your Throttling setting within Exchange 2013 edition, simply run the “GetThrottlingPolicy cmdlet”.

Conclusion

Many people often consider having a separate server for Office 365 migration but in actual sense, there is no need for such. You should consider using the Windows PowerShell feature to specify your Migration concurrency- for instance, you may want to set this at 20 mailboxes, as your default.  The best practices for migration performance are not only geared towards ensuring smooth migration on Office 365, but they are also geared towards ensuring a secured migration without disrupting all other activities on the system, over some time.

Continue Reading
Click to comment

Leave a Reply

Your email address will not be published. Required fields are marked *