JSOPanel Get started
Help Center › Administrators › A migration says the account "already exists on this server and did not come from this backup"

A migration says the account "already exists on this server and did not come from this backup"

Why a cPanel or DirectAdmin migration refuses an account name that is already here, and what the "Limits and access" lines of a restore or transfer mean.

Bringing an account across from cPanel or DirectAdmin stops at once with ACCOUNT already exists on this server and did not come from this backup. Nothing was done.

What it means

An account with that name is already on this server and the backup you chose is not the one that made it. Two different customers can share a name, and pouring one's files, mail and databases over the other's would overwrite them. Nothing was changed. A migration that stopped part-way and is run again from the same backup is recognised and carries on; this message is for a different one.

Steps

  1. Decide whether the account already here is the same customer. Look at it under Accounts.
  2. If it is a leftover you want gone, remove it first, then run the migration again:
    sudo jsopctl account clean ACCOUNT
    That deletes the account's files, mail and databases. Run it only for an account you are sure about.
  3. If it is a different customer, the name has to change on the old server before the backup is made. A migration never renames an account.

The "Limits and access" lines

A restore or transfer that creates an account now ends with a Limits and access section. Each line says whether a limit came back: the disk limit, CPU, memory and process limits, restricted PHP, the account's own PHP program, the process limit and shell access.

  • the disk limit was NOT applied usually means disk quotas are not switched on for this server. Turn them on under Server Settings, then save the package on the account again.
  • shell access could not be put back means the locked room (jail) could not be built. The account has no shell until it can, which is the safe state. Open Accounts → Manage and turn shell access on again, and read the reason shown there.
  • this backup was taken before the account's limits were recorded in it means the backup came from an older release. Open Accounts → Manage and save the package again.
Tip: an account that already existed keeps the limits it has now. A restore only puts limits back for an account it just created.