Fix New Teams Migration Does Not Complete on a Managed Device

Your managed device shows the New Teams migration in progress, but the switch never finishes. The app stays on the old Teams or shows an error that the migration cannot complete. This usually happens because of missing registry keys, blocked network endpoints, or outdated policies from your IT admin. This article explains the root causes and gives you step-by-step fixes to finish the migration.

Why the New Teams Migration Fails on Managed Devices

The New Teams migration on a managed device depends on three things working together: the Teams app, the Windows registry, and your organization’s policies. When any of these are out of sync, the migration stops.

The most common technical root cause is a leftover registry value that tells Teams the migration already ran. This value is called MigrationState and it lives under HKEY_CURRENT_USER\Software\Microsoft\Office\Teams. If this value is set to a status code that means “completed” but the new app is not actually installed, Teams refuses to try again.

Another frequent cause is a group policy that forces the old Teams app to launch. Policies in the Teams admin center, like the coexistence mode, can block the migration. If your admin set the mode to Islands, both apps run side by side, and the migration may not trigger at all.

Finally, network issues can stop the download of the new Teams installer. The installer needs to reach specific Microsoft endpoints. If your firewall blocks those endpoints, the migration shows as pending but never progresses.

How the Migration Process Works

When you switch to New Teams, the app runs a detection script. This script checks the registry for the current state, downloads the new installer, and then updates the registry. The whole process is logged in the Windows event viewer. If any step fails, the migration stops and the old Teams stays active.

Steps to Diagnose and Fix the Migration on a Managed Device

Follow these steps in order. They cover the most common fixes, from checking policies to clearing the registry.

Step 1: Check the Teams Upgrade Policy

1. Open the Teams admin center
   Go to Teams admin center > Teams upgrade settings > Coexistence mode. Sign in with an admin account. If the mode is set to Islands, the migration may not start. Change it to Teams only to force all users to the new app. This setting takes effect within 24 hours.
2. Check the migration notification policy
   In the same section, look at Migration notification policy. Make sure it is set to Notify users. If it is set to Hide, users never see the prompt to switch, and the migration stays incomplete.

Step 2: Reset the Migration Registry Value

1. Close Teams completely
   Right-click the Teams icon in the system tray and choose Exit. Make sure no Teams process is running in Task Manager.
2. Open the Registry Editor
   Press Win + R, type regedit, and press Enter. Navigate to HKEY_CURRENT_USER\Software\Microsoft\Office\Teams.
3. Delete the MigrationState value
   Find the value named MigrationState on the right side. Right-click it and choose Delete. If the value does not exist, skip this step.
4. Restart Teams
   Close the Registry Editor and start Teams again. The app should detect the missing value and begin the migration. Wait for the yellow banner that says “New Teams is ready.”

Step 3: Verify Network Endpoints

1. Check the required endpoints
   Open a browser and go to the Microsoft 365 URL and IP address range documentation. Search for the list of Teams endpoints. The installer needs access to teams.microsoft.com and download.microsoft.com and all subdomains.
2. Test connectivity
   On the affected device, open Command Prompt and run ping teams.microsoft.com. If the ping fails, your firewall is blocking the endpoint. Contact your IT admin to allow the traffic.

Step 4: Use the Teams Bootstrapper

1. Run the bootstrapper manually
   Open Command Prompt as an administrator. Navigate to C:\Users\%username%\AppData\Local\Microsoft\Teams. Run TeamsBootstrapper.exe -p to force the migration. This command installs the new Teams without waiting for the automatic trigger.
2. Check the installation log
   After the command finishes, open Event Viewer and look under Windows Logs > Application. Search for events with source Teams. A successful migration shows event ID 1000 with no error codes.

Step 5: Reinstall Teams Cleanly

1. Uninstall the old Teams
   Go to Settings > Apps > Installed apps. Find Microsoft Teams and uninstall it. This removes the old app but keeps your data.
2. Clear the Teams cache
   Open File Explorer and go to %appdata%\Microsoft\Teams. Delete everything inside this folder. Then go to %localappdata%\Microsoft\Teams and delete that content too.
3. Install the New Teams
   Download the installer from the Teams download page and run it. The new app installs directly without migration. Sign in with your work account.

If Teams Still Has Issues After the Main Fix

Teams Shows “Migration in Progress” Forever

If the banner stays on the screen for more than 24 hours, the migration script is stuck. Use the registry reset from Step 2, then immediately restart the device. After the restart, open Teams and check if the banner disappears.

Teams Launches the Old App After the Fix

Your admin policy may still point to the old app. Check the coexistence mode again. If it is set to Teams only but the old app opens, run the bootstrapper command from Step 4. This overrides the policy for the current user.

Error Code 0x80070005 Appears

This error means the installer cannot write to the registry or the app folder. The cause is usually a lack of permissions. Run Teams as an administrator once, or ask your IT admin to grant you write access to the Teams folder.

New Teams Migration on Managed Device vs Manual Switch

Item	Managed Device Migration	Manual Switch
Trigger	Automatic via policy	User clicks the toggle
Control	IT admin sets coexistence mode	User decides when to switch
Common failure	Policy blocks or registry stuck	No failure, but may be delayed
Fix method	Registry reset or bootstrapper	None needed

Now you can fix a stuck New Teams migration by checking the coexistence mode, resetting the MigrationState registry value, and running the bootstrapper. Try the registry reset first because it is the fastest fix. If that does not work, run the bootstrapper command and verify the network endpoints. For future issues, check the Event Viewer logs to see the exact error code before contacting support.