01-23-2023, 08:49 AM
There are four Office 365 migration types for you to consider.
1. Staged Migration
An Office 365 staged migration moves everything over in batches. It transitions all of your resource mailboxes and existing users from Exchange 2003 or 2007 to Exchange Online.
It’s a great method for medium-sized companies (especially those with over 2,000 mailboxes) that are currently using on-premises Microsoft Exchange 2003 or 2007. It is not, unfortunately, available for organizations using Exchange 2010 or 2013.
A staged migration moves mailboxes in batches over a determined period. It requires the use of the Directory Synchronization tool, which replicates your accounts from the on-premises Active Directory database. By the end of the process, all mailboxes will be hosted in Office 365.
During the migration, Office 365 users will still have the ability to send and receive emails from users that haven’t migrated over yet. The only resources users won’t be able to access are calendars and delegates.
2. Cutover Migration
A cutover migration is an immediate transition from an on-premises Exchange system to Office 365. All your resources are migrated at once, including mailboxes, contacts and distribution groups. With this migration, you cannot select specific objects to migrate, and once the move is complete, everyone will have an Office 365 account.
This Office 365 migration method is best if you’re currently using Exchange 2003, 2007, 2010 or 2013 and have less than 2,000 mailboxes. In fact, Microsoft recommends the cutover migration for companies with less than 150 users to the amount of time it takes to migrate so many accounts.
One thing to note: every user’s Outlook profile will need to be reconfigured to connect to Office 365.
3. Hybrid Migration
The Office 365 hybrid migration allows you to integrate Office 365 with your on-premises Exchange servers and your existing directory services. As a result, you can synchronize and manage user accounts for both environments.
With a hybrid migration, you’re able to move mailboxes in and out of Exchange Online. You can even pick and choose which mailboxes to keep on-premises and which to migrate to Office 365. Plus, you can synchronize passwords and introduce single sign-on to your team to make it easier to log in to both environments.
If you’d like to use a hybrid migration, you need more than 2,000 mailboxes. It’s also necessary to have Exchange 2010 or later. If you don’t, you must install at least one on-premises Exchange 2013 or Exchange 2010 Service Pack 3 (SP3) server to enable hybrid deployment connectivity.
4. IMAP Migration
While the other three Office 365 migration types depend solely on Exchange, an IMAP (Internet Message Access Protocol) migration allows you to transition users from Gmail or any other email system that supports IMAP migration.
An IMAP migration pulls information from your source mailboxes and hands it over to Office 365. However, IMAP migration doesn’t transition anything other than email. Calendar items, tasks and contacts all stay in the original inbox and have to be migrated manually by the user.
You’ll also have to create a mailbox for each user before initiating the email migration – something other migration types automatically create for you.
IMAP migrations have a limit of 50,000 total mailboxes and 5,000,000 items. And once the migration is complete, any new mail sent to the original mailbox won’t be.
1. Staged Migration
An Office 365 staged migration moves everything over in batches. It transitions all of your resource mailboxes and existing users from Exchange 2003 or 2007 to Exchange Online.
It’s a great method for medium-sized companies (especially those with over 2,000 mailboxes) that are currently using on-premises Microsoft Exchange 2003 or 2007. It is not, unfortunately, available for organizations using Exchange 2010 or 2013.
A staged migration moves mailboxes in batches over a determined period. It requires the use of the Directory Synchronization tool, which replicates your accounts from the on-premises Active Directory database. By the end of the process, all mailboxes will be hosted in Office 365.
During the migration, Office 365 users will still have the ability to send and receive emails from users that haven’t migrated over yet. The only resources users won’t be able to access are calendars and delegates.
2. Cutover Migration
A cutover migration is an immediate transition from an on-premises Exchange system to Office 365. All your resources are migrated at once, including mailboxes, contacts and distribution groups. With this migration, you cannot select specific objects to migrate, and once the move is complete, everyone will have an Office 365 account.
This Office 365 migration method is best if you’re currently using Exchange 2003, 2007, 2010 or 2013 and have less than 2,000 mailboxes. In fact, Microsoft recommends the cutover migration for companies with less than 150 users to the amount of time it takes to migrate so many accounts.
One thing to note: every user’s Outlook profile will need to be reconfigured to connect to Office 365.
3. Hybrid Migration
The Office 365 hybrid migration allows you to integrate Office 365 with your on-premises Exchange servers and your existing directory services. As a result, you can synchronize and manage user accounts for both environments.
With a hybrid migration, you’re able to move mailboxes in and out of Exchange Online. You can even pick and choose which mailboxes to keep on-premises and which to migrate to Office 365. Plus, you can synchronize passwords and introduce single sign-on to your team to make it easier to log in to both environments.
If you’d like to use a hybrid migration, you need more than 2,000 mailboxes. It’s also necessary to have Exchange 2010 or later. If you don’t, you must install at least one on-premises Exchange 2013 or Exchange 2010 Service Pack 3 (SP3) server to enable hybrid deployment connectivity.
4. IMAP Migration
While the other three Office 365 migration types depend solely on Exchange, an IMAP (Internet Message Access Protocol) migration allows you to transition users from Gmail or any other email system that supports IMAP migration.
An IMAP migration pulls information from your source mailboxes and hands it over to Office 365. However, IMAP migration doesn’t transition anything other than email. Calendar items, tasks and contacts all stay in the original inbox and have to be migrated manually by the user.
You’ll also have to create a mailbox for each user before initiating the email migration – something other migration types automatically create for you.
IMAP migrations have a limit of 50,000 total mailboxes and 5,000,000 items. And once the migration is complete, any new mail sent to the original mailbox won’t be.