Direct site migration

Move a WordPress site directly between servers.

Use the Direct Site-to-Site Migration workflow to transfer a completed backup from a source WordPress installation to a destination. A temporary migration key authorizes a resumable HTTPS transfer.

HTTPS-only transferExpiring migration keySource → destination
Migration process

No manual browser download and re-upload required.

The supported Direct Migration flow sends backup packages between WordPress sites after administrator authorization.

Source site preparation

Create or select a completed .uwh backup on the source installation.

Short-lived authorization

Generate a temporary key for the selected source backup; the source stores its hash rather than the plaintext key.

Secure destination setup

Enter the HTTPS source URL and migration key in the destination plugin interface.

Transfer in chunks

The destination requests package metadata and content in resumable steps, subject to server/network capacity.

Compatibility checks

WordPress/plugin version, space and transfer conditions are checked before the destination begins restore work.

Protected destination restore

A safety checkpoint is prepared before destructive restore phases where supported.

Step by step

Complete a direct WordPress migration.

Use staging sites if this is your first migration and keep independent backups of both installations.

01

Prepare both sites

Install compatible plugin versions, use HTTPS and ensure matching WordPress versions.

02

Share source backup

Create a completed backup and temporary migration key on the source.

03

Connect destination

Open Direct Migration and provide the source site HTTPS URL plus key.

04

Transfer & verify

Start the authorized pull, complete restore and check login, URLs, forms and media.

Security and compatibility

Controls designed around a sensitive site transfer.

A full backup can include private site files and database records. Protect your migration key like a credential and ensure you own or administer both sites.

  • The source only exposes the selected backup during an authorized active session.
  • The destination uses encrypted storage for transfer authorization state.
  • Existing migration keys expire; always use HTTPS endpoints.
  • Direct Migration is for standard single-site installations, not WordPress Multisite.

Direct Migration checklist

HTTPS on both sitesRequired
Compatible plugin versionsRequired
WordPress version matchRequired
Adequate destination spaceRequired
Working server connectionsRequired
Common migration questions

Know what to check before you transfer.

These details save time when moving from development to production or between hosts.

Does Direct Migration need Google Drive?

No. Direct Migration connects the selected WordPress source and destination directly. Google Drive is optional and independent.

Can I move to a different domain?

The plugin includes domain-aware restore handling for WordPress site references. Review internal URLs and third-party plugin settings after the move.

Can I migrate a WordPress Multisite network?

No. UWH Site Migrator v2.4.6 is intended for standard single-site WordPress installations.

What can cause migration failure?

A blocked outbound HTTPS connection, insufficient disk space, mismatched WordPress/plugin versions, expired key, PHP limits or host restrictions may prevent a transfer. Use Troubleshooting to investigate.

100% free plugin · v2.4.6

Move WordPress sites with a focused workflow.

Download the free plugin and follow the destination preflight requirements before transferring a production site.

Get UWH Site Migrator ↓