Moving Teams Phone systems between Tenants

Moving Teams Phone Systems from one Tenant-to- another can be complicated for various reasons. Businesses invest in phone systems and related hardware with enough capacity to meet present demands and future expansion. Rarely can organisations anticipate significant future changes, such as acquiring a business with other solutions. These issues are included in the price of merger, acquisition, and divestiture projects. 

Numerous Cloud phone solutions have substantial feature differences, technological difficulties, and system incompatibilities. Selecting just one system during migration is frequently better to enable optimum call handling. In addition, telephony systems often contain crucial customer-facing routines and processes that must continue to function to maintain client connections. 

Migratory Routes – Moving Teams Phone systems

Following are some specific categories for migration choices: 

Migrate it all: All users, data, and workflows should be migrated to the target system; however, this is not always achievable. This is the gold standard. When migrating across identical systems, complete migration is typically only attainable in phone migration initiatives. Even then, integrating items like call recordings might not be possible. Although this is the expected result, phone migration technology is not there yet. 

Dial tone recovery: When the migration procedure switches the phone service from the source to the target, it results in a dial tone recovery. The intention is to transfer functions (such as routing and phone numbers) rather than data. This tactic is frequently used when migrating systems is impossible owing to API or compatibility constraints or when data is not crucial. 

Offline data retention- is a technique like a dial tone migration, but the data is retained in a different system. This data comprises call recordings and call quality assessment details for phone migrations. The system may transfer the data into an archive or eDiscovery system, or the old plan may be kept operational for an extended time. This tactic is frequently used when the source and target systems are incredibly different, and the data is required for performance reporting, legal requirements, or other purposes. Giving users access to their data can be a challenging task, though. Additionally, data retention requirements for regulated businesses may come with unexpected expenditures. 

Divestitures, sometimes known as “carve-outs,” are problematic because businesses rarely operate intending to separate off a portion of the company. 

When arranging a migration, pay close attention to the TSA (Transition Service Agreement). This agreement specifies how long the source firm must supply service to facilitate the transfer. Including provisions in this agreement that are not technically feasible is a frequent annoyance. For instance, the TSA might specify that customers preserve their current phone numbers; however, while this may sound easy, it may be impossible. 

In addition to the technical difficulties, divestitures can significantly impact the business because both the source and target companies must make essential decisions that present IT with extremely difficult or even impossible challenges, especially given the short timelines that are typical of divestiture scenarios. Therefore, it is crucial to incorporate IT specialists with telephonic knowledge in decision-making. 

Moving Teams Phone systems

After discussing the fundamental concerns related to Moving Teams Phone systems throughout MAD projects, let us think about the related to the Teams Phone system. You can integrate Microsoft Teams Voice in various ways with traditional telephony.

Teams Phone with Calling Plans from Microsoft are offered as an add-on or are included in a specific Microsoft 365 Subscription. Microsoft Teams users can call PSTN landlines and mobile numbers with calling plans (available in domestic and international ) without integrating with any other service provider. Microsoft calling plans are now available to buy in In 33 Countries,

Direct Routing

Direct routing enables businesses to connect to a SIP trunk using an SBC (session border controller). SBC come in various forms, such as when a service provider provides the trunks and SBC or when your own SBC is connected to Microsoft Teams. You can choose a direct approach if you have a multi-year agreement and want to make the most of that investment. Alternatively, you can decide that you wish to offer phone services to a place that is not yet on the list. In that case, there would be a perfect incentive to take a straight path. 

Moving Teams Phone Systems from one tenant to another

The project is simple if you utilise a Microsoft calling plan because Microsoft still provides the phone service. Moving Teams Phone systems between two Tenants can be done by following simple steps.

• Go to the “Phone Numbers” tab from the Teams Admin Center Voice Tab.
• Select “Get phone number support.”
• This starts the number porting procedure (You may find more information on contacting the porting staff here).
• Add in your domain name, a domain-specific identifier such as a tenant ID, the date and time of your request, a phone number or numbers list, and emergency locations.
• Get your service numbers (call queues, auto attendants, and users) as they will be assigned as you go through the porting process. Moving Teams Phone systems are more accessible with the admin centre.

