Solved

Exchange 2010 on-premise staged migration to Office 365

Posted on 2016-11-08
7
97 Views
Last Modified: 2016-11-20
Hi All,

Before stating this isn't supported please checkout this article that states it can be done:

http://www.michev.info/Blog/Post/85/Microsoft-will-eventually-support-Staged-migration-with-Exchange-2010-and-above

The following Powershell command runs fine:

New-MigrationBatch -Name StagedBatch -SourceEndpoint StagedEndPoint -CSVData ([System.IO.File]::ReadAllBytes(“C:\Migration\Staged.csv”))

However, when I add the required -SkipSteps parameter I receive an error message:

New-MigrationBatch -Name StagedBatch -SourceEndpoint StagedEndPoint -CSVData ([System.IO.File]::ReadAllBytes(“C:\Migration\Staged.csv”))  -SkipSteps SettingTargetAddress

The error message received being “Skipping the SettingTargetAddress step isn’t supported for this migration type”.

The documentation for the New-MigrationBatch command states that the “SkipSteps” parameter is supported for Staged migrations.

I require the SkipSteps parameter otherwise the Staged Migration fails on Exchange 2010.

The reason why I require a Staged migration rather than a cutover migration is because we're migrating the Exchange on-premise mailboxes to 10 different Office 365 tenants. Some will be AD sync'ed others will be cloud only accounts. I already have AAD Connect setup and sync'ing to the various different tenants using OU filtering.

Any ideas?

Thanks

Ken
0
Comment
Question by:khodgson
  • 3
  • 3
7 Comments
 
LVL 15

Assisted Solution

by:Todd Nelson
Todd Nelson earned 250 total points
ID: 41879650
This TechNet article doesn't say a staged migration is not supported with Exchange 2010, it says this...

You can’t use a staged migration to migrate Exchange 2010 or Exchange 2013 mailboxes to Exchange Online.

In Exchange 2010 and Exchange 2013, the TargetAddress property can't be modified. This is the reason that staged Exchange migration doesn't support migrating Exchange 2010 and Exchange 2013 mailboxes to Exchange Online.

Despite what the article states that you referenced, this is the "'official' statement detailing ... the exact reasons."

As I see it, you have a couple options available in your scenario: PST migrations or use of a third party tool like BitTitan MigrationWiz.
0
 
LVL 9

Assisted Solution

by:Marshal Hubs
Marshal Hubs earned 250 total points
ID: 41879919
As suggested by Todd Nelson You can also perform migration with the help of third party tools:

Migrationwiz: https://www.bittitan.com/products/migrationwiz/overview
Stellar: http://www.stellarinfo.com/email-repair/edb-pst-converter.php
etc
0
 

Author Comment

by:khodgson
ID: 41880085
If the -SkipSteps parameter worked then I wouldn't be modifying the TargetAddress and hence the migration would complete.

The issue with 3rd party tools is that a mailbox doesn't exist on the Office 365 side as the user accounts are listed as contacts rather than mailboxes.

I can bodge the process by running the staged migration, which fails after provisioning the mailboxes on the Office 365 side. This then enables me to use a 3rd party tool to migrate the mailboxes but I'd rather get the process working properly and ideally use the free Microsoft staged migration method.

I don't understand why Microsoft have offered the -SkipSteps parameter exactly for the purpose I require on staged migrations and then for it not to work?
0
Optimizing Cloud Backup for Low Bandwidth

With cloud storage prices going down a growing number of SMBs start to use it for backup storage. Unfortunately, business data volume rarely fits the average Internet speed. This article provides an overview of main Internet speed challenges and reveals backup best practices.

 
LVL 15

Assisted Solution

by:Todd Nelson
Todd Nelson earned 250 total points
ID: 41883924
I don't believe the SkipSteps parameter is available in Exchange 2010.  It is in 2013 and 2016, and is specifically for staged migrations that include Exchange 2003 and 2007 and cannot be applied to Exchange 2010.  Because ... "In Exchange 2010 and Exchange 2013, the TargetAddress property can't be modified."  If it can't be modified--which includes skipping the targetaddress--then SkipSteps cannot be used.

If you think that third party migration tools should automatically provision user accounts in O365, that thinking is wrong.  And if you think you can perform a staged migration from one on premises environment to 10 Office 365 tenants, that thinking is incorrect too.  Staged migrations, cutover migrations, and hybrid migrations are one-to-one migrations to a single Office 365 tenant only.
0
 

Accepted Solution

by:
khodgson earned 0 total points
ID: 41885987
I spoke with Microsoft support who confirmed the -SkipSteps feature is still under development for Exchange 2010 with relation to Office 365 staged migrations.

I therefore used AAD Connect to sync the user objects to Office 365, the staged migration process to provision the mailboxes in Office 365 (it then fails due to the TargetAddress issue and no data is migrated but can be safely cancelled at this point) and a 3rd party tool to migrate the data. This is working perfectly.

AADConnect supports multiple Office 365 tenants and Microsoft confirmed this approach will work fine.
0
 
LVL 15

Expert Comment

by:Todd Nelson
ID: 41888209
Good luck to you.
0
 

Author Closing Comment

by:khodgson
ID: 41894664
The Information provided appears to work, but could be useful for others to know if they research the site for the same issue
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Adoption of Microsoft’s Enterprise Mobility and Security solution and Office 365 will re-order the File Sync and Share market Microsoft has stated that its Enterprise Mobility + Security (EMS) is the fastest growing product in the history of the …
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
A company’s greatest vulnerability is their email. CEO fraud, ransomware and spear phishing attacks are the no1 threat to a company’s security. Cybercrime is responsible for the largest loss of money to companies today with losses projected to r…

860 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question