Hostnirvana Support
Control Panel →

Hostnirvana Support Docs

Here you can find all the help documents and tutorials

How to migrate from Hostnirvana to another host?

March 17, 2026 — hnsupport

because Hostnirvana hosting isn’t cPanel-based, migrations are typically done by moving:

  • Website files (via FTP/SFTP)
  • Databases (via export/import)
  • DNS (to point the domain to the new host)
  • Email (only if you use mailboxes on this hosting)

Below is the cleanest “manual migration” approach that works with any new provider.

Step 1: Copy your website files (FTP/SFTP)

Use these FTP details for your hostnirvana.com hosting package:

  • FTP server (host): “”
  • FTP username: “”
  • FTP password: ""

You (or the new host) should download everything from your web root and upload it to the new server in the equivalent web root there (often public_html, htdocs, or similar).

Step 2: Export your databases from Hostnirvana

Export each database to a .sql file (most commonly via phpMyAdmin export), then you’ll import those .sql files into databases on the new host.

Important: for security, database passwords cannot be “read back” from our side. If you don’t know the DB password already, you’ll need to set/reset it in your Hostnirvana control panel and then update your site’s config file accordingly (for WordPress this is wp-config.php).

Step 3: Import on the new host + update config

After the new host imports the database(s) and uploads your files, you (or they) must update your site configuration to match the new database credentials:

  • Database name
  • Database username
  • Database password
  • Database host (often localhost on many hosts, but not always)

For WordPress this is inside wp-config.php.

Step 4: Point DNS to the new host

Once the site loads correctly on the new server (ideally tested via a temporary URL or hosts-file preview), update your DNS:

  • Change the website A record(s) (or nameservers) to the new host’s values.
  • If you use email, be careful not to break MX records (mail routing) during the DNS change.