GoAdmio
GoAdmio Documentation

Import SQL File

From the GoAdmio knowledge base.

Import SQL File

This page explains the Import SQL File screen in GoAdmio. It lets you import a .sql dump file and create a new database (and database user) from it — without needing phpMyAdmin, Adminer, or the command line.

Location: Admin Panel → Databases → Import SQL File
Location (User Panel): Databases → Import SQL File


Overview

Moving a site to GoAdmio, restoring a backup, or cloning a database usually means importing a .sql file. The Import SQL File page combines two steps into one:

  1. Creates a new database and database user (with the account's username prefix)
  2. Imports the .sql file into that database
This is more reliable than phpMyAdmin for large files (which can time out), and it avoids the manual steps of creating the database, user, and privileges separately.

> Note: The .sql file must already be on the server, in a location the importing account can read. Upload it first via File Manager, FTP, or GitHub Downloader. See Uploading the SQL File below.


What the Page Shows

| Field | Description |
|---|---|
| SQL File Path | The full path to the .sql file on the server (e.g., /home/bedorandsheroq.net/www/backup.sql) |
| Domain | The hosting account/domain that will own the new database |
| Database Name | The suffix for the new database (prefixed with the account username) |
| Database Username | The suffix for the new database user (prefixed with the account username) |
| Password | The password for the new database user (with a Generate Password button) |
| Import | Run the import |
| Status / Output | Result of the import, including errors and warnings |

> Tip: The Database Name and Database Username fields accept a suffix — GoAdmio adds the domain's username as the prefix automatically, following the same convention as MySQL Databases. For example, wordpress becomes bedorandsheroq_wordpress.


Uploading the SQL File

Before importing, the .sql file must be on the server. Upload it in one of these ways:

| Method | Best for |
|---|---|
| File Manager | Small to medium files (under the PHP upload limit) |
| FTP Accounts | Medium to large files, resumable transfers |
| SCP / SFTP | Large files, scripted uploads |
| GitHub Downloader | .sql files tracked in a Git repository |
| CLI (scp) | The fastest way for very large files |

> Tip: The SQL File Path must be readable by the database import process. The safest location is inside the account's home directory — for example, /home/<username>/www/backup.sql. Do not place it in /tmp unless you understand the server's temp-file permissions.

> Warning: A .sql file often contains sensitive data — user records, hashed passwords, API keys. Delete the file from the server after a successful import, and never place it in a web-accessible directory without protection (see Directory Privacy).


How to Import an SQL File

  1. Upload the .sql file to the server (see above).
  2. Log in to the GoAdmio Admin Panel (or User Panel).
  3. Navigate to Databases → Import SQL File.
  4. Enter the SQL File Path (e.g., /home/bedorandsheroq.net/www/backup.sql).
  5. Select the Domain that will own the new database.
  6. Enter the Database Name suffix (e.g., wordpress).
  7. Enter the Database Username suffix (e.g., wpuser).
  8. Click Generate Password or enter your own.
  9. Click Import.
GoAdmio creates the database and user, then imports the .sql file. The Status / Output column shows progress and any errors.

> Warning: Save the generated password immediately — it is not displayed again after import. Store it in a password manager and in the application's configuration file.


What the Import Creates

| Item | Created? | Notes |
|---|---|---|
| Database | ✅ Yes | With the account's username prefix |
| Database user | ✅ Yes | With the account's username prefix |
| User privileges | ✅ Yes | ALL PRIVILEGES on the new database |
| Tables from the dump | ✅ Yes | Structure and data |
| Indexes, views, triggers | ✅ Yes | As defined in the dump |
| Routines (procedures, functions) | ⚠️ Depends | Some dumps omit routines; verify after import |
| Events | ⚠️ Depends | May need the event scheduler enabled at the destination |
| The original .sql file | ❌ Unchanged | Delete it manually after a successful import |

> Tip: If the dump was created with --routines --triggers --events, all objects are included. If not, recreate any missing routines or events manually after the import.


File Format Requirements

The import tool expects a standard SQL dump — the output of mariadb-dump or mysqldump. Common acceptable formats:

| Format | Supported |
|---|---|
| mariadb-dump plain SQL | ✅ Yes |
| mysqldump plain SQL | ✅ Yes |
| gzipped (.sql.gz) | ⚠️ Depends on version — decompress first if unsure |
| ZIP (.sql.zip) | ❌ No — extract first |
| CSV | ❌ No — use phpMyAdmin's CSV import |
| phpMyAdmin export (SQL) | ✅ Yes |
| cPanel backup (.tar.gz with a .sql) | ❌ No — extract the .sql first, or use Restore Full Backup |

> Note: If the dump contains CREATE DATABASE or USE statements that reference the original database name, the import may fail or create a database with the wrong name. Check the first few lines of the dump:
```bash
head -n 20 /home/<user>/www/backup.sql

↑