Short answer: overheating after migrating from an old phone is normal — it does not mean the new phone is faulty. Migration copies your data across, but indexes, caches and thumbnails all have to be generated again on the new phone: the system rebuilds search indexes, re-downloads your apps and regenerates thumbnails for photos and videos. All of that keeps the processor busy, so heat and faster drain for a while after the progress bar finishes is expected. The fix order is simple: plug it in, join Wi-Fi, stop fiddling, leave it overnight — and only then look at Settings → Battery if something still seems wrong.
What the phone is still doing after the progress bar
"When the migration bar finishes" only means the files arrived. It does not mean the system is finished with them. In the background there is a whole second shift:
- Rebuilding search indexes. Spotlight, Mail, Messages and Notes all rebuild their indexes; this is the most CPU-hungry job of the lot.
- Re-downloading apps. Apps and their assets get fetched again. Apps carried over from the old phone may also not yet be adapted to the new system, so their first run can involve a data migration or a cache rebuild — which is why watching for app updates matters.
- Regenerating thumbnails and caches. The photo library redoes thumbnails, face and scene detection, videos rebuild preview frames, and chat apps rebuild their media caches.
- Syncing iCloud. iCloud Photos, Keychain, Notes and Health data all have to be reconciled.
None of this is visible, which is why the phone is still warm and still draining after the transfer appears to be done. The same mechanism is covered in more depth in Is a new iPhone getting hot and draining fast normal?.
The three migration routes are not equally heavy
| Route | Heat during the transfer | Background load afterwards |
|---|---|---|
| Quick Start (phone to phone) | Noticeable, worse with a bigger library | Somewhat lighter — data moved in one pass |
| Wired transfer | Usually the shortest, because it is faster | Similar to Quick Start |
| iCloud restore | Not necessarily hot, since data comes from the cloud | Can be heavier for days, with local organising and app downloads |
Whichever route you took, the tidying-up work runs on the new phone either way, so do not judge the hardware by how hot the transfer itself felt.
What makes it worse
Two factors beyond raw data size are easy to overlook:
① Old apps that have not adapted. Apps carried over from the old phone are older builds. On a new system their first run may migrate data, rebuild caches or even wake up abnormally often. So open the App Store updates list after migrating and bring everything up to date — it measurably reduces background churn.
② The habits and background load that came with the restore. If the old phone had plenty of Background App Refresh, live location and always-on syncing enabled, that exact configuration arrives on the new phone, so it gets woken far more often and runs warmer. This matters even more when the old battery was already worn: the heavy patterns you had grown used to (gaming while charging, long recording sessions, many resident apps) travel across with the data, so it is worth reviewing your settings on the new device. That threshold is explained in What is Battery Health?.
The order to do things in
Work through this and most cases need nothing more:
- Charge, join Wi-Fi, leave it overnight. This is the single most effective step. Background jobs hate running while the battery drains, so charging lets them run properly; Wi-Fi speeds up app downloads and iCloud sync; and with the screen off, cooling is at its best. Take the thick case off, and keep it away from duvets and hot cars.
- Check the battery list. Open
Settings → Batteryand look at the last 24 hours. An app whose share of drain is wildly out of proportion to its on-screen time is your suspect. Install every pending App Store update at the same time, especially for older apps carried over from the previous phone. - Tighten refresh and location. In
Settings → General → Background App Refresh, keep only chat and mail apps — switching the rest off does not break notifications, which travel over Apple's system-level push service. InSettings → Privacy & Security → Location Services, move apps that do not need live location to While Using. - Force restart if needed. Press Volume Up, press Volume Down, then hold the Side button until the Apple logo appears. It clears stuck background processes, which is exactly the situation when one migrated app misbehaves in the background.
If the old phone's battery health was already low, it is also worth opening Settings → Battery → Battery Health & Charging on the new phone to check Maximum Capacity, and confirming Optimized Battery Charging is on — that is the long-term care that actually matters.
When it is actually a problem
Concrete lines you can check yourself, so you do not over-worry:
- more than a week after the migration finished, with obvious heat and drain rather than occasional warmth;
- a body that is hot to the touch, with the screen frequently dimming on its own and clearly stuttery scrolling — that is thermal protection throttling, judged the same way as in Is iPhone 18 overheating normal?;
- every app update installed, yet one app still sits permanently at the top of the usage list — and the curve returns to normal once it is removed;
- more than 15% lost overnight on standby (roughly eight hours).
If any of those apply, then look further: erase and reinstall, or have Apple check the phone. Before that, let it finish the background work.