How to Back Up and Move a Joomla Website

Backing up your Joomla site is the one habit that turns a disaster into a minor inconvenience. A hacked site, a failed update, a hosting account that vanishes overnight, a migration to a new server — every one of these is survivable if you have a recent, complete, downloadable backup. Without one, you are rebuilding from memory.

This guide covers what a real Joomla backup actually contains, the fastest way to make one, how to automate it, and how to restore or move your site to a new server — for current Joomla (4, 5 and 6).

What a complete Joomla backup actually includes

A Joomla site is two things, and a backup is only useful if it captures both:

• The files — your Joomla core, template, extensions, images, and configuration.
• The database — every article, user, menu, setting, and extension record.

Copying just the files, or just exporting the database, gives you a broken half. A restorable backup is a single package that contains both, plus the small script needed to put them back. That is exactly what the tools below produce.

The easiest way: Akeeba Backup

For most Joomla site owners, Akeeba Backup is the answer. It is the long-standing standard for Joomla backups, the free Core edition is enough for the vast majority of sites, and the current version supports Joomla 4, 5 and 6. It packages your files and database into a single archive and includes the restore script inside it.

Run your first backup

1. Install Akeeba Backup from the Joomla Extensions Directory (or Akeeba's site), then open it from Components → Akeeba Backup.
2. Run the Configuration Wizard once — it benchmarks your server and sets safe defaults automatically.
3. Click Backup Now. Akeeba builds a single archive (a .jpa file) containing your whole site.

Get the backup OFF your server (this is the part people skip)

A backup that lives only on the same server as your site is not a backup — if the account is hacked or deleted, it goes with everything else. After each backup, download the archive to your own computer (or push it to remote storage like Dropbox, Google Drive, or S3, which the Pro edition automates). Keep it somewhere that is not your web host.

Automate it

Manual backups get forgotten. Schedule them so they happen whether you remember or not: enable Akeeba's system plugin for lazy scheduling, or trigger a backup from your host's cron. Set it to run on a cadence that matches how often your content changes, and always take a fresh one before any core or extension update.

Backing up from your hosting control panel

Most hosts (cPanel, Plesk, DirectAdmin) offer a full-account backup. It is quick and captures everything, and it is a good second layer — but treat it as complementary, not primary: it is tied to that host's format and often stored on the same infrastructure. Download the generated archive off the server, the same as above. If you are moving hosts, a control-panel backup is rarely the cleanest way to migrate a Joomla site — the Akeeba method below is. Planning a host move? Here's what to check before you switch web hosting companies.

The manual method (when you can't install an extension)

If you have no backend access to add extensions, you can back up by hand:

• Files: connect over SFTP and download your entire Joomla directory.
• Database: in phpMyAdmin, select your database and Export it to a .sql file (or run mysqldump from the command line if you have shell access).

Keep the files and the .sql dump together — you need both to restore. This works, but it is slower and easier to get wrong than a packaged backup, so reserve it for when the tools above aren't an option.

How to restore or move your Joomla site to a new server

The same Akeeba archive that backs up your site is also how you move it. The restore tool is Akeeba Kickstart, a tiny free script:

1. Upload your backup archive (.jpa) and kickstart.php to the destination server (a new host, or a local/staging environment).
2. Create an empty database on the destination and note its name, user, and password.
3. Open kickstart.php in your browser. It unpacks the archive and launches the Akeeba Backup Installer (ANGIE).
4. ANGIE walks you through pointing the site at the new database and updating the site URL — then your site is live on the new server, an exact copy of the original.

This is the reliable way to migrate a Joomla site to a new server, clone production to a staging site, or move a local build up to live, with no manual database surgery.

Backup best practices

• Follow 3-2-1: at least 3 copies, on 2 different media, with 1 off-site.
• Back up before every update — core, template, or extension. (If a core update ever fails, here's how to fix the "Database Structure Update Failed" error.)
• Automate so it happens without you.
• Test a restore occasionally on a staging site. A backup you have never restored is a backup you don't actually know works.
• Keep archives off your web host — the whole point is surviving the loss of that server.

Get this one habit right and almost every Joomla emergency — a bad update, a compromise, a host failure — becomes a 20-minute restore instead of a rebuild.