To clone website content in WordPress, you need to copy both the files and the database, then update every old URL safely. This guide shows the quickest Softaculous method, a migration-plugin method and a manual method for a new domain.
What you need before cloning
Prepare these items before you touch the live site:
- Administrator access to the source WordPress dashboard.
- Access to the source hosting panel and a recent backup of the files and database.
- The new domain added to the destination hosting account, with an empty document root.
- A new database name, database user and password for the destination site if you are working manually.
- Enough storage for two copies of the site. Keep the original copy until the new one has passed your checks.
If the new domain is also on HostKarle, DirectAdmin includes Softaculous, a PHP version selector and free SSL for each domain. The HostKarle WordPress hosting plans use the same DirectAdmin plans, so you can add a second site without changing the process.
Clone vs staging vs migration
These terms are related but they describe different jobs.
| Term | What it creates | Best use | What happens to the old site? |
|---|---|---|---|
| Clone | A second copy of files, database and settings | A new domain, a sandbox or a reusable template | It stays unchanged |
| Staging site | A temporary testing copy | Testing updates before applying them to the live site | It remains the public site |
| Migration | A move from one location to another | Changing host or server while keeping one main site | It is usually replaced or redirected |
For example, example.com copied to newexample.in is a clone when both sites should remain available. A copy at stage.example.com for testing a plugin is staging. A move from one host to another with the same domain is migration, not a new public website.
If your only goal is to move an existing site to HostKarle, see the related guide on migrating a WordPress website manually. If you want to create a test copy before changing the live site, read the guide on installing WordPress in DirectAdmin first.
Step 1: Prepare the source and destination
Why this matters: a clone can overwrite the wrong folder or expose a private test site if the destination is not ready.
- Write down the exact source and destination URLs, including
https://and whether each useswww. - Update the source WordPress core, theme and plugins only if you have tested those updates. Do not use the cloning process as a substitute for a backup.
- Make a fresh backup of the source files and database. Download a copy when possible.
- Add the destination domain or subdomain in DirectAdmin and confirm its document root. Do not install a second WordPress copy into the source domain’s existing folder.
- Temporarily keep the destination private. You can use a temporary URL, a password or WordPress’s indexing setting while you test.
Success looks like this: you have a named backup, a blank destination folder and a clear record of which URL belongs to each site.
Step 2: Clone with Softaculous
Why this matters: Softaculous can copy a Softaculous-managed WordPress installation and set up the destination database without making you move each file by hand.
Softaculous’s official Clone documentation says that you choose an installation, select Clone, enter the destination details and start the clone. WordPress Multisite cloning is not supported by that Softaculous procedure, so use the plugin or manual method for a Multisite network.
- Sign in to DirectAdmin and open Softaculous Apps Installer or WordPress Manager.
- Open All Installations and locate the source WordPress site. If it was installed manually and does not appear, import the installation into Softaculous first.
- Click Clone beside the correct source installation.
- Choose the destination domain. Leave the directory empty if you want WordPress at the root of the new domain; enter a folder name if you want
newexample.in/storeinstead. - Enter a new database name if Softaculous asks for one. Keep the source database selected only if you are deliberately working on a disposable test copy.
- Start Clone Installation and wait for the completion message. Large media libraries can take longer than a small blog.
- Open the new domain and sign in with the source site’s existing WordPress administrator credentials. Softaculous notes that the copied login details are the same as the source installation.
Success looks like this: the new URL opens, the WordPress dashboard loads and the source site still opens at its original URL. If you see the old domain in the address bar, continue to Step 5 before changing anything else.
Step 3: Clone with a free migration plugin
Why this matters: a plugin is useful when the source site is not listed in Softaculous or when you want a guided package-and-restore process.
One option listed in the WordPress plugin directory is Duplicator. Its free plugin can package the website files and database so you can install the package at another WordPress location. Menus can change between plugin versions, but the workflow is generally the same:
- In the source dashboard, open Plugins > Add New Plugin, search for Duplicator, install it and activate it.
- Open Duplicator and create a new backup or package. Let the scan finish, then build the package.
- Download the archive and installer files if the plugin provides two files. Keep them together and do not rename them.
- In DirectAdmin, add the new domain and confirm that its document root is empty. Upload the package files into that folder using File Manager or FTP.
- Open the installer URL in your browser, such as
https://newexample.in/installer.php, and enter the new database details when asked. - In the installer’s URL or replacement settings, check that the old domain is being replaced by the new domain. Do not type a partial domain that could alter an unrelated URL.
- Finish the installation, sign in to the new dashboard and remove the installer and archive files when the tool tells you it is safe.
Success looks like this: the package completes without an error, the destination dashboard opens at the new URL and the new site’s media, menus and plugins match the source. Keep the original backup outside the public web folder; an installer file left online can expose your site.
Step 4: Clone manually with files and a database
Why this matters: manual cloning works even when an installer cannot detect the site, but every part must be copied in the right order.
- Copy the files. Download the complete WordPress directory from the source, including
wp-content,wp-config.php,.htaccessand hidden files. Upload the files into the destination document root. - Create the destination database. In DirectAdmin, create a MySQL database and user, then grant the user all required privileges. Save the database name, username, host and password.
- Export the source database. Open phpMyAdmin or the database tool provided by your host, select the WordPress database and export it as an SQL file. Do not export a different site’s database by mistake.
- Import the database. Select the new empty database and import the SQL file. A large export may need the hosting panel’s import tool rather than a browser upload.
- Edit
wp-config.php. UpdateDB_NAME,DB_USER,DB_PASSWORDandDB_HOSTto the destination values. Keep the table prefix exactly as it appears in the imported database. - Open the destination. Visit the new domain. If it redirects to the old domain, that is expected until the URL values are corrected in Step 5.
Success looks like this: WordPress can connect to the destination database, the login page appears and the destination folder contains the same wp-content/uploads media files as the source.
Step 5: Replace old URLs safely
Why this matters: copying files does not change URLs stored in the database, and a plain text replacement can damage serialized theme, widget or plugin settings.
The official WordPress migration guide warns about serialized data and recommends a tool that understands it. Use one of these approaches on the destination copy:
- Softaculous or a migration plugin: use its built-in old-URL and new-URL fields during the clone or restore process.
- WP-CLI: from the destination WordPress folder, run a dry run first:
wp search-replace 'https://oldexample.com' 'https://newexample.in' --skip-columns=guid --dry-run
If the results look correct, run the same command without --dry-run:
wp search-replace 'https://oldexample.com' 'https://newexample.in' --skip-columns=guid
- A search-and-replace plugin: install one from the WordPress dashboard and select the destination database. Use its serialized-data-safe replacement mode, and run a preview before applying changes.
Do not run a blanket SQL REPLACE() across the entire database. Also do not change the guid column just because it contains the old domain; WordPress’s documentation says GUID values should remain unchanged. After replacement, check Settings > General and confirm both WordPress Address (URL) and Site Address (URL) use the destination URL.
Success looks like this: the dashboard stays on the new domain, internal links open on the new domain, and images do not request the old domain.
Step 6: Finish DNS, SSL and indexing checks
Why this matters: a technically correct clone can still look broken if the domain points elsewhere, HTTPS is missing or search engines index a private copy.
- Point the new domain to the destination hosting account using the nameservers or DNS records supplied by your host. Make the change at the domain registrar, not inside WordPress.
- Wait until the domain resolves to the destination, then issue or enable the free Let’s Encrypt SSL certificate in DirectAdmin.
- Open the site using
https://and check the home page, several posts, contact forms, menus, search and media files. - Go to Settings > Permalinks and click Save Changes once. This refreshes WordPress rewrite rules after a move.
- If this is a test or staging clone, go to Settings > Reading and enable Discourage search engines from indexing this site. Keep the test copy private as well; noindex is a safety layer, not access control.
- If the new domain is replacing the old one permanently, remove the test noindex setting and create relevant 301 redirects from old URLs to their matching new URLs. Update your analytics, Search Console property and important external references.
Success looks like this: the site loads securely at the new domain, the key pages return the expected content, and the indexing setting matches the purpose of the clone.
Verify the cloned site
Use this short checklist before allowing visitors or deleting anything:
- Open the home page in a private browser window.
- Log in and log out of
/wp-admin. - Open one post, one page, one category and one media attachment.
- Submit a test form and confirm its email destination.
- Check image URLs, CSS, JavaScript and the browser console for mixed-content warnings.
- Test mobile layout and the main menu.
- Confirm plugins that use domain-based licences or API callbacks are configured for the new domain.
- Check that the old site still works if this is a true clone.
- Keep the source site and backup until you are satisfied with the result.
Common errors and fixes
The new site redirects to the old domain. Check home and siteurl in the destination database’s *_options table, any WP_HOME or WP_SITEURL constants in wp-config.php, and leftover old URLs in the database.
Images or styling are missing. Confirm that wp-content/uploads and the active theme files were copied. Then run a serialized-data-safe URL replacement and clear any WordPress or browser cache.
The site shows “Error establishing a database connection”. Recheck the four database values in wp-config.php, confirm the database user has privileges and verify the database host supplied by your hosting panel.
The home page works but inner pages show 404. Save the permalink settings once, then inspect the destination .htaccess file and confirm the rewrite rules are present.
The clone appears in Google. For a test copy, enable the WordPress noindex setting and use access protection. For a permanent domain change, use the proper 301 redirect and update Search Console rather than leaving two public copies online.
FAQ
Can I clone a WordPress site to a different domain?
Yes. Copy the source files and database, then replace the old site URL with the new one using Softaculous, a migration plugin or a serialized-data-safe tool. Keep the original site and backup until the new domain passes your tests.
What is the easiest way to clone a WordPress site?
Softaculous is usually the quickest option when it detects the source installation and the destination domain is already added to your hosting account. A migration plugin is a useful alternative when the site was installed manually or you need a portable package.
Does cloning WordPress copy the database?
Yes, a complete clone needs the database as well as the files. Posts, pages, settings, users, menus and many plugin settings live in the database, while themes, plugins and uploads live in the files.
Should I change the WordPress URL after cloning?
Yes, if the clone will use a different domain or folder. Update both the WordPress Address and Site Address, then safely replace old links in the database; do not use a raw text replacement that can break serialized settings.
Can I clone a WordPress Multisite network with Softaculous?
Softaculous’s current clone documentation says its WordPress cloning procedure does not support Multisite. Use a Multisite-aware migration method and verify the network’s domain, path, uploads and database tables separately.
DONE how-to-clone-wordpress-site words=2324
Want to partner with us, suggest a resource or advertise on this blog? Email partnerships@hostkarle.in



