I got a new laptop and need to copy everything from my old laptop, but I don't have a USB drive, external storage, or an Ethernet cable, so I'm transferring the files over Wi‑Fi. After 13 hours, the transfer still says it has more than a day remaining. It started around 300 KB/s and has now dropped to roughly 2 KB/s. There are about 426,000 files in total, with around 350,000 still left to copy.
Both laptops are connected to the same Wi‑Fi network. The old laptop is set to a private network with network discovery and file sharing enabled, while the new laptop is set to public with the same sharing options enabled. The old laptop originally showed a 5 GHz connection and the new one showed 2.4 GHz. I tried forcing 5 GHz through Device Manager, but performance became worse, and the old laptop is now showing 2.4 GHz.
Could the network settings be causing this, or is the huge number of small files—such as Python files, datasets, cache folders, Git data, and editor files—the main problem?
4 Answers
The most reliable solution is to remove the old laptop’s drive and connect it to the new one with a SATA-to-USB adapter or another external drive enclosure. That avoids Wi‑Fi overhead and is usually much faster and more stable. An external drive would also be useful for future transfers and backups.
Hundreds of thousands of tiny files can be extremely slow to transfer, especially if the source laptop uses a mechanical hard drive. Each file requires separate filesystem and network overhead, so the transfer rate can collapse even when the Wi‑Fi connection itself is fine. If possible, compress the folders into one or a few archive files first, then transfer those archives and extract them on the new laptop.
If you later get Ethernet adapters or cables, a wired connection should be much faster and more consistent than Wi‑Fi. Don’t assign both laptops the same IP address, though—that causes an address conflict. Let them obtain addresses automatically, or configure two different addresses on the same network.
A local transfer tool such as LocalSend may perform better than ordinary network file sharing and is easy to use on devices connected to the same network. Still, it won’t completely eliminate the slowdown caused by hundreds of thousands of small files, so archiving them first is likely to help the most.

Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures