A database may contain customer information and application settings. Make changes only when you understand the application’s requirements.

What to do

  1. Identify the database and user assigned to the correct application. Use cPanel’s database tools and phpMyAdmin where available.
  2. Export a current backup before changing a schema, importing data or editing application records.
  3. Keep database credentials in the application’s protected server configuration, never in public JavaScript or downloadable exports.
  4. Ask JIJ to review a proposed import or database repair if it could overwrite a live site.

Good to know

Importing a development database over production can erase newer orders or account changes. Never send a database password in a public form.

Related help

Reviewed October 18, 2026. Need help? Contact JIJ support.

Was this answer helpful? 0 Users Found This Useful (0 Votes)

Most Popular Articles

Find the right document root before uploading files

The document root is the directory that serves a particular website. Not every domain in an...
Upload a static website using cPanel File Manager

For a static site, publish the generated HTML, CSS, JavaScript and public assets into the...
Build a backup plan you can actually restore

A useful backup covers the data you need and has a tested restore method. For a database-driven...
Request a website or database restore

A restore replaces data with an earlier copy. For a store or active mailbox, that may remove...
Prepare for a website migration to JIJ

A good migration preserves the website, email routing and business activity while the destination...

Powered by WHMCompleteSolution