Moving Teams Phone systems process is more challenging technically for companies using a direct routing solution. If you switch service providers, the porting process may take weeks or even months. Additionally, you can usually only relocate phone numbers that are a part of a continuous chain of numbers; otherwise, you must change full ranges of phone numbers at once. 

Auto attendants and call queues 

During moving Teams Phone systems between two Tenants, Call queues and auto attendants may be crucial components of Teams Phone. These services can be used by numerous internal and external Teams Calling policies and procedures. For instance, these features are frequently used in sales and help desk procedures. After phone numbers are transferred to the target tenant in a moving teams phone system between tenant-to-tenant migration, auto attendants and call queues must be re-established in the target tenant. 

Additionally, pay attention to service numbers. Service numbers are not associated with any one user, like shared mailboxes. They often participate in a hunt group or call queue. Service numbers could be an auto-attendant, sometimes an interactive voice response, or a conference call number IVR (Interactive Voice Response). As stated above, you are not permitted to transfer a single number across service providers. However, if you continue using that service, most companies let you move a phone number to another client. This circumstance applies when both organisations involved in the migration utilise the same provider. 

Channel-enabled call queues 

A Microsoft Office 365 group or team can manage agents assigned to call queues. Simply put, a user who is a member of a team and a particular channel inside that team can be chosen to answer a call queue. Using a familiar interface, this function makes controlling the queue easier. Additionally, allowing users access to phone management interfaces is no longer necessary with Teams, eliminating dangers and other potential problems. These third-party interfaces have the drawback of frequently not supporting restricting admin access. Users may make mistakes in different queues and configurations if they need to manage a single call queue. 

Moving Teams Phone systems between tenants are made more difficult by using groups for queue management since we must ensure that all pertinent individuals are transferred from one channel to the next. The Teams owners must be aware of when the member list will “freeze” because they will need to make modifications after the migration if the list of members is continually changing. 

To ensure no calls are dropped during moving Teams Phone systems, we must also configure the call queues to use the same channel in the other tenant. This practice can significantly increase reporting for moving Teams Phone systems between two Tenants scoping. It is crucial to check that all channel-enabled queues are identified and correctly configured in the target during the planning phase. Communications containing cut-offs for membership changes must be delivered to the users managing the queues during the planning phase. 

Operator Connect 

Microsoft backs Operator Connect for Teams, which enables a company to connect to a licensed phone operator easily. When you link them to Teams, these operators let you keep your agreement, connection, and a fee per minute. This constancy is good news for businesses wanting to meld into one company without a hitch. If your contract is still in effect, you can switch tenants, re-incorporate your current phone numbers into Teams, and then allocate the numbers correctly. Moving Teams Phone systems between tenants are more accessible with Operator Connect.

However, businesses have substantial problems moving Teams Phone systems between two Tenants without using a voice supplier. New numbers are given upon migration by the operator or telephone provider. The old, assigned numbers must then be removed and added to the new tenant. The administrator can then reassign the numbers in the target by going to the Teams Amin Center under Operator Connect. This work is significant in its scope. 

Teams Enabled Phones and Teams Meeting Rooms 

There are numerous phones available. Yealink, Crestron, Lenovo, AudioCodes, and Poly are among the Microsoft-certified Teams Rooms suppliers. You may access the complete list of devices here. 

Various suppliers also offer systems for team rooms and tools for administering that equipment. Businesses can use numerous Teams-enabled devices given a PSTN number to place and receive phone calls. Use only licensed service providers; a list of licensed service providers is available here. Moving Teams Phone systems from one tenant to another may require your IT Support Provider to remove the devices from your EndPoint Management Portal.

Many characteristics of Teams phones and Teams Rooms can be controlled using the Teams Admin Center. All devices must be reregistered or authenticated to the new target tenant, regardless of the manufacturer. Moving Teams Phone systems with Intune can be a big project, depending on how many rooms and physical endpoints there are. In contrast to typical phone system migrations, this form of migration benefits from the fact that phones that function on one tenancy also work on another. 

Most phones must undergo a hard reset to be visible in the Teams Admin Center. Currently, a phone that moves from one tenant to another without reset cannot reregister with Intune in the new renter, leaving the Phone still under previous Mobile Device Management.

We have tried to help you understand the process of moving Teams Phone systems between two Tenants. Contact Teams Phone Support for any help regarding Teams Phone system migration or Teams Phone Calling Plan Cost.