How to Migrate WordPress by Softaculous Clone or Import

admin

5 hours ago

How to Migrate WordPress by Softaculous Clone or Import migration tutorial showing backup, transfer, verification, and DNS cutover checks

Softaculous clone or import can move WordPress safely when it matches the source, destination, and risk level. This method is best for same-account clones, new-domain moves, and importing an existing WordPress install into Softaculous management.

Audience: shared-hosting users and hosts that provide Softaculous WordPress management. Before using this path, decide whether the move changes hosts, domains, DNS, email, PHP versions, database versions, cache layers, or business data. Those details matter more than the migration button itself.

Before migration

Back up the source and target locations.
Confirm the destination path is empty or safe to overwrite.
Know whether Softaculous already tracks the source installation.
Lower DNS TTL if the final launch will change DNS.

Migration steps

Open Softaculous from the hosting control panel.
Find the WordPress installation or use import if it is not tracked.
Choose Clone for same-panel moves or Import to bring an existing site under management.
Set the destination protocol, domain, directory, and database options.
Run the task and review completion output.
Test the clone before making it public.

Post-migration verification

Check the destination URL, wp-admin, media, permalinks, cache, SSL, forms, and whether Softaculous now tracks the install correctly for backups and updates.

Also check server logs, PHP errors, WordPress Site Health, cache behavior, CDN routing, redirects, robots/indexing state, cron jobs, and whether a new backup job exists on the destination.

Migration risks

Cloning into a non-empty directory can overwrite files.
Wrong protocol or directory choices can create bad URLs.
Installer-managed backups are not a substitute for an independent pre-migration backup.

Rollback and cutover planning

Keep the old site online until the new site is proven. For stores, memberships, bookings, LMS sites, directories, and lead-generation sites, plan a final data freeze or sync so records do not split between servers. Keep DNS rollback notes, old-host access, and a verified backup until traffic and logs are stable.

Fix I.T. Phill recommendation

Use Softaculous clone or import when it gives you the cleanest preview and rollback path. If the site makes money or stores customer records, treat the final cutover as a maintenance window, not a casual copy job.