Your Android Teams app is stuck on a migration screen and never finishes moving to New Teams. The migration can hang because the app lacks storage space, has a stale cache, or the network connection drops mid-process. This article explains why the migration stalls and gives you the exact steps to force the migration to complete on your Android phone or tablet.
New Teams on Android is the unified client that replaces the classic app. Microsoft rolls it out automatically, but the in-app migration can fail silently. You will learn how to clear the blocker, restart the migration, and prevent it from failing again.
Key Takeaways: Fix New Teams Migration on Android
- Settings > Apps > Teams > Storage > Clear Cache: Removes corrupted migration data that blocks the update.
- Settings > Apps > Teams > Force Stop: Kills the stuck migration process so you can restart it cleanly.
- Play Store > Teams > Uninstall: Removes the app completely for a clean reinstall that starts migration fresh.
Why New Teams Migration Stalls on Android
The migration from classic Teams to New Teams on Android is a background process that downloads the new app package and switches your account data. The process needs three things to succeed: enough free storage, a stable internet connection, and a clean app cache. When any of these fail, the migration shows a progress bar that never moves past a certain point.
The most common cause is a full or nearly full device storage. The New Teams package is about 150 MB, and the migration also creates temporary files. If your phone has less than 500 MB free, Android pauses the download. The app then shows a spinner or a percentage that stays at 0% or 50%.
Another cause is a corrupted cache from an interrupted download. If you previously tried the migration on a weak Wi-Fi signal, the partial data stays in the cache. The next attempt reads that broken data and fails. The app does not clear this automatically.
A third cause is the app process being suspended by Android’s battery optimization. When the screen locks, Android may pause the migration. When you unlock, the app resumes but the download state is lost, so it appears stuck.
Steps to Force New Teams Migration to Complete
Follow these steps in order. Stop when the migration completes. Test the app after each step to avoid unnecessary work.
- Check available storage
Open Settings > Storage on your Android device. Confirm you have at least 1 GB free. If not, delete unused apps, photos, or videos. The migration needs this space for the New Teams package and temporary files. - Clear the Teams app cache
Open Settings > Apps > Teams > Storage. Tap Clear Cache. Do not tap Clear Data yet. This removes corrupted migration files without signing you out. Then relaunch Teams from the app drawer. - Force stop Teams and retry
If the cache clear does not help, go to Settings > Apps > Teams and tap Force Stop. Then open Teams again. The app should show the migration screen and restart the download from scratch. - Disable battery optimization for Teams
Open Settings > Apps > Teams > Battery. Select Unrestricted or Don’t optimize. This prevents Android from pausing the migration when the screen turns off. Keep the screen on during the migration by setting your screen timeout to 10 minutes or longer. - Switch to a stable network
Connect to a 5 GHz Wi-Fi network or a strong cellular data signal. Do not use a public Wi-Fi that requires a login page. The migration needs a continuous connection. If the Wi-Fi drops, the process fails. - Reinstall Teams from the Play Store
If all else fails, uninstall Teams completely. Open the Play Store, search for Teams, and tap Uninstall. Then tap Install to get the latest version. Sign in with your work or school account. The migration will run automatically after sign-in.
If Teams Still Does Not Migrate After These Steps
Teams Shows a Blank Screen After Reinstall
A blank screen after reinstall means the migration started but the app cannot render the New Teams interface. This usually happens when the device runs an outdated Android version. Check Settings > About Phone > Android version. New Teams requires Android 10 or later. If your device is older, you cannot migrate, and you must keep using classic Teams until you change devices.
Migration Stuck at 100%
When the progress bar reaches 100% but the app never opens, the final step of switching the account profile failed. Force stop Teams and reopen it. If it stays stuck, clear the cache again and sign out and back in. Use the profile icon in the top left corner to sign out, then sign in again.
Error Message Says Migration Failed Due to Network
This error appears when the download times out. Check your Wi-Fi signal strength. Move closer to the router or use a mobile hotspot. Then tap Retry on the error dialog. If the error repeats, restart your phone to reset the network stack, then try again.
New Teams Android App vs Classic Teams Android App
| Item | New Teams | Classic Teams |
|---|---|---|
| Interface | Faster, unified with desktop | Older layout with separate tabs |
| Storage requirement | About 150 MB plus cache | About 100 MB |
| Update method | In-app migration | Standard Play Store update |
| Support for Android 9 | Not supported | Supported |
| Meeting features | Includes new meeting controls | Lacks newer features |
You can now force the migration to complete by clearing the cache, disabling battery optimization, and reinstalling the app if needed. Start with the storage check and cache clear because they solve most cases. If your device is on Android 9 or older, the migration will never complete, and you should plan to upgrade your hardware. As a final tip, keep your Android OS updated to Android 12 or later, because New Teams relies on newer background download APIs that older versions handle poorly.