[Last Call] Learn about multicloud storage options and how to improve your company's cloud strategy. Register Now

x
?
Solved

Exchange 2010 cutover migration to Office 365

Posted on 2016-10-23
12
Medium Priority
?
190 Views
1 Endorsement
Last Modified: 2016-11-08
I'm considering the cutover migration option for migrating from on premise Exchange 2010 to Office 365.  It seems pretty straight forward, however, during the time of the migration I would imagine user's mailboxes will be not accessible..  I plan to migrate to Office 365 and have the users use OWA to access their email for a few weeks to void using their Outlook clients.. The reason being their current domain, domain profile, and on premise Exchange server will go away..  They'll be moving to a new domain and new domain profile a few weeks after the migration.  Then I would create an Outlook profile on their new domain profile and pull down their mail via a department at a time..  So..  Back to my original concern..  It might take 3 or 4 days to migrate 300 GBs of emails...  Their internet circuit is 100mbps... But it's so hard to know how long it will take.  I'm trying to void email downtime on the weekdays..
1
Comment
Question by:gopher_49
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
  • 2
  • +2
12 Comments
 
LVL 7

Expert Comment

by:No More
ID: 41856036
You have also option to copy PST files to hard disk and send it to Microsoft Datacentre
0
 

Author Comment

by:gopher_49
ID: 41856051
Does the migration batch sync new email as they come in?  

Does it create all accounts in the migration batch first and then it syncs?  

If both are true I simply have it create the accounts, start the sync,  and once the sync is done change DNS.  I could even change DNS once the first sync cycle starts as long as the new mailbox is created and just let the mail sync.   The end users will be using OWA to check mail.
1
 
LVL 7

Expert Comment

by:No More
ID: 41856060
You are saying that, they are going to move to new domain and new domain profile
- Are you talking about new Web Domain and AD Domain ?
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
LVL 43

Assisted Solution

by:Vasil Michev (MVP)
Vasil Michev (MVP) earned 1000 total points
ID: 41856201
The Cutover migration method does not prevent users from accessing their existing on-prem mailboxes. It will periodically sync new messages every 24h, so you can have a fairly recent snapshot of the mailbox content. I'd suggest you review the TechNet documentation where this questions and more are detailed: https://technet.microsoft.com/en-us/library/jj898490%28v=exchg.150%29.aspx
1
 

Author Comment

by:gopher_49
ID: 41856211
I read some of the TechNet docs closely before seeing your response.. It sounds like the below steps will work..

Build the migration batch
Have it create the users and migrate the mailboxes
Let it run throughout the week
Once it seems to have finished the initial sync what to see the roll ups are catching up
Assign licenses on Office 365
Change TTL
Change MX record
Verify external mail is flowing
Leave sync running for in the event old DNS record result in old mail reaching the old mailboxes
Then stop/delete migration batch

The end users will be using OWA.. So.. No need to worry about Outlook profile right now..  Does this seems okay?  Also..  Once the leave the old domain, join the new one, and then log into the new domain profile..  I assume I need to add their Office 365 profile and pull the emails down?
1
 
LVL 43

Expert Comment

by:Vasil Michev (MVP)
ID: 41856250
The migration steps seem OK. Not sure how "changing the domain" part will work out, as they are many things to consider there. For starter, you will definitely want to verify the new domain in O365 and change the UPN and primary SMTP addresses to match it, in order to avoid user confusion and unnecessary login prompts.
1
 
LVL 9

Accepted Solution

by:
Lisa Hendrickson "CallThatGirl" earned 1000 total points
ID: 41856256
You can use MigrationWiz from BitTitan and start the migration process beforehand. It allows you to do it in date batches so the heaviness is not "so heavy". I only do small scale migrations, but it's nice. The day you cut over the mx records, you can do a final pass (delta pass I think it's called) and then you can run their deployment pro agent on the users computer and it sets up a new profile and does the aftercare (autocomplete, calendar sharing, permissions, etc). I have not tested the DP product but I had a BitTitan tech on my podcast and I trying it on my next migration.

I know MS has some built in migration tools, but I haven't used them. Consider this just a tip if you're looking for something that doesn't require the online use for so many weeks. I know my clients want their Outlook up asap.
0
 

Author Comment

by:gopher_49
ID: 41856334
Vasil,

I'll probably use a utility to sync AD accounts from old domain to new domain.  I would imagine something is out there.  Then I would log into each windows profile on the new domain and manually add the Office 365 account to their Outlook profile.   Not sure if there is a more automated way of doing that.
0
 
LVL 43

Expert Comment

by:Vasil Michev (MVP)
ID: 41856524
There are some tools available for that part as well. My idea is that when you do this, you should aim to at least have matching usernames on-prem and in the cloud, which will make user's life much easier. Otherwise, expect to have to explain multiple times when to use which set of credentials. Anyway, one step at a time I guess, you should be all set for the email migration atm.
0
 
LVL 9
ID: 41856528
MigrationWiz is great and offers the desktop agent. I have a rep if you want contact info.
0
 

Author Closing Comment

by:gopher_49
ID: 41879358
In the scenario of leaving a multi-tenancy Exchange environment to Office 365 I suggest using 3rd party tools..  The environment we're leaving from was MT and the native cutover migration wanted to move all mailboxes..  That or the admin was confused..  We ended up using a 3rd party utility..
0

Featured Post

What’s Wrong with Your Cloud Strategy ?

Even as many CIOs are embracing a cloud-first strategy, the reality is that moving to the cloud is a lengthy process and the end-state is likely to be a blend of multiple clouds—public and private. Learn why multicloud solutions matter in this webinar by Nimble Storage.

Question has a verified solution.

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

Know the reasons and solutions to move/import EDB to New Exchange Server. Also, find out how to recover an Exchange .edb file and to restore the file back.
How to deal with a specific error when using the Enable-RemoteMailbox cmdlet to create a mailbox in the cloud-based service, for an existing user in an on-premises Active Directory.
Migrating to Microsoft Office 365 is becoming increasingly popular for organizations both large and small. If you have made the leap to Microsoft’s cloud platform, you know that you will need to create a corporate email signature for your Office 365…
In this video I am going to show you how to back up and restore Office 365 mailboxes using CodeTwo Backup for Office 365. Learn more about the tool used in this video here: http://www.codetwo.com/backup-for-office-365/ (http://www.codetwo.com/ba…
Suggested Courses

650 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