If your eSIM transfer is pending, the most common reasons are carrier approval delays, old device still holding the profile, weak Wi-Fi during transfer, identity verification checks, software mismatch between phones, or temporary server issues.
This is a common problem when upgrading to a new phone. You try to move your eSIM, but instead of completing instantly, the process stays on Pending.
The good news: most pending transfers can be completed with the right steps.
You may notice:
- Transfer Pending for a long time
- new phone waiting for activation
- old phone still has service
- QR transfer not finishing
- No Service on new device
This guide explains exactly why your eSIM transfer is pending, how to fix it quickly, and how to move your plan successfully.
Quick answer: Keep both phones nearby, connect both to strong Wi-Fi, update software, disable the old line if required, restart both devices, and wait for carrier confirmation.
1. Carrier Approval Is Still Processing
This is the #1 reason.
Some transfers require backend approval from the carrier.
This can take minutes or longer depending on the provider.
Fix:
- Wait 5–15 minutes
- Keep phones online
2. Old Phone Still Holds the eSIM Actively
The original device may still be using the profile.
Fix:
- Turn OFF the old phone temporarily
- Disable the eSIM line on old device if instructed
3. Weak Wi-Fi Interrupts Transfer
Many eSIM transfers rely on secure internet communication.
Fix:
- Use stable high-quality Wi-Fi
4. Software Versions Are Outdated
Older iOS or Android builds can delay transfer tools.
Fix:
- Update both phones fully
5. Identity Verification Needed
Some carriers request OTP, email confirmation, or account login.
Fix:
- Check SMS
- Check email
- Complete verification prompts
6. Bluetooth or Device Pairing Needed
Some phone-to-phone transfer flows need nearby connectivity.
Fix:
- Enable Bluetooth
- Keep devices close together
7. Temporary Server Delay
Busy activation systems can slow migrations.
Fix:
- Retry later if stuck too long
8. The eSIM Must Be Reissued Instead
Some providers do not support live transfer and instead issue a new QR code.
Fix:
- Request fresh installation details
Helpful guides:
9. New Phone Is Not Compatible
Not every model supports eSIM transfer equally.
Fix:
- Check compatibility first
Helpful guide: Which Phones Support eSIM in 2026?
10. Restart Solves Many Pending States
Phones sometimes hold stale activation sessions.
Fix:
- Restart both devices
Best Way to Transfer Successfully
- Strong Wi-Fi
- Updated software
- Both phones nearby
- Old phone powered on initially
- Verification ready
How to Fix on iPhone
- Settings > Cellular
- Add eSIM
- Transfer From Nearby iPhone
- Keep both devices unlocked
How to Fix on Android
- Settings > SIM Manager
- Add eSIM
- Use provider transfer method
Fast 60-Second Fix Checklist
- Connect strong Wi-Fi
- Update phones
- Enable Bluetooth
- Restart both phones
- Check verification messages
- Wait 10 minutes
Common User Mistakes
Turning off old phone too early
Some transfers need both devices active.
Using weak hotel Wi-Fi
Often causes pending status.
Ignoring verification prompts
Transfer may pause silently.
Assuming instant completion always
Some providers take longer.
When to Contact Support
Contact support if:
- pending lasts over 30 minutes
- old phone lost service and new phone still pending
- transfer repeatedly fails
Helpful page: Contact Support
Final Thoughts
If your eSIM transfer is pending, the issue is usually approval timing, device communication, or connection quality — not a broken eSIM.
Keep both devices connected, updated, and nearby for the fastest result.
Need reliable travel connectivity on your new phone? Browse travel eSIM plans before your next trip.
FAQ
How long should eSIM transfer pending last?
Usually a few minutes, but some providers may take longer.
Should both phones stay on?
Yes. Many transfers require both devices active.
Does Wi-Fi matter?
Yes. Strong Wi-Fi is very important.
Can I restart both phones?
Yes. This often clears stuck pending states.
Is the eSIM broken?
No. Usually it is a transfer process issue.

