Ways to migrate multiple email accounts to Office 365

Your organization can migrate email to Office 365 from other systems. Your administrators can migrate mailboxes from an Exchange Server or from migrate email from another email system. And your users can import their own email, contacts, and other mailbox information to an Office 365 mailbox created for them. Your organization also can work with a partner to migrate email.

Before you start an email migration, review limits and best practices for Exchange Online to make sure you get the performance and behavior you expect after migration.

See Decide on a migration path for help with choosing the best option for your organization.

You can also view an overview video:

Your browser does not support video. Install Microsoft Silverlight, Adobe Flash Player, or Internet Explorer 9.

Migrate mailboxes from Exchange Server

For migrations from an existing on-premises Exchange Server environment, an administrator can migrate all email, calendar, and contacts from user mailboxes to Office 365.

An administrator performs a staged or cutover migration to Office 365. All email, contacts, and calendar information can be migrated for each mailbox.

There are three types of email migrations that can be made from an Exchange Server:

  • Migrate all mailboxes at once (cutover migration)   

    Use this type of migration if you're running Exchange 2003, Exchange 2007, Exchange 2010, or Exchange 2013, and if there are fewer than 2000 mailboxes. For an overview of cutover migration, see What you need to know about a cutover email migration to Office 365. You can perform a cutover migration by using the Setup wizard, or by starting from the Exchange admin center (EAC). If you want to use the EAC, see Perform a cutover migration to Office 365. See Use the Office 365 Setup wizard to perform a cutover migration to migrate during the setup (note that you might not see the same setup experience as in the topic, if not, use the EAC method).

    Important: The Setup wizard is limited to migrating 150 mailboxes only.

    If you start the cutover migration from the EAC, you can move up to 2000 mailboxes, but due to length of time it takes to create and migrate 2000 users, it is more reasonable to migrate 150 users or less.

  • Migrate mailboxes in batches (staged migration)   

    Use this type of migration if you're running Exchange 2003 or Exchange 2007, and there are more than 2,000 mailboxes. For an overview of staged migration, see What you need to know about a staged email migration to Office 365. To perform the migration tasks, see Perform a staged migration of Exchange Server 2003 and Exchange 2007 to Office 365.

  • Migrate using an integrated Exchange Server and Office 365 environment (hybrid)   

    Use this type of migration to maintain both on-premises and online mailboxes for your organization and to gradually migrate users and email to Office 365. Use this type of migration if:

    • You have Exchange 2010 and more than 150-2,000 mailboxes.

    • You have Exchange 2010 and want to migrate mailboxes in small batches over time.

    • You have Exchange 2013.

    For more information, see Plan an Exchange Online hybrid deployment in Office 365.

Use Office 365 Import Service to migrate PST-files

If your organization has many large PST files, you can use the Office 365 Import Service to migrate email data to Office 365.

An administrator migrates PST files to Office 365.

You can use the Office 365 Import Service to either upload the PST files through a network, or to mail the PST files in a drive that you prepare.

For instructions, see Office 365 Import Service.

Migrate email from another IMAP-enabled email system

You can use the Internet Message Access Protocol (IMAP) to migrate user email from Gmail, Exchange, and other email systems that support IMAP migration. When you migrate the user's email by using IMAP migration, only the items in the users' inbox or other mail folders are migrated. Contacts, calendar items, and tasks can't be migrated with IMAP, but they can be by a user.

IMAP migration also doesn't create mailboxes in Office 365. You'll have to create a mailbox for each user before you migrate their email.

An administrator performs an IMAP migration to Office 365. All email, but not contacts or calendar information, can be migrated for each mailbox.

To migrate email from another mail system, see Migrate your IMAP mailboxes to Office 365. After the email migration is done, any new mail sent to the source email isn't migrated.

Have users import their own email

Users can import their own email, contacts, and other mailbox information to Office 365. See Migrate email and contacts to Office 365 for Business to learn how.

A user can import email, contacts, and calendar information to Office 365.

Work with a partner to migrate email

If none of the types of migrations described will work for your organization, consider working with a partner to migrate email to Office 365.

Method

Description

Use third-party migration tools to migrate mailboxes to Office 365

Use a third-party email migration tool

Migration tools can help speed up and simplify email migration. You'll find a list of tools in the Office 365 Marketplace.

Hire a partner to help you deploy Office 365

Hire a partner to help migrate your email

You'll find a list of partners in the Office 365 Marketplace.

See Also

Use PowerShell for email migration to Office 365

Share Facebook Facebook Twitter Twitter Email Email

Was this information helpful?

Great! Any other feedback?

How can we improve it?

Thank you for your feedback!

×