Backups, Restore and Migration
How automatic backups are scheduled, kept and copied to another server, how to restore accounts, files and cPanel backups, and how to migrate accounts from a cPanel or intoPanel server.
This page covers the admin menu sections Backups (Backup Settings, Restore Backups, Accounts to Back Up, Restore Files and Folders) and Migration and Restore (Server Migration, Migration History, Restore an Account from a File, Turn an Addon Domain into an Account).
What a Backup Contains#
An intoPanel account backup is one compressed file (.tar.gz). It holds:
- the account's whole home folder
/home/<username>, with its websites, mail and other files; - a dump of each of its databases;
- its database users, with their password hashes and the databases they may use;
- the settings needed to bring the account back: its websites, package and limits, DNS zones, mail forwarders and mailbox passwords.
Backups made from the admin area belong to you. Clients cannot see, download or delete them, and they do not count towards an account's disk space. A client can also make one backup of its own in the client area; that one is kept separately in the account's folder and does count towards its disk space.
Before a backup starts, the panel checks the free space. There must be room for about what the account uses, plus 10% and 100 MB; otherwise the backup fails with a message naming the numbers.
Good to know:
- A website keeps running while it is backed up. Files that change during the backup are taken as they are at that moment.
- Deleting an account deletes its backups on this server. Copies on a remote destination stay there.
Backup Settings: Schedule#
In the admin area, open Backups → Backup Settings (Backup Settings).
The form is in five numbered parts. Fields that do not apply to the chosen frequency are hidden.
- Tick Make backups automatically.
- Under 1. When, choose How often: Every day, Once a week or Once a month, and At (server time), the hour the backups begin. The default is 02:00.
- Every day: tick On these days. With all seven ticked, backups run every day.
- Once a week: choose the weekday under On.
- Once a month: choose On day (1 to 28, so every month has it).
- Under 2. How many to keep, set the numbers (see "Backup Settings: Copies Kept").
- Under 3. Safety, optionally set Skip the backups when the disk has less free than (%). When a smaller share of the backup disk is free, the backups do not start and you are told. Tick Back up suspended accounts too if they should be included.
- Under 4. Which accounts, choose every account or only the ticked ones (see "Accounts to Back Up").
- Part 5 sets an optional copy to another server or disk (see "Backup Settings: Remote Destination").
- Click Save settings.
At the chosen hour, the selected accounts are backed up one after the other. Which accounts are included is set under Which accounts (see "Accounts to Back Up"). The rest of the form sets how many copies are kept and where (see the next sections).
Good to know:
- If an automatic backup fails and Tell me when an automatic backup failed is ticked under Alert Contacts, you get an email with the reason.
- When a remote destination is set up, you also get a notification after each run, saying which accounts were copied and which were not.
Backup Settings: Copies Kept#
Part 2. How many to keep, for each account of the Backup Settings form sets how many backups are kept on this server for each account:
- Latest backups (1 to 30; the default is 3): the number of automatic backups kept. When a new one is made, the oldest beyond this number is deleted.
- Weekly backups, as well (0 to 30), shown with daily backups only: the backup made on the weekday chosen beside it (taken from the backup made on) is also kept as a weekly backup, and this many weekly backups are kept. Empty or 0 keeps none.
- Monthly backups, as well (0 to 30), shown with daily backups only: the backup made on the day of the month chosen beside it is also kept as a monthly backup, and this many are kept. Empty or 0 keeps none.
For example, daily backups with 7 kept, 4 weekly and 3 monthly give you the last week day by day, the last four weeks and the last three months.
A weekly or monthly copy is a second name for the same file (a hard link). It takes no extra space until the daily backup it came from is deleted.
Good to know:
- A backup started with Back up now counts as an automatic backup, so it also counts towards the number kept.
- A second automatic backup on the same day replaces the first one of that day.
Run the Scheduled Backup Now (under the settings) makes the scheduled backups at once, with the saved settings, without waiting for the hour or the day: the selected accounts one after the other, the copies to the second place, and the weekly and monthly copies. From the server's command line the same is bash /root/intopanel/install/daemon-call.sh backup.runnow.
Where Backups Are Stored#
On this server, backups are kept in /var/backups/intopanel, a folder only root and the panel can read. Backup Settings shows this folder and its free space under Stored in and Free space there.
The administrator's backups are filed by date, one file per account:
/var/backups/intopanel/daily/<date>/accounts/<account>.tar.gz
/var/backups/intopanel/weekly/<date>/accounts/<account>.tar.gz
/var/backups/intopanel/monthly/<date>/accounts/<account>.tar.gz<date> is the day the backup was made, such as 2026-10-08. Automatic backups, and backups started with Back up now, are filed under daily. The weekly and monthly folders hold the copies kept longer (see "Backup Settings: Copies Kept").
A client's own backup is kept in /var/backups/intopanel/<account>/. Uploaded backup files, and backups kept after restoring from the remote destination, wait in /var/backups/intopanel/_restore.
The remote destination uses the same layout inside its folder: daily, weekly or monthly, then the date, then accounts/<account>.tar.gz. There, the first part follows How often the backups run.
Good to know:
- Put
/var/backups/intopanelon a separate disk if you can, or copy backups to a remote destination. A backup on the same disk as the accounts does not help if that disk fails. - This layout is the same as cPanel's, so a cPanel backup folder copied in here can be restored too (see "Restoring cPanel Backups").
Backup Settings: Remote Destination#
The Copy to another server or disk part of Backup Settings copies every automatic backup to a second place.
- Choose the Method:
- SFTP (recommended).
- FTP with TLS.
- FTP (not encrypted): it sends the password and the data unprotected.
- Another folder on this server: a second disk or a mounted network share.
- For SFTP and FTP, enter the Host, the Port (22 for SFTP and 21 for FTP when left empty), the Username and the Password. A stored password is kept if you leave the field empty.
- Enter the Folder on that server, such as
backups. For a folder on this server, give the full path, such as/mnt/backup. The folder must already exist, and system folders and/homeare refused. - Set Copies kept per account on that server (1 to 365). Older copies there are deleted.
- Under Where backups are kept, choose to keep backups both here and on the second place, or Only on the second place. With the second choice, the copy on this server is removed once it has arrived there.
- For FTP with TLS and a self-signed certificate, tick accept a certificate that cannot be verified.
- Click Save settings, then Test the remote server. The test uploads a small file with the saved settings and removes it again.
Good to know:
- With SFTP, the other server's key is remembered at the first connection and must stay the same afterwards.
- The Other server column under "Accounts to Back Up" shows each account's last copy and how many copies are there.
- The remote destination's settings, including its login, can be copied to other servers with the Settings Sync Group.
Accounts to Back Up#
In the admin area, open Backups → Accounts to Back Up (Accounts to Back Up). The table lists every account with:
- Automatic: whether it is included in automatic backups;
- Backups here: how many backups of it are on this server, and their total Size;
- Newest (UTC): the time of the newest backup, Running now while one is being made, or Last one failed (hover over it for the reason);
- Other server: the result of the last copy to the remote destination, and how many copies are there.
To back up one account now, click Back up now in its row. The backup runs in the background, is kept as an automatic backup and is copied to the remote destination when one is set.
To choose which accounts are backed up automatically, go to Which accounts in Backup Settings:
- Every account, including ones created later, or
- Only the accounts ticked here: tick the accounts.
Then click Save settings.
Good to know:
- Suspended accounts are left out of automatic backups unless Include suspended accounts is ticked.
- Only one backup of an account can run at a time.
Restore Backups#
In the admin area, open Backups → Restore Backups (Restore Backups). The Restore Backups card shows every account that has backups, from this server and from the remote destination.
- Pick the backup in one of two ways:
- On the Pick an Account First tab, choose an account, then a date in the calendar.
- On the Pick a Date First tab, choose a date, then an account.
- Under Options, choose what to restore:
- Include subdomains and other domains.
- Include mail settings.
- Include databases.
- Restore from: Local or Remote.
- Give It a Dedicated IP Address.
- Click Add to the List. Repeat for other accounts. Each account can be on the list once.
- Under Restore at the same time, choose how many accounts are fetched and restored side by side, from 1 to 10.
- Click Restore under Accounts to Restore.
Each account being restored gets its own box at the top of the page, with its progress and its own log. There are as many boxes as accounts restored at the same time. Each box keeps the same size; its log scrolls inside it. When an account is finished, its box is cleared and the next account on the list starts in it; a box with no account left folds up to its title line (the −/+ button folds or opens a box by hand). The Restored accounts table shows the result for each account: Completed, Completed with warnings (something in it was not restored, such as a skipped database, or a file in the backup that could not be written; cPanel skips such files too, and the log lists them) or Failed, with View log to open that account's own log. These logs are kept for 30 days, and the full log of every account also stays in the restore log. Nothing is restored until you click Restore.
In each box:
- Pause holds that account at its next step; Resume carries on.
- Cancel stops that account. Parts already restored stay; the next account on the list starts in the box.
Stop the whole restoration cancels the accounts in progress and leaves the rest of the list unrestored.
Restoring several accounts at once is faster, but it uses more disk, memory and database time. On a busy server, choose fewer.
Fetching from the remote destination: a backup on an SFTP, FTP or FTPS destination is fetched in parts over several connections at once, 4 unless you change it under Backup files on this server → Connections per backup fetched from the remote destination (1 to 16). This is much faster when the backup server limits the speed of each connection. The restore log shows the size, time and speed of every fetch. If the backup server allows only a few connections per login, choose fewer; 1 fetches the plain way over one connection. If fetching in parts does not work, the backup is fetched over one connection by itself. Server Migration copies packed accounts the same way.
When an account is restored, its files, databases and mailboxes from the backup replace the current ones. Files that are in the account now but not in the backup are left in place. An account that is not on this server yet is created, without a panel password until you set one on its account page.
From a backup made by a cPanel server, the account is also put on the package it had there. If this server has a package of that name it is used as it is; otherwise the package is made from the limits the account had. An account that already has a package here keeps it. An account that had no package of its own on the other server (cPanel's "default"), or one whose name cannot be used here, gets a package named after it, such as alice_custom, made from its limits. Each website keeps the PHP version it ran on; when that version is not installed on this server, the website uses this server's default PHP version and the restore log says so.
When a restore is finished, the panel looks after the account's certificates. Every website whose DNS points at this server gets a free certificate and sends its visitors to HTTPS. A website whose DNS still points elsewhere is named in the restore log; the daily Automatic SSL run gets its certificate once the DNS points here, and HTTPS is enforced from then on. Nothing is requested when Automatic SSL is switched off or not enabled for the account.
An account created by a restore from a cPanel backup signs in to the panel with the password it had on the other server.
Several accounts in one go: on the Pick an Account First tab, tick the accounts in the list, or use Tick: all not on this server, then click Add to the List. Each ticked account is added with its backup of the chosen date or, when it has none that day, its newest backup. The accounts on the list are restored one after the other, never at the same time, so the server is not overloaded. A list holds up to 500 accounts. The list is kept on the server: if the panel is restarted while it is being restored, for an update for instance, the restoration goes on by itself about half a minute later, starting again with the account it was at.
Backup files on this server: a backup fetched from the remote destination for a restore is kept on this server afterwards, under a name such as backup-11.7.2026_00-00-30_server1.tar.gz (the account and the backup's day). It is listed under Backup files on this server with a Remove button, and on the Restore Backups card as a backup on this server (source Local). So an account, or a part left out the first time (its databases, say), can be restored again at once, without fetching the file again. Restoring the same remote backup again also uses the kept copy. To have fetched backups removed after restoring instead, untick Keep backups fetched from the remote destination on this server after restoring them; files kept before stay until you remove them. Uploaded files are always kept until removed. Kept files take disk space in /var/backups/intopanel/_restore: remove them when no longer needed.
Good to know:
- Remote backups appear once a remote destination is set up. Click Look at the remote destination again to read the remote folder afresh.
- Only one restore or migration can run at a time.
- To restore single files instead of a whole account, use "Restore Files and Folders".
Restoring cPanel Backups#
You can restore account backups made by cPanel/WHM on the Restore Backups page.
From a cPanel backup folder:
- Copy the folder into
/var/backups/intopanel, keeping its layout. For example, copy2026-10-07/accounts/,weekly/…ormonthly/…. - Open Restore Backups. The accounts and dates appear in the Restore Backups card. Restore them as described in "Restore Backups".
Backups at the remote destination are listed too, including cPanel ones.
From single files: cpmove-user.tar.gz, user.tar.gz or backup-DATE_user.tar.gz. Copy them into the backup folder, or upload them under Upload a backup file (see "Restore an Account from a File").
Files you copy in by hand are given the usual owner and permissions (root, group intopanel, 0640) when they are listed.
What comes across from a cPanel backup:
- Restored: the home folder (websites and mail), databases with their users and passwords, mailboxes with their passwords, forwarders, addon domains and subdomains, DNS records and cron jobs.
- Not taken: SSL certificates (get new ones under Automatic SSL) and FTP accounts.
DNS records: each domain's zone is made here pointing at this server, and then the other records of the old zone are added to it, such as ns1, ns15 or vpn A records that point at other servers, CNAME, TXT, SRV and CAA records. Records that pointed at the old server's own address now point at this server. Left as made here: the domain's own NS records, MX, SPF, DKIM and DMARC records (mail is handled by this server), cPanel's own names (cpanel, whm, webdisk and the like), and any name this server already answers. The restore log lists how many records were added, and names any mail server the old zone pointed at elsewhere.
Cron jobs: paths in the old home folder (/home/olduser/, /home2/olduser/) are changed to the account's home folder here, and cPanel's PHP programs (ea-php81, /usr/local/bin/php) to this server's. @reboot jobs are not taken, nor jobs that download code from the internet and run it (the restore log names them; see "Secure /tmp and Cron Check" under Security). The jobs are listed on the account's Cron Jobs page.
Database names keep their ending; the part before the first _ becomes the account's name. An account that was renamed on cPanel without renaming its databases (its databases still start with the old name, such as oldname_wp) keeps them under their own names: the account here takes that prefix, so the websites' settings still name the right databases, and its new databases start with it too. When that cannot be (some of its databases start with its own name and others with the old one, that prefix belongs to another account here, or the account already has databases), they are renamed to the account's prefix instead, and so are their database users. Whenever a database or database user is renamed, the new names are written into the websites' settings files in the account's home folder (wp-config.php, configuration.php, .env and similar settings files; not uploads, caches or mail), and the restore log lists the files changed. Check any website whose settings are kept elsewhere.
Good to know:
- To move accounts straight from a running cPanel server, use Server Migration instead. It also brings FTP accounts and the panel password.
Restore Files and Folders#
In the admin area, open Backups → Restore Files and Folders (Restore Files and Folders). This puts single files or folders of an account back as they were in one of its backups, without restoring the whole account.
- Choose the Account and click Show Backups. The account's backups on this server are listed with the time they were made and their size.
- Click Browse next to a backup.
- Click folder names to open them. The path at the top takes you back up.
- Click Restore next to the file or folder to put back.
The restoration runs in the background, and the page shows the result. Whatever is in the account now under the same name is overwritten. Everything else stays as it is.
Good to know:
- Only the account's home folder can be browsed here. To bring back databases or mail settings, restore the whole account under Restore Backups.
- Only the first 1000 entries of a folder are shown.
- Only backups on this server are listed. A backup that is only on the remote destination must first be restored with Restore Backups.
- Clients can restore files from their own backups in the client area.
Server Migration: Connecting#
In the admin area, open Migration and Restore → Server Migration (Server Migration). It copies accounts from another server running cPanel & WHM or intoPanel to this one, over SSH.
- Enter the Address of the other server and Its SSH port (22 when left empty).
- Under Sign in with, choose Password and enter the other server's Root password, or choose SSH key of this server (see below).
- Under Panel on the other server, leave Find out by itself, or choose cPanel & WHM or intoPanel.
- Keep Compress the data on the way ticked for faster transfers over slow links. Tick Pack at low priority to be gentler on the other server, at the cost of speed.
- Click Connect and Scan.
The other server must allow root to sign in over SSH, and this server must be able to reach its SSH port. Its key is remembered at the first connection.
Signing in with a key: in Sign in with a key instead of the root password, click Make this server's key. Add the line shown to /root/.ssh/authorized_keys on the other server, then choose SSH key of this server when connecting.
Good to know:
- The root password is kept in memory only, until you click Disconnect or the panel restarts. It is never written to disk.
- The private half of the key stays on this server, readable by root only.
Server Migration: Choosing Accounts#
After connecting, Server Migration shows the source and target servers and three tabs: Accounts, Packages and Service Settings.
On the Accounts tab, every account on the other server is listed with its domain, disk usage, owner, package and dedicated IP. Use the search box and page size to find accounts.
- Tick the accounts to transfer, or tick Select all shown.
- Optionally change the Username Here to give an account another name on this server.
- Tick Dedicated IP to give an account an address of its own here.
- Open Default under What to Copy to choose what comes across for that account:
- Home folder (files)
- Databases
- Mailboxes and mail
- Keep its password
- Keep its package
- Scheduled tasks (cron jobs)
- FTP accounts
Apply to other selected accounts copies these choices to the other ticked accounts.
- Choose whether to overwrite accounts that are here already. Exists here marks them.
- Choose how many accounts are moved at the same time, from 1 to 10 (3 accounts at a time unless you change it).
- Click Copy.
Each account is packed on the other server, copied here and restored. A progress card shows the whole transfer, and Transferred accounts shows the result.
Each account being moved gets its own box under the progress card, with its progress and its own log. When an account is finished, its box is cleared and the next account on the list starts in it; a box with no account left folds up. In each box, Pause holds that account at its next step and Resume carries on; Cancel this account stops it, keeps what was restored so far, and the box goes on with the next account. Stop the whole transfer cancels the accounts in progress and leaves the rest out. The full log of every account stays in the progress card and in Migration History, and View log in the results table opens one account's own log.
Moving several accounts at once is faster, but each one is packed on the other server at the same time, so both servers work harder and the other server needs room for several packed accounts. On a busy server, choose fewer.
What comes across: websites and files, addon domains and subdomains, databases with their users and passwords, mailboxes with their passwords and mail, forwarders, and the options chosen above. From another intoPanel server, each website's PHP version and settings and its DNS records come across too. From cPanel, DNS zones are made pointing at this server and the other records of the old zones are added, as in "Restoring cPanel Backups"; SSL certificates are issued again once the domain points here.
Good to know:
- The other server needs free space to pack each account. Nothing is removed there except the packed file.
- Websites answer here once each domain's DNS points at this server. Until then, test a site by adding this server's address for the domain to the hosts file on your own computer.
Server Migration: Packages and Service Settings#
While connected in Server Migration, two more tabs copy things other than accounts.
Packages tab: lists the packages on the other server with their disk space, monthly transfer, additional domains, databases, mailboxes and FTP logins. Here shows whether each one already exists on this server; new ones are ticked in advance.
- Tick the packages to copy.
- Choose Do not overwrite packages that are here or Overwrite packages that are here.
- Click Copy.
An account's package is also copied by itself when the account is transferred with Keep its package ticked.
Service Settings tab: lists the services whose settings can be copied, with the version on each server and the number of settings that can be copied. Tick the services and click Copy. The chosen settings replace this server's settings for that service. Each value is checked first, and values this server does not accept are left out. The message names what was copied and what was not.
Scan the Other Server Again reads the other server's accounts and packages afresh. Disconnect ends the connection and forgets the password.
Good to know:
- To copy this server's settings out to other intoPanel servers instead, use the Settings Sync Group.
Migration History#
In the admin area, open Migration and Restore → Migration History (Migration History). It lists every finished migration, newest first: when it started and finished, the server the accounts came from, how many were transferred and how many failed, and which accounts were in it.
Press Results and log on a migration to see its accounts one by one — the account (with its old name if it arrived under a new one), its main domain, Transferred or Failed with the reason, and what else came along — and below them the whole log of that run.
The migrations stay in the history until you remove them, also when the panel restarts. Remove one with its × button (or Remove on its page), or all of them with Remove all. Removing a migration removes only its results and log, never the accounts it brought over.
The table of the run that just finished is also shown on the Server Migration page, with the client's panel login for each account:
- If Keep its password was ticked and the password came along, the client signs in with the same password as on the other server.
- Otherwise the account has no panel password yet. Set one on its account page.
- If the account belonged to a reseller that exists here with the same name, it joins that reseller.
Migrations made before this history existed are not in it.
Restore an Account from a File#
In the admin area, open Migration and Restore → Restore an Account from a File (Restore an Account from a File). Use the Upload a backup file and Uploaded backup files cards near the end of the page.
- Under Upload a backup file, choose the
.tar.gzor.tarfile and click Upload. intoPanel backups and cpmove-format backups (cpmove-USER.tar.gzorbackup-DATE_USER.tar.gz) can be restored. - In Uploaded backup files, click Look inside. The page shows who made the backup, the account, its main domain, its websites and its databases.
- Under Restore this backup, check Restore into account. You can type another username here.
- If the account does not exist here yet, enter a Panel password for a new account (at least 10 characters).
- Click Restore.
If the account, or its domain under another account, is already on this server, you are asked once more before anything is replaced.
To restore several uploaded files at once, tick them and click Restore the ticked backups. Each is restored into the account it was made from; new accounts are created without a panel password.
Good to know:
- Large files are quicker to copy straight to
/var/backups/intopanel/_restorewith SFTP orscp. They then appear in the list. - Remove deletes an uploaded file.
Turn an Addon Domain into an Account#
In the admin area, open Migration and Restore → Turn an Addon Domain into an Account (Turn an Addon Domain into an Account). The page lists every additional domain of every account, with its folder, subdomains and mailboxes.
- Click Convert next to the domain.
- Enter the Username of the new account (a suggestion is filled in), the Password twice, and optionally a Contact email address and a Package.
- Leave Move the mailboxes with their mail ticked to move them. Mail forwarding moves in any case.
- Tick any databases to copy. A ticked database is copied to the new account under the new account's name, with its database users and their passwords.
- Click Convert.
The website files are copied from the domain's folder to the new account's public_html. The domain, its DNS zone, certificate, website settings and its subdomains move to the new account. The new account belongs to the same owner as the old one. The page shows the progress.
Good to know:
- The website stays online while the files are copied.
- The copies in the old account (website folder, mail folder, databases) are left in place. Delete them once the new account works.
- FTP logins and scheduled tasks are not moved.
- If databases were copied, update the website's configuration file with the new database and user names.
- An account's main domain cannot be converted. To give a whole account another name, rename it on its account page.
Something missing? Ask in the community or open a ticket.