MessageOps Office 365 Exchange Migrator gives administrators the ability to perform several types of migrations to and from Office 365. The supported scenarios are:
- PST Import to Office 365 Mailbox
- PST Export from Office 365
- On Premise Public Folder to Office 365 mailbox migration
- On Premise Exchange mailbox to Office 365 mailbox migration
When migrating to Office 365, you can choose to have the data imported into the user’s mailbox or archive. When exporting, you can export the mailbox and archive.
MessageOps Office 365 Exchange Migrator connects to the local Exchange servers using MAPI, so there is no need to enable RPC over HTTP, which the native migration tools from Microsoft require.
Requirements
- Office 2007 or Office 2010 (32 Bit)
- PowerShell 2.0
- The Office 365 Administrator account specified must have a mailbox
Usage
Importing PST Files to Office 365
MessageOps Office 365 Exchange Migrator works best for importing PST files if you have the PST files centralized. If the PST files are on the end user workstations, you may find MessageOps PST Importer a better solution.
If you have a large number of PST files to import, you will likely want to devote several workstations to the task. It’s recommended that you create an Office 365 Admin account, with a mailbox, for each instance of the Exchange Migrator you are running. If you run multiple instances using the same Administrator account, you could run into throttling imposed by Office 365.
To begin the PST import, launch the application and select the Import PST files option

Next enter your Administrator Credentials for Office 365. This account must have a mailbox.

The next screen allows you to add PST files to an import queue and specify the import options.

The first thing you’ll want to do is select the PST file you want to import by clicking the Select PST File button and browsing to the PST file. You then must select which mailbox you want the PST imported into by clicking the Select Mailbox button.
You then have several options to decide on.
Address Rewriting
Address rewriting will rewrite the Native Exchange email address format (for example EX: /o=First Organization/ou=first administrative group/cn=Recipients/cn=UserName’) which are only valid in the source Exchange organization to the SMTP address for the address entry if it can found within other message properties or resolved by looking at the Global Address List based on the Display Name of the recipient. Note because this is an automated processes exact address matching can never be 100% assured if GAL resolution is used and more than 1 contact has the same display name.
Thread Control
In most cases these shouldn’t be modified, but here is what these settings control.
Max Threads – The number of simultaneous TCP connections to Exchange. The Exchange server will throttle any more than 10 simultaneous connections.
Batch Size – The total number of message that will be sent in one batch. The actual batch size will depend on the size of the messages in the batch.
Destination
The Destination is simply whether you want to import the PST data to your mailbox or archive.
Destination Root
The Destination Root controls whether a new folder is created for the PST data. When PST Name as Root is selected, a top level folder will be created in the mailbox and the PST data will be copied to that folder. As an example, if the PST name was Matt Backup, and the PST Name as Root is selected, the import would create a top level folder called Matt Backup and the PST data would be restored beneath that folder.

If the Root of Store option is selected, the top level folders of the PST files will be restored to the top level of the mailbox or archive. So the Inbox of the Matt Backup PST file will be placed in the Inbox folder of the mailbox.
Error Processing
If the Ignore Single Property Errors is checked, if a property on a message is corrupt, the message will still be uploaded.
Add to Import Queue
Once you have the PST file and Mailbox Selected, you can add it to the Import Queue.

Once added to the queue, you can add more items to the queue or click Start Import to import the queue.

When the import is running, you can see the progress and click the log link to open the log file in Notepad.

Exporting Office 365 Mailboxes to PST Files
To begin the PST Export, launch the application and select the Export PST option

Next enter your Administrator Credentials for Office 365. This account must have a mailbox.

Once authenticated, you can click the Select Mailbox button to display a list a of mailboxes in your organization, along with the mailbox and archive size for each one. Select the mailbox, or group of mailboxes, you want to export.

Once a mailbox, or group of mailboxes, is selected you can choose to export the mailbox, archive, or both. In the File Options area click the Select Export Directory button to define where the PST files should be exported to.
You can either create a new PST file or use an existing PST file. If you choose an existing PST file, it will not import duplicate items (assuming the PST file was created by Exchange Migrator). You can use the existing PST option to resume a failed or interrupted migration.
Once the options are selected click the Add to Export Queue button to queue up the exports. If you are ready to export the archive, click the Start Export button.
When the export starts, you’ll be prompted for a username and password. Enter the Office 365 Administrator username you entered previously and check the box to remember the credentials. You must check the box to remember the credentials when prompted or the export won’t work.
During the export the progress is displayed. If you need additional information, click on the Log Link for the user to get a detailed log.

Migrating On Premise Exchange Mailboxes to Office 365
MessageOps Office 365 Migrator supports migrations from Exchange 2000 and higher.
To begin the Mailbox Migration, choose the From On Premise Exchange Option and click Next.

Next you must provide the following information.

