1. Check the file and destination
Identify the source database, date and SQL format. A WordPress XML export is not an SQL backup. Keep an untouched copy. Imports can replace tables; back up the destination and preferably use a fresh database for migration.
2. Open database management
In DirectAdmin, select the domain and look for Account Manager → MySQL Management or Databases, depending on the theme. Create a database and user if needed, retaining their full names. Open the provided phpMyAdmin link; ask support if unavailable.
3. Select the correct database
In phpMyAdmin, select the target database in the left column. Confirm its name before opening Import. Do not import into a live database selected by default. Check that the user has appropriate privileges.
4. Import the SQL file
Choose the .sql file or a supported compressed format, leave SQL selected and start importing. Wait for the result. If file size exceeds the displayed limit or processing stops, request a suitable method instead of repeatedly importing partial data.
5. Connect and test the application
Check tables and the success message. For WordPress, confirm DB_NAME, DB_USER, DB_PASSWORD and DB_HOST in wp-config.php, plus the table prefix. Test pages, login and main functions. Keep credentials private.
6. Handle migration differences
A changed address may require URL updates that preserve serialised data. Avoid blanket text replacements in SQL. For a shop, coordinate files and database at the same recovery point and protect recent orders before switching.
Related service
Web hostingOfficial documentation
Labels and options vary with versions, plugins and your account. Refer to publisher documentation for your configuration.