Introduction

A cPanel account transfer can move the website successfully while SFTP access stops working for one or more users. In many cases, the main account still exists, but additional SFTP accounts were not recreated cleanly, their home directories now point to the wrong path, or shell and chroot settings no longer match the new server.

Treat this as an account-definition problem instead of a generic password failure. Start by proving which SFTP users should exist on the destination server, then confirm where each one is supposed to land and whether the new host still allows that access model.

Symptoms

  • SFTP users that existed before the transfer are missing from cPanel or the server
  • Login works for the main cPanel user, but additional SFTP accounts fail
  • SFTP clients connect but land in the wrong folder after the transfer
  • A migrated SFTP account now gets permission denied on paths it used before
  • Only some transferred SFTP users are broken while others still work
  • The issue started immediately after cPanel migration, restore, or account move

Common Causes

  • Additional SFTP accounts were not restored during the transfer
  • The migrated account now uses a different home-directory path than the old server
  • The SFTP user is mapped to a directory that no longer exists on the destination host
  • Shell or chroot settings changed during the migration
  • Passwords, SSH keys, or account state were not carried over cleanly
  • The new server uses a different SFTP or jailed-shell policy than the old one

Step-by-Step Fix

  1. Confirm which SFTP users should exist by comparing the new server with the old account records or backup, because you need an exact list before deciding whether the problem is missing accounts or broken access.
  2. Check the destination cPanel or server configuration for each expected SFTP user, because transferred sites often arrive without the additional account definitions being recreated.
  3. Verify the home directory assigned to each SFTP account on the new server, because path changes during migration can leave a user pointed at a folder that no longer exists or is no longer correct.
  4. Confirm that the mapped directory actually exists and belongs to the right account context, because an SFTP login can succeed but still fail immediately when the user lands in a missing or inaccessible path.
  5. Review shell, jailed-shell, or chroot behavior for the migrated users, because a different server policy can make a previously valid SFTP account stop working or expose the wrong directory tree.
  6. Reset the affected SFTP password or reapply the intended authentication method if there is any doubt about transfer integrity, because restored credentials do not always remain usable after an account move.
  7. Test with one affected SFTP account using a clean client session and verify the exact landing directory, because that separates authentication success from directory-mapping failure.
  8. Compare one working SFTP user with one broken user on the same server, because differences in home path, shell, or ownership usually show which part of the restore went wrong.
  9. Document the final SFTP account list, directory mappings, and access model after recovery, because additional SFTP users are easy to miss during future cPanel transfer validation.