Office 365 Tenancy Migration Q
Discussion
I've done plenty of external Email to Office365 migrations, but never Office-to-Office, so wondering if there is any easier way than I'm currently looking at. So I've got Tenancy A with Domain A, and Tenancy B, with Domain B.
I need to move Domain B, and all the associated accounts/emails into Tenancy A. There are only about 30 accounts....most places are recommending external services or software to do it, but as it's only a few accounts, I was just planning to connect Outlook up to an account, wait for it to sync, download the PST (x30), shift the domain across, then reverse the process.
A) Is there a better way; and
B) Sharepoint and OneDrive isn't used, but what else could potentially be missed?
I need to move Domain B, and all the associated accounts/emails into Tenancy A. There are only about 30 accounts....most places are recommending external services or software to do it, but as it's only a few accounts, I was just planning to connect Outlook up to an account, wait for it to sync, download the PST (x30), shift the domain across, then reverse the process.
A) Is there a better way; and
B) Sharepoint and OneDrive isn't used, but what else could potentially be missed?
The problem with your current approach is the [b]shift the domain across[\b] bit. It takes a several days from you removing the @***. before the onmicrosoft.com from tenancy B to being allowed to add it to tenancy A and then it seems to take ages for The routing at Microsoft to sort itself out.
So definately change the @***. before the onmicrosoft.com and update your MX accordingly.
If they are both 'clean' in terms of ownership, ie. set up directly with microsoft, not via a reseller or ISP you can raise a support ticket from tenancy B and request the move to tenancy A from Microsoft Support.
mattley said:
The problem with your current approach is the [b]shift the domain across[\b] bit. It takes a several days from you removing the @***. before the onmicrosoft.com from tenancy B to being allowed to add it to tenancy A and then it seems to take ages for The routing at Microsoft to sort itself out.
So definately change the @***. before the onmicrosoft.com and update your MX accordingly.
If they are both 'clean' in terms of ownership, ie. set up directly with microsoft, not via a reseller or ISP you can raise a support ticket from tenancy B and request the move to tenancy A from Microsoft Support.
Thanks for this - wasn't aware. So definately change the @***. before the onmicrosoft.com and update your MX accordingly.
If they are both 'clean' in terms of ownership, ie. set up directly with microsoft, not via a reseller or ISP you can raise a support ticket from tenancy B and request the move to tenancy A from Microsoft Support.
For reference, I won't be changing the onmicrosoft.com domain at all - that will remain where it is (and stay dormant) it'll purely be DomainB moving, which we host the DNS for.
Problem is that it seems even if I move the domain early, it'll still mean downtime for their email accounts if it takes a while to move. Looks like it's the only way, they'll need to just live with it for a few days!
Moving a domain from one 365 account to another shouldn't take several days. We do it all the time here and can take literally minutes. Varies a little with MS though.
You could change your domain email addresses to onmicrosoft.com which would keep the mailboxes live so you can move the old emails over at a later point.
Delete the domain, add domain to new account, fire in the txt records etc and then add the email addresses into the new 365 account.
If you wanted to reduce downtime you could create onmicrosoft.com email addresses on the new account so the mailboxes all propagate ready for when the domain goes live in 365. You can then change the onmicrosoft addresses to the domain addresses.
The real time sink would normally be the migration of old emails to your new account/addresses.
You could change your domain email addresses to onmicrosoft.com which would keep the mailboxes live so you can move the old emails over at a later point.
Delete the domain, add domain to new account, fire in the txt records etc and then add the email addresses into the new 365 account.
If you wanted to reduce downtime you could create onmicrosoft.com email addresses on the new account so the mailboxes all propagate ready for when the domain goes live in 365. You can then change the onmicrosoft addresses to the domain addresses.
The real time sink would normally be the migration of old emails to your new account/addresses.
Just pay for Skykick, I don't remember the prices off hand but on 30 mailboxes it's going to be peanuts compared to your time downloading everything to PST/OST and back again, and never being quite sure if you got everything. Just not worth your time.
https://www.skykick.com/blog/office-365-to-office-...
https://www.skykick.com/blog/office-365-to-office-...
Our engineers tend to use an automation tool for most of our customer migrations, but which one depends on the specifics of the job. If you are using workflows, the migration can quickly become complex, but by the sounds of it you are not. I am currently working on a similar project with 80-90 users, PM me if you would like some more details.
MintyScot said:
Moving a domain from one 365 account to another shouldn't take several days. We do it all the time here and can take literally minutes. Varies a little with MS though.
You could change your domain email addresses to onmicrosoft.com which would keep the mailboxes live so you can move the old emails over at a later point.
Delete the domain, add domain to new account, fire in the txt records etc and then add the email addresses into the new 365 account.
If you wanted to reduce downtime you could create onmicrosoft.com email addresses on the new account so the mailboxes all propagate ready for when the domain goes live in 365. You can then change the onmicrosoft addresses to the domain addresses.
The real time sink would normally be the migration of old emails to your new account/addresses.
This. We use Skykick or Migwiz for the tedious copying of mailbox data - especially useful for bigger mailboxes which will break PST files, and the twilight zone while you wait for DNS and mail could still be delivered to old mailbox.You could change your domain email addresses to onmicrosoft.com which would keep the mailboxes live so you can move the old emails over at a later point.
Delete the domain, add domain to new account, fire in the txt records etc and then add the email addresses into the new 365 account.
If you wanted to reduce downtime you could create onmicrosoft.com email addresses on the new account so the mailboxes all propagate ready for when the domain goes live in 365. You can then change the onmicrosoft addresses to the domain addresses.
The real time sink would normally be the migration of old emails to your new account/addresses.
Gassing Station | Computers, Gadgets & Stuff | Top of Page | What's New | My Stuff