🎉 FREE 1 Month on All Shared Hosting Plans — No Money Due Today! No Promo Code Required

How To Back Up A Website Before Making Changes

Cyclone Hosting practical guide to how to back up a website before making changes, including decision points, safety checks, and troubleshooting information.

Cyclone Hosting practical guide: A pre-change backup should capture the exact state you may need to restore, not merely an old scheduled copy.

Backups Turn Risky Changes Into Reversible Changes

Before editing code, updating software, moving domains, or importing data, create a restore point.

Download Website Files

Use cPanel File Manager, FTP, or a backup tool. Include hidden configuration files and confirm the archive is not empty.

Export The Database

Use phpMyAdmin or the application's backup tool. Large databases may require command-line or server-side export methods.

Record The Current Environment

  • PHP version
  • Enabled extensions
  • DNS records
  • Application version
  • Plugin and theme versions
  • Scheduled tasks

Store The Backup Somewhere Else

Download a copy to your computer or off-site storage. A backup kept only inside the hosting account may be affected by the same problem.

Name Backups Clearly

Include the domain, date, and purpose, such as before-plugin-update or before-migration. Clear names prevent confusion during an emergency.

Verify Before Starting

Open the archive, confirm expected folders exist, and check that the database export contains tables and data.

Cyclone Hosting Practical Checklist

  • Back up files and the database immediately before the change.
  • Record PHP, plugin, theme, and DNS settings.
  • Store a copy outside the web root.
  • Verify the archive and SQL export before starting.

When To Contact Support

Contact Cyclone Hosting support when the issue involves the hosting account, server access, DNS hosted with us, email-server settings, SSL issuance, or an error you cannot isolate. Include the domain, the exact error, the page or mailbox affected, when it began, and the troubleshooting already attempted. Never send a password in a normal support message.

What To Record For Future Reference

Keep a short change log containing the date, the setting changed, the reason for the change, and the backup or rollback point. This makes future troubleshooting faster and helps separate a hosting problem from an application change.