Exchange to Office 365 Migration: 6 Best Practices

Since Office 365’s market debut in 2011, moving from Exchange to the cloud productivity suite is one of the most frequent migrations performed each year. Despite its popularity, each migration project is different and presents unique challenges before, during, and after the move.

In a recent webinar, BitTitan Senior Technology Strategist Lauren Brunson walked through six best practices for this specific source to destination path. This includes a host of factors like migration type, Outlook configuration, as well as ways to avoid downtime and maintain security throughout the transition.  For those who missed it, that webinar and all others from BitTitan can be found on-demand here. Let’s get to it!

1. Impersonation v. Delegation

An early decision service providers will need to make is between impersonation and delegation. It’s important to understand the differences between the two and where each makes the most sense. Delegation consists of logging into individual user mailboxes using an admin account that has full access rights to each mailbox. Impersonation, on the other hand, means the admin will have the ability to impersonate each user when performing the migration and can use credentials in email to scan or copy data without needing passwords in the mailbox process.

For large-scale migrations or “hot cut” moves (more on this later), impersonation is often faster and can help combat throttling. For moves to or from Office 365, we highly recommend impersonation; however, BitTitan’s MigrationWiz supports delegation as well.

2. Understanding Data Speeds

Like fine wine, whiskey, and cheddar cheese, migrations don’t happen overnight. A wide range of variables affect the speed of a migration, making the overall time difficult to predict. These factors include source, system load, internet bandwidth, and even folder structure. Cloud providers like Microsoft and Google have their own throttling limits, which don’t do IT teams or service providers any favors, especially if expectations haven’t been set as to the true duration of the migration. That said, there are ways to adjust those limits. For Exchange to Office 365 moves, we see average speeds around 750MB per user, per hour, with the high end at 1.25GB and the low end at 250MB. Performing a smaller trial move with a handful of mailboxes – always a good pre-migration step – is a good litmus test for the pace of the larger project.

3. Hot Cut or Cool Phase?

This is about as hip as migrations get. Believe us, we’ve been trying to make it cool for years.

A “hot cut,” also known as a “quick switch,” is best for customers on a tight timeline who need to be live in the destination environment from day one. In this scenario, users are moved over with the last 90 days of data and then MX records are updated to direct mail flow to the new destination. IT can go back and copy or backfill the rest of the data prior to those 90 days while the users are live on the destination to prevent any downtime.

If a quick switch isn’t ideal, another option is a phased migration, which offers the greatest returns on larger projects with a lengthier timeline. In this case, users are moved over in batches rather than all at once. Phases are often determined by department, seniority, network dependencies, or other factors that make the most sense for the end users.

4. Avoiding User Interruptions

Regardless of method, an important goal when performing migrations is to limit downtime. Nearly every project produces some kind of error – identifying what that problem is and how to remedy it is crucial for overall success.

MigrationWiz is a copy and paste migration tool, meaning it creates a mirror image of the mailbox and keeps a log file of each message ID copied onto the destination. This helps pinpoint errors, improve tracking, and identify missing items post-migration.

To avoid further disruptions, MigrationWiz leaves a watermark copy on each mailbox. If only the most recent 90 days’ worth of data is moved, MigrationWiz recognizes that and starts migrating things before that timeframe in the next phase. It’s also customizable by time, data type, calendar, contacts, and more to avoid duplicating or losing data. Since the tool isn’t extracting data from the source, there’s no disruption to the end user and data speeds increase since the whole mailbox doesn’t have to be scanned.

5. Leveraging DMA and DeploymentPro

If you’re migrating from Exchange to Office 365 using MigrationWiz, two other tools help make assessing and configuring Outlook a breeze.

The first is a lightweight Device Management Agent (DMA) available as both a client or gateway to collect detailed information about your customer’s computers such as name, users, OS version, memory, and more. This enables a proper assessment of the pre-migration environment and gauges the ability to execute the move. While the DMA client gathers data on the computer it is installed on, the DMA gateway also performs a discovery scan of the customer’s Active Directory for items like servers, computers, users, and groups.

The second tool, DeploymentPro, is a module within that DMA to help configure Outlook email profiles to send and receive email from Office 365. After the cutover date is decided, IT will schedule the date/time in DeploymentPro. When that time comes it sends a heartbeat from our UI to the agents to flip the profile. When that occurs, it does the following:

  • Creates a new mail profile (can bypass Autodiscover)
  • Attaches any existing locally-stored PSTs from the current default mail profile
  • Copies over signatures from the current default profile;
  • Copies over autocompletes from the current default mail profile

6. Enabling Advanced Options

Because there are so many variables in each migration project, having access to deep customization options is crucial to keeping the project on track. Notification settings scratch the surface here, keeping project stakeholders aware of migration progress while helping identify and remedy errors as they arise. Notifications also relieve project owners from sitting and monitoring the entire migration, enabling them to focus on other work while MigrationWiz runs in the background.

Customization settings should also include a filtering option to target specific folder sets, subfolders in an inbox, or unselect items like deleted folders that may not need to be migrated. The advanced options section is where the impersonation v. delegation call can be made, as well as audit log options for more detailed reports and performance settings.

For your next move to Office 365, check out BitTitan’s User Migration Bundle. This combines the most popular workloads – mailboxes, documents, and archives – into a single 12-month license with Outlook configuration. For more technical information on Exchange to Office 365 moves, head on over to the BitTitan Knowledge Base.

Happy migrating!

 

About the author

Grady Gausman

Grady Gausman is a staff writer for the Bits & Bytes blog.

Leave a Reply

Be the First to Comment!

avatar
  Subscribe  
Notify of