How to Transfer a Website
How to Transfer/Copy a Website to a Subdomain
If you already have a live website on your main domain, you can transfer or copy it to a subdomain. However, if you plan to make changes to the subdomain, you may encounter difficulties transferring the database back to the main domain later.
This is because the main site will continue to operate, accumulating up-to-date data such as new user registrations and requests, while the subdomain may have different settings. In such cases, data synchronization will no longer be possible.
The Premium Exchanger script license includes the option to create a test version of your website on a subdomain, which can later be transferred to the main domain.
To do this, specify your subdomain on the Your Licenses page:

You can create a subdomain using the ISP Manager server control panel by following this guide.
Install the script on the subdomain by following this guide.
Please note that license files are updated with the subdomain information after you specify the subdomain on the Your Licenses page. Once the subdomain is specified, it is mandatory to update the license files on the server and upload them to the root folder of the subdomain.
After setting up the website on the subdomain and testing its functionality, you will need to transfer it to the main domain. To do this, use ISP Manager to move all files to the main domain folder and update the site name in the copied database (in the _options
table, specifically the siteurl
and home
fields).

If you plan to transfer all requests and settings from the subdomain to the main domain with full replacement, there should be no issues.
However, if you want to transfer only the settings from the subdomain to the main domain (while the main domain already has a live site), synchronization between the two sites will not be possible. This is because two separate databases will be used, which cannot be linked.
How to Transfer a Website to Another Server
Preparation for Transfer
What You’ll Need:
Access to the old server (hosting)
Access to the new server (hosting)
An FTP client or file manager
A program for working with archives (e.g., WinRAR, 7-Zip)
Access to the database (phpMyAdmin or equivalent)
Step 1: Create a Backup of Your Files
Using the Hosting File Manager:
Log in to the control panel of your old hosting provider.
Open the file manager.
Navigate to the root folder of your website (usually
public_html
orwww
).Select all WordPress files and folders.
Click "Archive" or "Create Archive."
Choose the archive format (ZIP is recommended).
Wait for the archive to be created.
Download the archive to your computer.
Using an FTP Client:
Connect to the server using an FTP client (e.g., FileZilla, WinSCP).
Download all files from the root folder of your website.
Create an archive of the files on your computer.
Important: Ensure that all files, including hidden ones (e.g., .htaccess
), are downloaded.
Step 2: Create a Backup of Your Database
Log in to your hosting control panel.
Find the "Databases" or "phpMyAdmin" section.
Open phpMyAdmin.
Select your website’s database from the list on the left.
Go to the "Export" tab.
Choose export options:
Export Method: Quick (or Custom for large databases)
Format: SQL
Options: Include CREATE DATABASE
Click "Go" or "Export."
Download the resulting SQL file to your computer.
Step 3: Upload Files to the New Server
Preparing the New Hosting:
Ensure that the new hosting supports PHP and MySQL.
Create a new database (if it wasn’t created automatically).
Note down the database connection details:
Database name
Database user name
Database user password
Database host (usually
localhost
)
Uploading Files:
Log in to the file manager of the new hosting provider.
Navigate to the root folder of your website (
public_html
orwww
).Remove any default hosting files (if present).
Upload the WordPress archive.
Extract the archive into the root folder.
Verify that all files have been extracted correctly.
Step 4: Restore the Database
Open phpMyAdmin on the new hosting.
Select the newly created database.
Go to the "Import" tab.
Click "Choose File" and select the downloaded SQL file.
Ensure the correct format (SQL) is selected.
Click "Go" or "Import."
Wait for the import process to complete.
Step 5: Configure Database Connection
Locate the
wp-config.php
file in the root folder of your website.Open it for editing using the file manager or download it to your computer.
Update the following lines with the new database details:
// Database name
define('DB_NAME', 'new_database_name');
// Database user
define('DB_USER', 'new_database_user');
// Database password
define('DB_PASSWORD', 'new_password');
// Database host
define('DB_HOST', 'localhost'); // or another host provided by your hosting provider
Save the changes.
If edited locally, upload the file back to the server.
Step 6: Test Your Website
Open your website in a browser using the new address.
Check the main pages.
Log in to the WordPress admin panel (
/wp-admin/
).Test all functionality.
Common Issues and Solutions:
Database Connection Error:
Verify the database details in
wp-config.php
.Ensure the database was fully imported.
Incorrect Links:
Update the site URL in WordPress settings.
Image Issues:
Check file permissions for the
wp-content/uploads
folder.Ensure all files were uploaded.
Alternative Options
Fresh Installation (if data is not critical):
Download the latest version of WordPress from the official website.
Install WordPress on the new hosting.
Reconfigure the site from scratch.
Export only the content from the old site if needed.
Hosting Provider Services:
Many hosting providers offer free or paid website migration services:
Contact the support team of your new hosting provider.
Provide access details for the old hosting.
Wait for the migration to be completed by their specialists.
Security Recommendations
Change all passwords after the migration.
Update WordPress and all plugins to the latest versions.
Review security settings.
Create new backups on the new hosting.
Once the migration is complete and all functionality is verified, you can safely delete files from the old hosting.
Last updated