I switched my web hosting provider and backed up my website on my computer. Then, I tried to transfer all the data from my old hosting to the new FTP server using TotalCommander. However, some folders and files such as "www" and "public_html" did not copy due to copying restrictions.

In an attempt to solve the problem, I downloaded and installed FileZilla and attempted to download those folders. Despite the program working fine for a few minutes, it ultimately failed, resulting in 10,000 failed transfers. The error message read: "unable to start transmission."

It is essential to verify the access rights to the files. It appears that the unpacking may have been done without considering the hosting provider's specific requirements. For instance, the website's root directory should contain an index file, while the unpacked archive might be a home directory from the previous hosting provider and not the website's root.

To solve this, one needs to locate the exact location of the site files and move them to the website's root directory. Additionally, the administrator folder must have a configuration file that includes connection details to the database.

In such situations, it's always best to seek assistance from the hosting provider's support team, as they can guide you through the entire process and ensure that everything is set up correctly.

When you first attempted to transfer your website data using TotalCommander, the inability to copy essential folders like "www" and "public_html" indicates that the software may have had limited access permissions to these directories. This restriction is often encountered with system folders critical to the functioning of a website, and it's essential to have the necessary credentials and permissions to access and transfer such files.

Subsequently, your switch to FileZilla was a logical step, as it is a widely used FTP client known for its reliability. However, the 10,000 failed transfers accompanied by the error message "unable to start transmission" indicate a more complex issue. This could point to potential network instability, server load, or restrictions imposed by the new hosting provider that hinder the transfer of data.

To address these challenges comprehensively, I would recommend the following steps:

1. Contact Technical Support: Engage the technical support teams of both your old and new hosting providers. They can provide specific insights into any limitations or requirements that may be affecting the transfer process. They can also offer guidance on best practices for migrating large volumes of data and may suggest alternative methods or tools for a smoother transition.

2. Check Server Stability: Ensure that the FTP server on the new hosting provider's end is stable and responsive. High server loads or network issues can contribute to failed transfers. It's crucial to confirm that the server is capable of handling the incoming data.

3. Review Transfer Logs: Examine the logs provided by FileZilla to identify the exact nature of the failed transfers. Detailed error logs can reveal specific reasons for the failures, such as file permissions, network interruptions, or server-side restrictions.

4. Consider Alternate Transfer Methods: If traditional FTP transfers continue to encounter issues, consider alternative methods such as using SSH (Secure Shell) for secure file transfers, or utilizing specialized migration tools provided by hosting providers.

Successful migration of website data between hosting providers requires a thorough understanding of the specific requirements and limitations of both the old and new hosting environments. Open communication with technical support teams, rigorous testing of transfer methods, and a meticulous review of error logs are essential to overcome the challenges you've encountered.