In a previous post I wrote about how you can migrate Microsoft Teams from one (source) Office 365 tenant to another (target) Office 365 tenant by using third party (3P) tools to ease and automate the migration process. BitTitan is one of the tools which can be used.
BitTitan published a White Paper regarding “Top Migration Considerations for Cross-Tenant Teams Migrations” which you can request and download to avoid typical pitfalls and get awareness on what limitations there might be. You can find the link to request the download of the White Paper at the bottom of this post.
In the past I wrote a post regarding migrating a single capability, Teams telephony workloads, from a source to a target Office 365 tenant. In this post I like to emphasize a new third party service and its capability which can help to accomplish a complete Teams Tenant-to-Tenant migration.
BitTitan, a third party service provider for service automation, announced their new service to migrate Teams from a source to a target tenant. It enables companies who need to merge or split Teams into or off another Office 365 tenant.
BitTitan MigrationWiz Teams Tenant-to-Tenant Migration
MigrationWiz enables for migrating the following Team workloads:
- Teams instance and the individual components
- Files within that instance
On top the service offers a pre-migration assessment
- to analyze the number of Teams to be migrated
- to analyze the amount of data to be migrated
- to analyze the number of users to be migrated
The above described service capabilities are subject to change at anytime. The described capabilities are just a high-level overview. I recommend to read the lastest service provider’s service specification etc. before.
Conclusion, opinion and summary
I dealt with a few Microsoft Office 365 Tenant-to-Tenant migration due to different business requirements. However, it was very much to do and script. Now, MigrationWiz seems to really simplify the complete process for Office 365 Tenant-to-Tenant migrations regarding Microsoft Teams.
As of now [July 2019] there are only a few service providers out there offering a service to smoothly migrate Teams from Tenant-To-Tenant as far as I could see. So, BitTitan MigrationWiz is now an option to speed up, simplify and automate your T2T migration batches for Teams, too.
- Migrate Microsoft Teams with MigrationWiz
- BitTitan Introduces Microsoft Teams Migration Capabilities to MigrationWiz
- Bittitan MigrationWiz for Teams
- Architecture approaches for Microsoft cloud tenant-to-tenant migrations
- How to port Microsoft Phone System phone numbers between Office 365 Tenants? [erik365]
In this post I describe and share my experience on how you can port numbers from Microsoft Phone System from one Office 365 source tenant to another Office 365 target tenant. First of all, why should you do this? Well, there are several reasons you might have to port existing phone numbers from a source to a target Office 365 tenant, e.g.
- company merger and acquisition
- company segregation
- other forms of organizational restructure measures and needs
- technology change requirements (migrate / cutover / move (partially) from a PoC environment to a production environment …)
- security change requirements
When do you have to port phone numbers?
On the one hand, if one of the above reasons or another reason may apply to your organization. And of course, on the other hand, if your organization and you like to keep the phone numbers to carry on getting calls on these ones. To sum it up,
- you’ll have to port phone numbers if you rely on Microsoft Phone System Calling Plans and
- Microsoft is also your PSTN service provider from whom you get your PSTN phone numbers
- and you might published (to suppliers, customers, partners) and adopted these phone numbers in your company communication with the outside world … (mail signatures, business cards, …)
Is this difficult to do?
Fortunately it is not.
Still, you have to pay attention to a few things to make the phone number porting a smooth cutover and a success. I recommend to read carefully what’s on the Microsoft Phone System documentation and a blog (see links below). I do not mention here that an Office 365 Tenant-to-Tenant migration might has other challenges you have to cope with. I recommend that you plan it – the whole migration – thoroughly to get it working with a minimal impact to your users.
What numbers can I port?
You can port user and service numbers.
What do I have to do?
As a prerequisite I recommend to set up the destination tenant with the appropriate licenses (e.g. E5 + Calling Plan International + Communication Credits + Audioconf …) to be ready for assignment as soon as the numbers are available in the destination tenant. Don’t forget about setting up Communication Credits.
Besides of all your other Office 365 Tenant-to-Tenant (T2T) migration tasks as your first step please read the blog post from “Porting Cloud PSTN Telephone Numbers Between Office 365“.
What data do I need to submit to the Microsoft PSTN Porting team?
Because it is almost always the same data you need to submit to Microsoft for a T2T migration I just created an easy to use table which you can copy and help as a guiding and supporting tool.
|Data||Value (you need to insert)|
|O365 source tenant domain name||….onmicrosoft.com|
|O365 source tenant unique identifier||…|
|O365 source tenant (porting) PIN||…|
|O365 destination tenant domain name||….onmicrosoft.com|
|O365 destination tenant unique identifier||…|
|O365 numbers emergency location address (for the numbers)||e.g. (Floor, Building,) Street, City, ZIP, Country|
|Number(s) to be ported from source to destination tenant||e.g. +49711xxxxxxx to +49711xxxxxyy|
|Number type (user vs. service phone numbers?)||e.g User|
|Requested date and time range of port requestion execution||e.g. 17/03/2019 10am|
|Request mail-to [Microsoft PSTN Team, see port request Microsoft page]||e.g. Microsoft PSTN Europe Team|
After you have submitted the request the Microsoft PSTN Team answers, either with additional questions or a confirmation request. You than need to confirm the port request which enables the Microsoft PSTN Team to port your numbers based on the details of the confirmation mail.
During the porting
- the numbers will be removed on the source tenant,
- users will not be able to be called or make a (PSTN) call [inform your users early enough],
- numbers will show up in the destination tenant.
If you have licenses, numbers ready, congratulations you made it and can now assign the user/service numbers within the target O365 tenant.
Conclusion, opinion and summary
In my opinion porting phone numbers is really a smooth migration part of an Office 365 T2T migration. Recently, I had to port numbers and was really positively surprised how straightforward and smooth it worked. The only thing I really want to note and highlight is that if you should have all your licenses early enough in the destination tenant because in a recent T2T migration the licenses where added/booked quite late and that’s why it took some time till phone numbers could be assigned to users.
- Microsoft Phone System – Here’s what you get with Phone System in Office 365
- Port a Phone Number to Cloud PBX in Office365 [2016, general post about porting numbers from a PSTN provider to Microsoft Phone System, still a good read, bit different to do in the EU/Germany]
- Transfer phone numbers to Office 365
- Transferring phone numbers common questions
Phone Number Porting Tenant-2-Tenant
- Porting Cloud PSTN Telephone Numbers Between Office 365 Tenants [worked fine for me; in EU/DE you could send a mail to PTNEU instead of PTN; or other mail address you used at requesting (new)/porting (of) numbers the first time; good read]