Essential Steps for Teams Voice Tenant to Tenant Migration

Essential Steps for Teams Voice Tenant to Tenant Migration​

Unlike standard Teams data, voice services involve intricate configurations to ensure seamless call continuity throughout the process. This additional layer of complexity necessitates a well-defined approach to guarantee a smooth and successful migration. This blog post will serve as your guide, outlining the essential steps for Teams Voice Tenant to Tenant  migration, addressing the specific considerations involved, and ensuring a successful transition for your organization’s communication needs.


Pre-Migration Planning

Laying the groundwork is crucial for a successful Teams Voice tenant to tenant migration. This phase involves planning across various aspects.

1. Source Tenant assessment:

        • User base: Total number of users relying on Teams voice for communication.
        • Call volume: Average call volume to understand how often people are calling your service. To identify overall usage patterns.
        • Phone system integration: Identify the existing phone system integration method (Direct Routing, Calling Plans etc.)
        • Feature identification: Pinpoint the specific Teams voice features currently utilized within your organization. This might include functionalities like:

            • Call forwarding
            • Voicemail
            • Auto attendants
            • Call recording (if applicable)

2. Target Tenant preparation:

        • Licensing: Ensure the target tenant has the necessary Teams voice licenses for all migrating users. 

        • Phone number porting: If your organization plans to retain existing phone numbers, establish a plan for porting them to the target tenant. 

3. Communication strategy:

        • User awareness: Clearly communicate the timeline, potential downtime during the transition, and any changes they might experience in their Teams voice functionality.

        • Addressing concerns: Be prepared to address user inquiries and provide adequate support throughout the migration process.

Migration Process

The first task you need to do is to have the following information required.

      1. Source Tenant domain name
      2. Source tenant unique identifier.

        The tenant unique identifier is often known as a globally unique identifier or GUID. To find this from within the Azure AD admin center:

      3. Destination Tenant name and a unique identifier
      4. Numbers
        These need to be broken down as a user number or a or a service number (auto attendants, call queues or virtual numbers which need to follow a particular function but are not attributed to a physical user).
      5. Addresses
        The addresses on the destination tenant for user numbers will need to be supplied.
      6. Request date and time


Third-party Solutions

It’s important to acknowledge that Microsoft currently doesn’t offer built-in tools for complete migration of Teams voice functionalities between tenants.

Due to the absence of native tools, you can explore leveraging third-party migration software. These tools offer functionalities to:

        • Transfer user data: Migrate call history, voicemail recordings, and potentially limited configuration settings.
        • Automate certain aspects: Streamline the migration process by automating repetitive tasks.


Post-migration validation

Following the successful migration of your Teams Voice functionality to the new tenant, a thorough validation process is essential. This guarantees everything is working as intended and identifies any potential issues before widespread user adoption.

1. User account verification:

Verify that all migrated user accounts are accessible and functional within the new Teams Voice tenant. This includes logging in, accessing call history, and managing voicemail settings.

2. Phone number validation:

Conduct test calls from various internal and external numbers to ensure proper call routing and reception.

3. Voicemail functionality testing:

Ensure voicemail greetings have been transferred correctly and can be customized by users.

4. Call quality and connectivity:

Conduct test calls between users within the new tenant and with external contacts to assess call quality.

5. Addressing migration issues:

If any errors or inconsistencies are encountered during validation, document them clearly.

After considering all of the factors that a tenant-to-tenant migration in Teams Voice, we can conclude that it can be a complex process, especially for mid-sized organizations with a significant amount of data and users. However, with the help of BlueSky UC’s experts, you can ensure a smooth transition and avoid disruptions to users and business operations. Let us help you migrate seamlessly, book a meeting with one of our migration experts today to start the exciting journey ahead. 

Sign up to learn more

Get news, updates, and insights about Microsoft Unified Communications (UCaaS).

Share this story, choose your platform!

Related posts

side banner-direct routing

Microsoft Teams Direct Routing Services

Enjoy high-quality calls, flexible pay-as-you-go, volume pricing, and failover solution

Recent Posts


teams icon

Microsoft Teams Professional Services

Tailor Teams to your unique needs with expert design and integration