When migrating from Exchange 2000 or 2003, the Exchange Server should be the server that the mailboxes reside on. When migrating from Exchange 2007 or 2010 the Exchange Server should be a Client Access Server.
The Username specified must have full access to the mailboxes being migrated. The domain is the Active Directory name name the account is in and the Password is the Active Directory Password.
Next enter your Administrator Credentials for Office 365. This account must have a mailbox.

The next screen allows you to add mailboxes to an import queue and specify the import options.

The first thing you’ll want to do is select the source mailbox you want to import by clicking the Select Mailbox button and choosing the mailbox. You then must select which Office 365 mailbox you want the source mailbox imported into by clicking the Select Mailbox button in the Destination Mailbox options area.
You then have several options to decide on.
Address Rewriting
Address rewriting will rewrite the Native Exchange email address format (for example EX: /o=First Organization/ou=first administrative group/cn=Recipients/cn=UserName’) which are only valid in the source Exchange organization to the SMTP address for the address entry if it can found within other message properties or resolved by looking at the Global Address List based on the Display Name of the recipient. Note because this is an automated processes exact address matching can never be 100% assured if GAL resolution is used and more than 1 contact has the same display name.
Thread Control
In most cases these shouldn’t be modified, but here is what these settings control.
Max Threads – The number of simultaneous TCP connections to Exchange. The Exchange server will throttle any more than 10 simultaneous connections.
Batch Size – The total number of message that will be sent in one batch. The actual batch size will depend on the size of the messages in the batch.
Destination
The Destination is simply whether you want to import the mailbox data to your mailbox or archive.
Destination Root
The Destination Root controls whether a new folder is created for the source mailbox data. When Separate Folder is selected, a top level folder will be created in the mailbox and the source mailbox data will be copied to that folder. As an example, if the mailbox name was user@domain.com, and the Separate Folder is selected, the import would create a top level folder called user@domain.com and the mailbox data would be restored beneath that folder.
If the Root of Store option is selected, the top level folders of the source mailbox will be restored to the top level of the Office 365 mailbox or archive. So the Inbox of the source mailbox will be placed in the Inbox of the Office 365 mailbox.
Error Processing
If the Ignore Single Property Errors is checked, if a property on a message is corrupt, the message will still be uploaded.
Add to Import Queue
Once you have the Source Mailbox and Office 365 Mailbox Selected, you can add it to the Import Queue.

Once the mailboxes are queued for import, click the Start Import button to start the mailbox migrations.
When complete, the results will be displayed, and you can click the LogLink column to view a detailed log for each user.

Migrating On Premise Public Folders to Office 365
MessageOps Office 365 Exchange Migrator gives you the ability to import Public Folder data into Shared Mailboxes in Office 365. Before attempting to import Public Folders into Office 365, ensure you have an account which has access to the Public Folders.
To begin the migration, select the From On Premise Public Folder Tree option.

Next you must provide the following information.

When migrating from Exchange 2000 or 2003, the Exchange Server should be the server that the mailboxes reside on. When migrating from Exchange 2007 or 2010 the Exchange Server should be a Client Access Server.
The Username specified must have full access to the mailboxes being migrated. The domain is the Active Directory name name the account is in and the Password is the Active Directory Password.
Next enter your Administrator Credentials for Office 365. This account must have a mailbox.

The next screen allows you to select the Public Folders that will be migrated to the Office 365 mailboxes.

Click the Select Folder Button to bring up a list of Public Folders

Select the folder you wish to copy and click OK.
You must then select which mailbox you want to copy the Public Folder data to. Click the Select Mailbox button and select the Mailbox. Then click the Add to Import Queue button to add the folder to the import queue. Repeat the procedure if you have more folders to import.

Click the Start Import button to begin the import.
Troubleshooting
The best place to start is with the log files. Detailed log files are kept in the c:\users\username\MessageOps directory. The most common problems are:
- Messages that are too large to import. The Message Size limit in Office 365 is 30 MB. Messages over 25 MB can’t be uploaded. Those messages are placed in a directory named OverSize in the log file directory.
- Throttling. If you are importing or exporting messages with Office 365, you’ll realize it’s a slow process. The reason is because the connection is throttled by the Office 365 servers. If you have a lot of data you want to move, you’ll need to devote multiple workstations to the task. Each workstation should use a separate Admin account to sign into Office 365.
Pricing
The preferred payment method is to designate MessageOps as your Partner. The process is detailed on the Setting MessageOps as your Partner page. This doesn’t cost you anything and allows MessageOps to be paid by Microsoft. Once MessageOps is set as your partner, follow this link and request a license key.
If you do not want to set MessageOps as your Partner, the Exchange Migrator can be purchased as part of the MessageOps PST Bundle. The price is $99 per Office 365 Tenant and includes the PST Importer and Exchange Migrator. Click here for purchase details.
Download
This content is available to members only. Anyone can become a member for free!
Login or Become a member
[Guarded by Wordpress membership plugin - Membership Sites Builder - MemberWing - Advanced Membership site software]
Connect &
Network with us: