365 Command Exchange Migrator – Getting Started Guide

STEP 1: Ensure the Exchange Migrator prerequisites are met

System RequirementsThe Exchange Migrator has the following base requirements: Outlook 2010 or 2013 (fully patched with latest updates) installed on machine running the Migrator PowerShell 2.0 or higher The Office 365 Administrator account specified must have a full mailbox license We do not recommend running the Exchange Migrator on the Exchange server directly or older

operating systems such as Windows XP or Windows 2003 server.  It is typically best to install the Exchange Migrator on a workstation running Windows 7 or Windows 8.  A system with a solid state drive (SSD) will also offer some performance improvement when importing data into Office 365.

If Office365 AD sync is already configured in your environment, it is possible that you will experience difficulties authenticating while importing to Office365.  As a workaround, please attempt to import from a machine either not joined to your domain or outside of your network

STEP 2: Ensure you have the latest version of the Exchange Migrator

STEP 3: Ensure you have Admin Account Access Ensure the local Admin account has a mailbox on the local Exchange server and has full access to

the mailboxes being migrated.  Note the Exchange Migrator populates the list of available source mailboxes by reading the Active Directory.  It does not verify the Admin account has access to the mailboxes.

Ensure the admin account specified to connect to Office 365 is a global administrator in Office 365 with a full mailbox license assigned.  

STEP 4: Ensure Outlook is Configured

Verify that you can manually create an Outlook profile to connect to the local Exchange server on the Exchange Migrator workstation using the local admin account specified.  If you can connect to the local Admin mailbox, try and add the user you are attempting to migrate as an additional mailbox in the admin's Outlook profile.  This will confirm that the admin account has the necessary permissions to migrate the user's mailbox.

Verify you can manually configure an Outlook profile on the workstation the Exchange Migrator is installed on for the admin account being used to connect to Office 365.  Manually setting up a profile will confirm that the auto-discover process is working and connectivity to Office 365 is working.

STEP 5: Take a Demo

Before ordering we recommend you download a full version to preview and make sure it fits your organization’s needs.

No license key is required to demo a full version of Exchange Migrator. Migrate up to 15 ‘items’ using the demo mode.

1

STEP 6: Ensure you have an Exchange Migrator License Key File

Download an Exchange Migrator license key from the Client Management page in the MSP portal. After adding an Office 365 tenant to 365 Command, you will have access to a ‘Migrate Button’ and menu. Select Download Migrator License Key.

Exchange Migrator FAQWhat is the 365 Command Exchange Migration Tool for Office 365?

The 365 Command Exchange Migration tool is a time saver for on-premises Exchange to Office 365 mailbox migrations. It is an easy to use downloadable software. Exchange migrator is cloud Migration automation tool with everything an MSP needs to complete on premises Exchange mailbox to Office 365 mailbox migrations and unlike competitors comes with 1-year of enhanced Office 365 monitoring and reporting service - and costs less that ½ of competitor products.

Why are MSPs using the 365 Command Exchange Migration Tool for Office 365?

Today, MSPs are losing revenues and having margins reduced by customers moving to the Office 365 Cloud. The margins MSPs once got for on-premises Exchange Servers is gone. Replaced by lower Cloud services margins. You can get those lost revenues and margins back with an Office 365 Migration service.

What can I Migrate?

The Exchange Migrator can do migrations from on-premises Exchange to Office 365 quickly and easily. Supports migrations from Exchange 2003 and higher.

How do Migrations work?

The way it works is different than most other migration tools in that it runs on premise, pulls the mail out of the local Exchange server and then pushes it to the Office 365 mailbox. 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. The Office 365 Exchange Migration Tool 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.

What can I expect with regards to Exchange Migrator speed?

Even on a fast connection the most you will be able to upload running a single instance of the Exchange Migrator is around 500 MB – 1 GB per hour. This is primarily due to throttling imposed by Office 365. In order to get more upload speed, you must dedicate multiple systems to the upload process and each should be configured with its own Office 365 Admin account, which will reduce the likelihood of running into throttling issues. For exporting messages from Office 365 to PST files, the speed will typically be around 1 – 2 GB per hour. Again the main limitation is throttling in Office 365.

What are the requirements to run the Migration software?

Requirements to run the software are Outlook 2010, or 2013; PowerShell 2.0; The Office 365 Administrator account specified must have a mailbox

What other Features are included?

Export Office 365 Mailboxes to PST files for easy backup.

2

How can I try the 365 Command Exchange Migration Software?

Before ordering we recommend you download a full version to preview and make sure it fits your organization’s needs.

Exchange Migrator – First Use Instructions

Export Mailboxes to PST from Exchange Server

Step 1: ‘Export Mailbox to PST from OnPremise Exchange’

-> Select the radial button

->Select the ‘Next’ button

3

Step 2: Enter your OnPremise Exchange details and credentials

->Select the ‘Next’ button

The Username specified must have full access to the mailboxes being migrated.   The domain is the Active Directory domain name (the UPN domain name) the account is in The Password is the Active Directory Password. You be domain joined to use the Migrator (same domain as Exchange server/domain controller)

Step 3: Select Mailboxes to Export

->Select the ‘Select Mailbox’ button

4

Step 4: Highlight mailboxes to Export to PST

->Select the ‘Select Mailbox’ button

Step 5: Select Export Directory

->Select the ‘Select Export Directory’ button

-> Select location to store exported PSTs

-> Select OK

5

Step 6: Add mailboxes to the Export Queue

->Select the ‘Select Mailbox’ button

6

Step 7: Start Mailbox to PST Export

Select the ‘Start Export’ button

Step 8: Processing

7

Step 9: View Results

Step 10: View Logs

8

Select Log Link

Import PST Mailboxes to Office 365Step 1: Import mailbox PST to Office 365

Select Radial Button Select Next

9

Step 2: Import mailbox PST to Office 365

Enter Office 365 Global Admin Credentials Select Next

10

Step 3: Select Mailboxes to Import

11