Phones after a suite switch: moving ten people's mail, calendar and authenticator apps without a lost day
The phone side of a Google Workspace and Microsoft 365 switch for ten people: the order that avoids lockouts, Temporary Access Pass and backup-code steps, iPhone and Android differences, a 28-minutes-a-phone budget and a plan for the person who is away.

The mailboxes moved on Saturday. On Monday at 8:40 someone cannot open Outlook on their phone, someone else is asked for a login code on a phone that is in a drawer at home, and the person in Lisbon cannot sign in at all. The server side of a suite switch is a weekend. The phones are where the lost day happens.
This is the phone side of the move for ten people, in both directions (Google Workspace to Microsoft 365, and back). It has the order that avoids lockouts, per-phone steps for iPhone and Android, a time budget and a plan for the person who is away. For the server side, read the migration weekend first.
One honest note. We did not stand over ten phones with a stopwatch for this article. The limits, defaults and steps come from the vendors' own pages, read on 21 November 2026 (links at the end). The minutes in the time table are a planning budget with the assumptions written out. Replace them with what your pilot phone takes.
The short version
- The mail app is the easy part. Add the new account, remove the old one. About 5 minutes.
- The authenticator is the part that locks people out. The app on the phone is tied to the old suite's sign-in. It has to be set up again on the new suite, and the person needs a way in that does not depend on the old setup.
- Microsoft's backup does not carry work accounts. Only the account name comes back, then each person signs in again. Backup works for personal and third-party codes, and only between the same kind of phone (iPhone to iPhone, Android to Android).
- Give each person a way in before Monday. On Microsoft 365 that is a Temporary Access Pass. On Google Workspace it is an admin-generated backup code.
- Keep the old phone and the old suite seat until the new sign-in has worked once.
Step 0: list what is on each phone
Do this a week before. Ask each person for a list of names, not the codes themselves. You want to know, per phone:
- iPhone or Android, and whether anyone changes phone type this month. That decides whether backup restore works (see below).
- Which mail app: the suite's own (Gmail or Outlook) or the built-in one.
- Which authenticator app holds the work sign-in, and which other accounts (bank, GitHub, social) share that app.
- Whether they use a passkey for work sign-in.
- Whether they are away during the cutover week.
In a ten-person office this list takes about 20 minutes to collect. It saves finding out on Monday morning.
The order that avoids lockouts
Two rules decide everything. First, nobody can set up a new authenticator on the new suite if the only way in is a code from the old setup. Second, the old suite's seat stays on until the new sign-in works. Our migration article already says to keep the old plan one more month.
| Order | Do this | Who | When |
|---|---|---|---|
| 1 | Turn on the way-in tool: Temporary Access Pass policy (Microsoft) or check you can generate backup codes (Google) | Admin | Week before |
| 2 | Everyone backs up third-party codes (see the per-phone sections) | Each person | Week before |
| 3 | Mail, calendar and files cut over | Admin | Saturday |
| 4 | Admin issues each person a pass or code that starts Monday 8:00 | Admin | Sunday evening |
| 5 | Person signs in on a laptop browser, sets up the new authenticator, adds the new mail account on the phone | Each person | Monday morning |
| 6 | Person removes the old authenticator entry and old mail account | Each person | After a successful test |
| 7 | Admin checks each person's methods and revokes old sessions | Admin | Tuesday |
Google Workspace to Microsoft 365: the MFA re-enrolment
Microsoft's tool for this is the Temporary Access Pass (TAP): a time-limited code an admin creates for a person. With it the person signs in at mysignins.microsoft.com/security-info without another second step, and registers Microsoft Authenticator from there.
The numbers from Microsoft's page (updated November 2026):
| Setting | Default | Allowed |
|---|---|---|
| Minimum lifetime | 1 hour | 10 to 43,200 minutes (30 days) |
| Maximum lifetime | 8 hours | 10 to 43,200 minutes |
| Default lifetime | 1 hour | 10 to 43,200 minutes |
| One-time use | Off (a pass can be used more than once while valid) | On or off |
| Length | 8 characters | 8 to 48 |
Setup, as the admin:
1. Sign in to the Microsoft Entra admin center as at least an Authentication Policy Administrator.
2. Go to Entra ID > Authentication methods > Policies > Temporary Access Pass, choose Enable, include your staff group, and save. Only people in the policy can sign in with a pass.
3. Go to Entra ID > Users, open the person, choose Authentication methods > Add authentication method > Temporary Access Pass. Set the start time (Monday 8:00) and the lifetime.
4. Copy the pass before you click OK. You cannot view it again.
5. Send it by a channel that is not the mailbox that just moved: a text message or a phone call.
The lifetime we would pick for the office: 4 hours, multi-use. Microsoft notes that a one-time pass used to register a passwordless method must be finished within 10 minutes of sign-in. A multi-use pass lets the person enter it again if the phone setup needs a second try. The 4 hours has to sit between your minimum (default 1 hour) and maximum (default 8 hours) lifetime.
What the person does on Monday:
1. In a browser, go to the Security info page. Enter the work address, then the pass.
2. Choose Add sign-in method, then Authenticator app. Install Microsoft Authenticator if it is not there, choose Work or school account, scan the QR code.
3. Approve the test prompt.
4. Remove the old methods listed on that page that belong to the old setup.
5. If your policy needs passkeys: add one from the same page and test it before removing anything.
If somebody is stuck, the admin can open Authentication methods for that user and choose Require re-register MFA. Microsoft says this deletes the person's phone numbers, Microsoft Authenticator apps and software OATH tokens, and asks them to set up again at the next sign-in. Do not use it on a person who is away: they would be asked to set up a method they cannot complete yet.
Microsoft 365 to Google Workspace: the MFA re-enrolment
Google's tool for this is the backup verification code. The admin generates one for the person; the person signs in with their password and that code.
The facts from Google's pages:
- A set holds 10 codes, 8 digits each. Each code works once.
- Making a new set switches the old set off.
- The admin needs the User management privilege. Only a super administrator can generate codes for another admin.
- Google's recovery page tells the admin to copy one code and send it to the person by message.
Admin steps: in the Admin console go to Directory > Users, click the person, Security > 2-step verification > Get Backup Verification Codes, copy one code and send it. This works when 2-step verification is enforced for your organisation or turned on for that account.
On the new Google Workspace you can enforce 2-step verification with a new user enrollment period (1 day to 6 months; during it, new users can sign in with just a password). We would pick 1 day: long enough to cover the Monday phone clinic, not longer.
What the person does: sign in with the password and the code, add Google Authenticator or phone prompts under their Google Account security page, and test. Google Authenticator can sync its codes to a Google Account. Keep personal codes (bank, social) out of the work account: if the person leaves, those codes leave with it.
iPhone, step by step
Before the cutover, third-party codes. Microsoft Authenticator on iOS backs up through iCloud. Turn on iCloud Drive, iCloud Keychain and iCloud Backup, then go to Apple Account > iCloud > Saved to iCloud and switch on Authenticator. Microsoft's page says that if a backup does not show on a new iPhone, update Authenticator to version 6.8.33 or later, open the app on the old phone before the switch, then uninstall and reinstall on the new one.
What comes back: third-party entries with a code that refreshes every 30 seconds (Amazon, GitHub, social sites), and personal Microsoft accounts that use only the code. What does not: a work or school account. Only its name comes back, with red text asking you to sign in again. That is expected.
Mail and calendar. Add the new account in the suite's app (Outlook for Microsoft 365, Gmail for Google), sign in and approve the second step. If the person uses the built-in Mail app, add the new account under Settings and remove the old one only after the test. Check that Monday's calendar shows in the new account first.
Android, step by step
Before the cutover. Open Microsoft Authenticator, Settings, turn on Cloud Backup and pick a Microsoft personal account to hold it. If you chose the wrong account, delete the backup and make a new one. Microsoft's page also says that from January 2027 Android backups move to Google One, where you enable Microsoft Authenticator. If you do this after the new year, check that screen first.
Mail and calendar. Google's help says Gmail on Android supports Microsoft 365 and Exchange ActiveSync accounts. In Gmail, tap the profile picture, Add another account, choose Exchange and Office 365 and sign in. If a message says the address is used with more than one Microsoft account, choose the work or school one. Your admin may require a screen lock or password on the phone once the account is added. The Outlook app is the other route: add the account and sign in.
The mixed case: iPhone to Android, or the other way
Microsoft says you can only back up and restore on the same device type. If anyone changes phone type in the same month as the suite switch, restore will not work and they must add every account by hand, each with its own QR code or setup key. Tell them to keep the old phone until every entry has signed in once, as Microsoft's page says. Passkeys need the same care: if a passkey was saved only to the old phone, create a new one from the Security info page before getting rid of it; if it sits in a synced manager (iCloud Keychain, Google Password Manager, Microsoft Password Manager) check it is there first. For what happens to a phone when its owner leaves, see our offboarding checklist.
A planning budget: minutes per phone
The assumptions: an admin on hand, one pilot phone done the Thursday before, the person has a laptop with a browser, backup was on before the switch, nobody changes phone type. These are budget numbers, not measured ones.
| Step | iPhone | Android |
|---|---|---|
| Check backup is on and list the app entries | 5 | 5 |
| Add new mail and calendar account in the app | 5 | 5 |
| Admin creates pass or code (admin time) | 2 | 2 |
| Sign in to Security info, add authenticator, test prompt | 6 | 6 |
| Remove old account and old method | 4 | 4 |
| Restore third-party codes from backup | 3 | 3 |
| Test: mail, calendar, one sign-in on the laptop | 3 | 3 |
| Total per person (minutes) | 28 | 28 |
Ten people at 28 minutes is 280 minutes, 4.7 hours of staff time. At an example loaded cost of $40 an hour (use your own) that is $187. A lost day for one person is 8 hours, $320; for all ten it is $3,200. The setup costs about 6% of that.
The Monday phone clinic. Book 15-minute slots from 8:30, two people at a time with two helpers: five slots, about 75 minutes of the clock, while the rest of the office works on laptops. With one helper, ten slots is 150 minutes. Keep the browser steps (sign-in, pass, authenticator registration) for the person to do alone before the slot, so the clinic is only the phone.
The person who is away
Someone travelling or on leave is the case that causes the real lockout. Their phone has the old setup, and the new suite does not know it.
- Microsoft 365: create a Temporary Access Pass that starts on their return. A pass can be valid for up to 30 days (43,200 minutes), so it can be created before they leave. Raise the policy's maximum lifetime first if needed.
- Google Workspace: generate backup codes and send one by message or phone. A new set switches the old one off, so give them one set and note the date.
- Do not use Require re-register MFA for them until they are back and have a phone in hand.
- Their phone mail will show an error. Tell them to expect it and ignore it until they have the pass or code. The old setup can stay until the old plan ends.
- If the old plan ends while they are away, see the renewal-date maths in the migration article. It may pay to move their seat last.
If the phone is lost or stolen while they are away, an admin on Microsoft 365 can choose Revoke sessions for that user, which invalidates their refresh tokens and forces sign-in again everywhere. Then issue a pass.
Tuesday cleanup
- Admin: open each person in the new suite and check the authentication methods list. There should be one authenticator and no old phone numbers.
- Everyone: delete the old authenticator entry for the old suite. A dead entry shows a code nobody can use.
- Shared logins belong in a password manager, not on someone's phone: our password manager rollout covers it. For info@ and support@, see shared mailboxes without a paid seat.
Sources
- Microsoft Learn: Transfer Microsoft Authenticator to a new phone, updated July 2026 (iCloud and Android backup steps, what restore brings back, passkeys)
- Microsoft Support: Back up your accounts in Microsoft Authenticator (same device type only, version 6.8.33, Google One move from January 2027)
- Microsoft Learn: Configure a Temporary Access Pass, updated November 2026 (lifetimes, one-time use, 10-minute limit)
- Microsoft Learn: Manage authentication methods for Microsoft Entra MFA (require re-register MFA, revoke sessions)
- Google Account Help: Sign in with backup codes (10 codes, 8 digits, single use)
- Google Workspace Admin Help: Recover an account protected by 2-Step Verification and Deploy 2-Step Verification (admin steps, new user enrollment period)
- Google Account Help: Transfer Google Authenticator codes
- Google Workspace Admin Help: Set up an Android device with an Office 365 or Exchange account
- Photo: Pexels, two iPhones on a desk, Pexels License
Planning the switch and want the domain and email checks on one list? Our free business tools cover them.
Explore free business tools