Vous êtes sur la page 1sur 35

eMail Migration

to Office 365

Michael Lopez
Sales Enablement
LATAM

1
Overview
This presentation covers the simple migration options available with
Exchange Online, which are:
IMAP migration
Cutover Exchange Migration
Staged Exchange Migration

2
Simple Migrations

3
Summary of Migration Options

* Additional options available with tools from migration


partners

4
Migration Option Decision
Factors

5
In EAC, select
recipients |
migration

Migration Tool
Launched
from
the Exchange
Admin Center

Start migration
wizard

Choose
migration type
and follow
prompts

6
Migration Tool is also Available via
PowerShell
Set of Migration
Cmdlets
New-MigrationBatch
Start-MigrationBatch
Get-MigrationBatch
Get-MigrationStatus
Complete-Migration
Test-
7
MigrationServerAvailability
IMAP Migrations

8
IMAP Migration Features and
Benefits
Works with a large number of source mail systems
Works with on-premises or hosted systems
Users can be migrated in batches
On-premises migration tool is not required

9
IMAP Data Migration Scope

10
IMAP Migration Flow

11
Cutover Exchange
Migration (CEM)

12
CEM Features and Benefits
Simple and quick migration
High-fidelity migration solution
Typically best suited to small and medium organizations
Users are provisioned automatically during migration
Works with Exchange 2003 and newer
Works with on-premises or hosted Exchange systems
Identity management in the cloud (at least initially)
On-premises migration tool is not required

13
CEM Requirements and
Limitations
Can only migrate 2000 mailboxes in total (hard limit)
Outlook Anywhere enabled and available on source system
(must have SSL certificate issued by a public CA)
Migration Account requires Full Access or Receive-As permissions
to all mailboxes that will be migrated
Directory Sync disabled in Office 365 tenant
SMTP domains configured in Office 365 tenant prior to migration

14
Cutover Exchange Migration Architecture

15
CEM Accounts and Passwords
Account Provisioning:
Migration creates users, mailboxes, DLs and contacts
Migration enables reply-ability to migrated messages
(i.e. provisioning process brings over the Legacy DNs)

Passwords:
No access to passwords from source directory
New passwords created for all users
A link to download passwords is sent to admin
Users must change password on their first login

16
CEM Data Migration Scope

17
CEM End User Experience
Admin needs to distribute new passwords to users
Users need to create a new Outlook profile
All mail is downloaded from the Office 365 mailbox
(i.e. the OST file must be recreated)
Any client side rules, settings, and customizations need to be
recreated again

18
CEM Migration Flow

19
Staged Exchange
Migrations (SEM)

20
SEM Features and Benefits
Simple and flexible migration solution
High-fidelity migration solution
Typically best suited to medium and large organizations
Users are provisioned with DirSync prior to migration
No limit on the number of mailboxes you can migrate
Users can be migrated in batches (up to 1000 per batch)
Works with Exchange 2003 and 2007 only, on-premises or hosted
Identity management on-premises
On-premises migration tool is not required

21
SEM Requirements and
Limitations
Outlook Anywhere service configured and enabled on source
system
(must have SSL certificate issued by a public CA)
Migration Account with Full Access or Receive-As permissions to
all mailboxes that will be migrated
Directory Sync enabled in the Office 365 tenant
Directory Sync tool deployed On-Premises
SMTP domain(s) configured in the Office 365 tenant
Does not work with Exchange 2010 and higher

22
Staged Exchange Migration
Architecture

23
SEM Accounts and Passwords
Account Provisioning:
For every on-premises mailbox to be migrated there needs to be a
corresponding user in Office 365
DirSync is responsible for provisioning these objects for you

Passwords:
Directory Synchronization can synchronize password hashes from the on-
premises Active Directory environment to Office 365 if configured
Or the administrator chooses to create new passwords in the .csv file used
during the migration and then force these to be changed at first logon
With the second approach, users end up with two sets of credentials, one for on-
premises and one for Office 365

