The Wear OS Transfer Protocol allows you to migrate a smartwatch to a new smartphone without performing a full factory reset. When this transfer fails, the watch typically gets stuck on “Connecting,” rejects the Bluetooth pairing key, or reports that it “Can’t connect to your new phone.” This breakdown happens when the previous phone maintains an active Bluetooth bond, when Google account authentication tokens do not match, or when local device discovery times out during the security handshake.
Quick Answer
To unblock the transfer, turn off Bluetooth on your old phone so it releases its connection bond. On your watch, navigate to Settings > General > Transfer watch (or “Connect to new phone”). On your new phone, verify you are logged into the identical Google Account, open the companion watch app (Pixel Watch or Galaxy Wearable), and accept the pairing prompt.
Device & Signal Snapshot
- Platform: Wear OS devices (Pixel Watch series, Galaxy Watch 4 and newer)
- Affected Feature: “Transfer Watch” / Seamless Device Handoff
- Common Errors: “Pairing rejected,” “Can’t connect to new phone,” or an endless discovery spinner
- Data State: Watch faces, local preferences, app data, and unsynced health metrics remain safe on device storage during troubleshooting
What Is Actually Happening?
Prior versions of Wear OS forced a complete storage wipe whenever you switched smartphones. Modern Wear OS systems handle migrations using an encrypted handoff protocol.
[Old Phone] [New Phone]
(Holds Active BLE Bond) (Attempts New Pairing)
│ │
├──────────────┐ ┌──────────────┤
▼ ▼ ▼ ▼
[BLE Connected] [Cloud Auth] [Device Found] [Auth Request]
│ │ │ │
└──────┬───────┘ └──────┬───────┘
│ │
▼ ▼
[Watch Rejects Handoff: Old Bond Still Active / Conflict]
To complete this transfer without wiping the watch, the operating system must:
- Revoke the existing Bluetooth Low Energy (BLE) link key with the old phone.
- Verify that the new phone is authenticated with the exact same Google Account currently registered to the watch.
- Generate a new set of shared cryptographic encryption keys between the new phone’s companion app and the watch’s Secure Element.
If the old phone is nearby with Bluetooth enabled, its radio will constantly re-establish its background connection. This interrupts the transfer protocol and causes the watch to reject the new phone.
Step-by-Step Resolution Protocol
1. Sever the Old Phone’s Bluetooth Grip
Do not simply unpair the watch in settings; disable the radio completely to eliminate background polling:
- Take your old phone and toggle Bluetooth OFF.
- If your old phone is being traded in, wiped, or is already powered down, proceed directly to Step 2.
- If the old phone is still accessible, open its Bluetooth settings and confirm the watch is no longer listed as “Connected.” If ghost pairings remain, see How to Remove “Ghost” Bluetooth Pairings That Block New Connections.
2. Reconcile Account and Network Environments
The transfer protocol relies on Google Play Services to verify device ownership:
- Ensure both your new phone and your watch are connected to the same local Wi-Fi network.
- Verify that the primary Google Account logged into your new phone matches the account on the watch. (Open the watch’s Settings > Accounts and backup > Google Account to verify the active address).
3. Initiate the Transfer Routine on the Watch
- On your watch, swipe down and tap Settings (gear icon).
- Scroll to General.
- Tap Transfer watch (on Samsung Galaxy Watches, this may appear as Transfer watch to new phone).
- Tap the checkmark to confirm. The watch will enter an active pairing broadcast state and display a prompt telling you to open your phone.
4. Complete the Handshake on the New Phone
- On your new phone, install and launch the appropriate companion app:
- Google Pixel Watch app (for Pixel Watch models)
- Galaxy Wearable app (for Galaxy Watch models)
- The app should automatically detect the watch in pairing mode. Tap Connect.
- A six-digit numeric passkey will appear simultaneously on the watch and phone screen. Confirm that the codes match and tap Pair.
- Allow the companion app 2 to 3 minutes to transfer local cryptographic credentials.
If your device is a Galaxy Watch and the handshake fails at the confirmation screen, follow the dedicated pairing recovery steps in Samsung Galaxy Watch 7/8: Troubleshooting “Something Went Wrong” Pairing.
What to Do If the Protocol Fails Completely
If the watch repeatedly fails the handoff or displays an unresolvable error message, the transfer protocol daemon has locked up. You can still migrate without losing your layout, apps, and preferences by using a cloud backup:
[Watch Settings > Accounts and backup] ──> [Back Up to Google One / Samsung Cloud]
│
▼
[Factory Reset Watch via Settings] <── (Wait for Cloud Backup to Finish)
│
▼
[Pair Fresh to New Phone] ─────────────> [Restore from Recent Cloud Backup]
- On the watch, go to Settings > Accounts and backup > Backup and ensure a fresh backup was uploaded within the last hour.
- Perform a standard reset on the watch (Settings > General > Reset).
- Open the companion app on the new phone and pair the watch as a new device.
- During initial setup, select Restore from backup to bring back your tiles, complications, app layouts, and system settings.
For a broader walkthrough on swapping phones across different wearable brands, review How to Transfer Your Smartwatch to a New Phone Without a Factory Reset.
Bottom Line
The Wear OS transfer protocol stalls when the old phone fights for the Bluetooth link or accounts do not match; disable Bluetooth on the old phone, confirm matching Google Accounts, and initiate the handoff directly from the watch’s General settings menu.