Microsoft Office Tutorials and References
In Depth Information
Third-party migration tools
Third-party migration tools
If for some reason the existing tools and options provided by Microsoft do not meet your
migration needs, there are always third-party tools you can turn to. Examples of third-party
Exchange migration tools are Quest Software, Binary Tree, BitTitan, Cemaphore, and
Metalogix. Exchange is a mature platform and has been around for some time. Therefore,
thirdparty tools are readily available and are just as mature.
Migration best practices
There are several best practices when migrating mailboxes. We will list some of the
common ones you should consider adopting when migrating mailboxes from on-premises mail
servers to Exchange Online.
Reduce the TTL for MX records
In most scenarios, you will want to route incoming email to Exchange Online. Therefore, before
starting any of the migration tasks, regardless of whether it is a cutover, staged, or IMAP
migration, change the Time To Live (TTL) of your MX records so as to improve the DNS convergence
time when you do switch your MX records. The recommendation is that you change the TTL to
3,600 seconds, which is one hour.
Migration performance
There are many factors that affect migration performance, such as the size and number
of items in the mailboxes, network bandwidth, network latency, and the on-premises mail
servers. Migration performance can also be affected by the time of day and the number
of users on the network. That is why you should carry out migrations after the work day
is done or over weekends. As an example, after initial tests with a small staged migration
batch, Microsoft Consulting Services generally aims to ramp up to a migration rate of 1,000
mailboxes a week, mostly conducted after business hours when network utilization is at the
lowest level.
As we mentioned in Chapter 2, “Planning and preparing to deploy Office 365“, bandwidth
is not necessarily the only factor. Latency and sustained throughput are factors that are just
as important when it comes to migration performance. For an idea on how much
throughput is required for the different types of migration options we covered in this chapter, refer
to the Migration Performance white paper referenced in the following Inside Out sidebar. In
the Migration Performance white paper, an important metric to note is that past experience
has shown that a 5 GB to 10 GB per hour rate of data migration can be reliably achieved,
but depends on the Internet connection.
Search JabSto ::

Custom Search