24
SEM Batch File
CSV column format
EmailAddress, Password, ForceChangePassword
One user per line
Max of 1000 users in each CSV
Smart-check performed against the Office 365 directory

25
SEM Data Migration Scope

26
SEM Migration Mail Flow
When you start the migration, all mail flows to on-premises
During the migration process, the migration service sets the
TargetAddress attribute on the on-premises mailbox so that email
forwards to the appropriate Exchange Online mailboxes
The TargetAddress is set to the Exchange Online routing address
user@domain.onmicrosoft.com
All new messages will now be forwarded to the TargetAddress, which
resolves to the Exchange Online mailbox
New messages will not be copied to the on-premises mailbox that
remains, as such, the mailbox can be disconnected/deleted
Set the MX records to point to Exchange Online only after all mailboxes
have been migrated
27
SEM End User Experience
Two things happen after a mailbox is migrated via SEM:
A user has an on-premises mailbox and a cloud mailbox
Mail sent to the users on-premises mailbox is forwarded to their cloud
mailbox
For Outlook to successfully create a new profile against the cloud mailbox
using AutoDiscover you will need to convert the existing on-premises
mailbox to a mail enabled user or delete the mailbox
A script has been written to perform this conversion process
http://community.office365.com/en-us/w/exchange/845.aspx

28
SEM Migration Flow

29
Migration Options Summary
Migration
Method IMAP CEM SEM Hybrid

Protocol IMAP4 HTTPS HTTPS HTTPS


(Outlook Anywhere) (Outlook Anywhere) (Exchange Web Services)

Limits No limits, 50,000 2000 mailboxes total No limits, 1000 mailboxes per No limits
mailboxes per batch batch

Any IMAP4 system Exchange 2003 + Exchange 2003/2007 only Exchange 2010 SP3 +
Port 143 or 993 Outlook Anywhere configured Outlook Anywhere configured EWS and AutoD
Requirements Port 443 Port 443 configured
Public certificate Public certificate Port 443
Public certificate

OST Resync N/A Yes Yes No

Dirsync N/A No Yes Yes

Migration 10-15 GB per hour


10-15 GB per hour with 100 10-15 GB per hour with 100 15-50 GB per hour with
with 100 concurrent
concurrent moves concurrent moves 50 concurrent moves
Performance moves

30
Remote Move Migration (Hybrid)
A remote move migration is used to migrate on-premises Exchange mailboxes to Exchange
Online in an Exchange hybrid deployment. You must have an Exchange hybrid deployment
to use a remote move migration. With a hybrid deployment, you get the following
capabilities:
User account management in your on-premises organization.

Directory synchronization between your on-premises and Exchange Online


organizations.
Single sign-on to mailboxes located either on-premises or in the Exchange Online
organization.
Secure mail routing between on-premises and Exchange Online organizations.

Free/busy and calendar sharing between on-premises and Exchange Online


organizations.
Even if you plan to permanently move your on-premises email organization to Exchange
Online
31 and Office 365 over a longer period of time, you can take advantage of these hybrid
Which migration method is right for your
organization?
Existing organization
Number of mailboxes to
Do you want to manage
user accounts in your on- Migration type
migrate
premises organization?
Exchange 2013, Exchange
2010, Exchange 2007, or Less than 2,000 mailboxes No Cutover Exchange migration
Exchange 2003
Exchange 2007 or
Less than 2,000 mailboxes No Staged Exchange migration
Exchange 2003

Staged Exchange migration or


Exchange 2007 or More than 2,000
Yes remote move migration in an
Exchange 2003 mailboxes
Exchange hybrid deployment

Exchange 2013 or More than 2,000 Remote move migration in an


Yes
Exchange 2010 mailboxes Exchange hybrid deployment
Exchange 2000 Server or
No maximum Yes IMAP migration
earlier versions
Non-Exchange on-
premises messaging No maximum Yes IMAP migration
system

32
Q&A
2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it
should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation.
MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.