My IPhone Duo setup stalled on the calculating screen while moving my messages. I got it on launch day, and my old phone was still plugged into the kitchen outlet when I gave up.
Do you actually use direct phone-to-phone transfer, a cloud restore, or a fresh setup, and why?
Don’t erase or trade in the old phone until you’ve checked messages, photos, authenticator apps, and anything stored only on the device.
I’d use direct phone-to-phone transfer first because it usually carries over the most with the least cleanup. Keep both phones charging, close together, and leave them alone for a few hours. The “calculating” stage can look frozen when the message history is large, so I wouldn’t restart it repeatedly unless there’s clearly no activity after a long wait.
If direct transfer fails twice, I’d switch to a cloud restore rather than keep fighting it. Fresh setup is my last choice because signing back into every app and finding missing settings gets old fast. It makes sense if the old phone has years of clutter or recurring software problems, but otherwise it creates more work than it saves.
Direct transfer could easily tie both devices up for hours and have an incredible amount of messages to pull through. I would attempt a wired connection if possible, assuming your devices support it, and allow Messages to sync from iCloud later rather than waiting for a progress bar to finish calculating.
Don’t wipe or trade in the old phone until you’ve checked that the message history and attachments actually arrived. A transfer can look finished while older photos, voice notes, or threads are still missing.
I’d use direct phone-to-phone for the basic setup, but I wouldn’t keep restarting it just because Messages sits on “calculating.” @primecache’s wired suggestion may help with speed, though it won’t necessarily fix a damaged message index or a nearly full source phone. Make a fresh backup, confirm Messages in iCloud is enabled on both devices, and let the new phone finish syncing on Wi-Fi and power.
Keep the old phone untouched for a few days. That safety net matters more than shaving an hour off setup.
The missing factor is the size difference between the memory occupied by data on the old device and its total capacity. If it is close to the second parameter’s value, delete unnecessary videos, podcasts, and other media files and try again. Switching from direct transfer to cloud-based account restore also not relevant.
Phone-to-phone migration is suitable when the old phone is functioning correctly, but calculating its storage utilization should not be interpreted as an indefinite delay of the transfer session. MMS contents frequently take the lion’s heart in messages storage, so years of accumulated videos, group chats’ multimedia, and other data may consume all the storage space.
Prior to resuming balance checking after migration, cross-verify a dozen older conversations’ approximate dates with the attached files. If a particular message’s row appears in the Chats list, it does not mean that all multimedia contents are held locally on the receiving device.
The hidden downside of direct transfer is that “plugged in” does not mean “safe to walk away from.” Both phones need to stay close together, and moving the new phone around the house can interrupt the device-to-device connection without giving you a useful error. If the old phone stayed in the kitchen while the new one wandered elsewhere, I’d suspect that before assuming the Messages library was broken.
I’d still use phone-to-phone migration, but only when I can park both devices side by side and leave them untouched. Disable VPNs, avoid switching Wi-Fi networks, and stop checking the new phone every few minutes. “Calculating” is annoyingly vague, though I wouldn’t give it unlimited time. If the storage indicator and network activity show no change after a long stretch, another attempt under the same conditions probably will not magically fix it.
The alternative people overlook is an encrypted backup to a Mac or PC, followed by a restore to the new phone. The encryption setting matters because an unencrypted computer backup leaves out certain sensitive data such as saved passwords and Health information. It takes computer storage and a cable, but it gives you a backup file that is separate from both phones. That feels less risky than depending entirely on a transfer screen that refuses to explain what it is doing.
After restoring, expect Messages and photos to keep filling in for a while if you use iCloud syncing. Don’t start deleting apparent duplicates or “cleaning up” conversations during that period, since synced deletions can spread back to the old phone too. I’d treat launch-day setup as unfinished until calls, authentication codes, banking apps, and a few genuinely old message attachments all work on the new device.
Before you touch that old phone again, open your authenticator app and make sure the codes actually moved. This is the thing that bites people. Message history at least fails loudly on the calculating screen. Two-factor seeds can sit there looking fine and then you find out they didn’t migrate the moment you try to log into your bank, and by then you’ve already wiped the source. @primecache flagged authenticator apps in passing, but I’d bump it to the top of the checklist instead of lumping it in with photos.
The rest of your thread is good. I’m adding to it that eSIM itself has some wrinkles, unrelated to this topic. They sometimes prompt to transfer the line, and sometimes they don’t, and if you have questions, you have to call your carrier anyway, confirm that you can make a call, before you consider the setup ‘done’.
Don’t keep rerunning the same transfer on whatever software the new phone shipped with. Launch-day phones can arrive with an older build than the one installed on your old phone, and migration gets weird when the source is ahead of the destination.
Set up the Duo temporarily without moving your data, install the latest available update, then erase only the new phone and start Quick Start again. Your old phone stays untouched through that process. If the old phone is running beta software, the new phone may need the matching beta before it can accept the transfer.
Yes, I’d still use direct phone-to-phone transfer. It saves a lot of app setup and account fiddling. I just wouldn’t sit through another endless “calculating” screen until both phones are on compatible software. Keep them together and charging once the real transfer starts, but updating the destination first would be my next move here.
Afterward, search Messages for a couple of distinctive old phrases instead of judging the transfer by the conversation list. That quickly tells you whether older content is genuinely searchable or merely still downloading.
Doing this on launch day makes a slight difference to the backup advice. Everyone is saying to fall back to a cloud restore if the direct transfer fails twice, and that’s generally good advice. But launch day is when Apple’s activation and iCloud servers are getting slammed by everyone else who just got their devices out of the box. A cloud restore that would take an hour on a Tuesday is going to crawl for most of the day on a launch day, and you’ll be staring at a different (and less informative) progress bar than the calculating screen.
So if the direct transfer stalls, I wouldn’t automatically jump to cloud. The local encrypted computer backup that @pandaking brought up is the smarter move on a busy day, because it doesn’t depend on Apple’s servers being in a good mood. It’s slower to set up but it actually finishes when it says it will.
The one thing nobody’s really flagged: check the old phone’s battery and heat before you blame the transfer. Two phones running a big migration side by side get warm, and if the old one throttles or the screen’s been off long enough to nap, the connection can quietly stall without any error. Keep both awake and cool, not just plugged in. And @nick_codes is right to shove authenticator seeds to the top of the list, that’s the one that genuinely ruins your week if you wipe too early.
I wouldn’t count on a guaranteed finish time with any of these options. Direct transfer would be my choice without a deadline, but I’d be cautious about @shadowwolf2011sync’s claim that a computer restore finishes when it says it will. If you need a working phone before heading out, I’d leave the migration for later rather than spend that window trying another method.