How to Migrate WordPress by Installatron Clone or Import

admin

2 months ago

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

Installatron clone or import can move WordPress safely when it matches the source, destination, and risk level. This method is best for same-panel clones, app imports, and managed WordPress moves where Installatron will track backups and updates afterward.

Audience: hosting customers on panels that provide Installatron application 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 app and confirm whether Installatron already tracks it.
Choose a destination domain and path that will not overwrite another site.
Check database and file-size limits.
Plan DNS and SSL after the clone.

Migration steps

Open Installatron from the hosting panel.
Choose the WordPress app under My Applications or use import for an existing install.
Select Clone or Import as appropriate.
Set the destination location and database options.
Run the task and monitor completion.
Validate the target site before redirecting traffic.

Post-migration verification

Confirm the new app path, URL, SSL, login, media, plugins, forms, cron tasks, and backups. Verify Installatron tracks the migrated app afterward.

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 to the wrong path can overwrite another app.
Installer tracking can break if files are moved manually afterward.
Remote backups and app metadata should be checked after migration.

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 Installatron 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.