We talking about Cloud
Web Hosting & Cloud Services
Celebrate the power and freedom of Open Source
with Open Source Cloud Servers starting at only £10/mo £5/mo.
Web Hosting & Cloud Services
Celebrate the power and freedom of Open Source
with Open Source Cloud Servers starting at only £10/mo £5/mo.
You can copy a database in phpMyAdmin to create a separate version for testing, development or a website migration. Choose Structure and data to duplicate the tables and their contents, or Structure only to create empty tables.
Before starting, check the destination database carefully. On cPanel hosting, create it through cPanel first so the control panel can track it correctly for account management and backups.
Take a database backup before making changes. Use your hosting backup tools or export the source database as an SQL file.
Keep the backup somewhere secure outside your website’s public directory. Database exports may contain customer information, password hashes and other private data.
If the application is actively saving orders, bookings or messages, plan a quiet period or use an application-supported backup process. A copy made while data changes may not represent one consistent point in time.
For cPanel accounts:
For example:
Source database: account_website
Destination database: account_staging
These names are illustrative.
Do not create the destination database directly in phpMyAdmin on cPanel. cPanel recommends using its database-management tools so the database is mapped to the account correctly.
See cPanel’s database-management documentation.
For Plesk, create the destination through its Databases section, or use its database-copy feature where available. The options depend on your hosting permissions.
Launch phpMyAdmin from your hosting control panel.
Select the source database in the left-hand navigation, then open the Operations tab.
Check the database name before continuing. You need the database-level Operations page, rather than the Operations tab for an individual table.
Find Copy database to and enter the complete destination database name.
Choose the settings appropriate to your task:
| Setting | When to use it |
|---|---|
| Structure and data | Copy table definitions and their existing records |
| Structure only | Create the table layout without copying rows |
| CREATE DATABASE before copying | Leave unchecked when the destination was already created through your hosting panel |
| Add AUTO_INCREMENT value | Preserve the current sequence value where supported |
Keep the destination empty unless you deliberately intend to merge or replace objects.
Do not enable options that drop existing tables or overwrite data without understanding their effect. Labels and available settings vary between phpMyAdmin versions.
Review the source, destination and selected options, then click Go.
Wait for the result before refreshing the page or starting another copy. Repeating the operation can produce conflicts if tables have already been created.
If the interface reports an error, record the message and check the destination before retrying. A failed operation may still have copied some tables.
Refresh the navigation panel and open the destination database.
Check that:
Table counts and displayed sizes are useful checks, but they do not prove that a copy is complete. Some phpMyAdmin statistics may also be cached.
For important tables, compare exact row counts where practical. Remember that counts can change if the source application remains active.
Copying a database does not automatically switch a website to it.
Update the test application’s database configuration with the destination database name, username, password and hostname.
For related guidance, see How to Connect to the MySQL Database.
If you are creating a staging website, also review scheduled jobs, outgoing email, payment integrations and external services. A database copy can retain settings that trigger real actions.
Confirm that the logged-in account can read the source and create the required objects in the destination. Check the database-user assignments through your hosting control panel.
Stop and inspect it. Do not delete tables simply to clear an error. Use a new empty database if you are unsure whether the existing data is needed.
Large databases can exceed browser-based processing limits. Ask your provider about a server-side backup and restore or an appropriate command-line method.
Before retrying, check for a partial copy. The phpMyAdmin troubleshooting documentation covers processing and import limits.
Check the application’s configuration file or environment variables. Confirm that you edited the correct installation and changed the database connection details.
A copy operation is intended to retain the source database. Make sure you selected Copy, not Move, and review any destructive options before proceeding.
The Operations workflow generally works within the connected database server and your available permissions. For a different server, use export and import, a hosting migration tool or a provider-assisted transfer.
Do not assume it does. Database accounts and grants are managed separately from application tables. Create or assign the destination user through your hosting panel.
A copy can help with testing, but it should not replace a separate, recoverable backup. A second database on the same account may be affected by the same account or server problem.
Contact DigitalBerg support with the source and destination database names, approximate database size and any error message.
Do not include database passwords or private customer records.

