Prepare a WordPress Site for Migration

A successful migration starts with the destination server. Siteligent performs automated checks before transferring any files or database data, so problems with PHP, database support, extensions, permissions, or available storage can be identified before the migration begins.

Before You Start

Before beginning a migration, make sure:

You have access to the destination WordPress site.
The destination server meets Siteligent's technical requirements.
There is enough free disk space for the incoming site files.
The destination site's wp-content directory is writable.

The destination Connector version is checked during the connection handshake. If the required version is not installed, Siteligent will warn you before data transfer starts.

Destination Server Requirements

Siteligent's preflight check verifies several server requirements before the migration can proceed.

PHP 7.4 or Higher: The destination server must run PHP 7.4 or higher. This ensures the server can support the libraries and functionality required by the migration process.

MySQL 5.7 or Higher: The destination database must use MySQL 5.7 or higher or a compatible MariaDB version. Siteligent uses database operations that require a modern database environment.

ZipArchive: The PHP ZipArchive extension must be enabled. Siteligent uses PHP's native ZipArchive functionality to extract migration files rather than relying on shell-based extraction methods. If ZipArchive is missing, the preflight check will prevent the migration from starting.

PDO MySQL: The pdo_mysql PHP extension must be available. Siteligent uses it for database importing and streaming database data efficiently during the migration.

OpenSSL AES-256-GCM: The destination server must support OpenSSL encryption using AES-256-GCM. Siteligent uses this encryption when handling migration state information and does not fall back to older CBC encryption methods.

Writable wp-content Directory: Siteligent needs to be able to write to the destination site's: /wp-content/. The preflight check verifies that this directory is writable before the migration begins.

Enough Free Disk Space: The destination server needs enough available storage for the migration archive and the extracted WordPress files. Siteligent checks the available space in the wp-content directory before starting the transfer.

How Siteligent Checks the Destination

You don't need to manually check every requirement before starting.

When you begin a migration, Siteligent contacts the destination site's transfer endpoint:

/siteligent/v1/transfer/preflight

The destination server is checked before Siteligent starts copying data. If a required component is missing or doesn't meet the minimum requirement, the migration can be stopped before the transfer begins.

This helps avoid starting a large migration only to discover later that the destination server cannot extract the files or import the database.

If a Preflight Check Fails

If Siteligent reports a failed requirement, fix the reported issue on the destination server and run the migration again.

For example:

PHP version too old: Upgrade PHP through your hosting provider.
MySQL version too old: Ask your hosting provider to upgrade the database server.
ZipArchive unavailable: Enable the PHP zip extension.
PDO MySQL unavailable: Enable the pdo_mysql extension.
wp-content not writable: Correct the directory permissions or ownership.
Insufficient disk space: Free up storage or increase the destination server's disk capacity.

Don't proceed with a migration while a required preflight check is failing. Resolving these issues first reduces the chance of an interrupted or incomplete transfer.

Ready to Migrate?

Once the destination site passes its preflight checks, Siteligent can begin the migration process. The transfer is handled in background stages rather than attempting to move the entire site in one large request, helping the process stay within normal server execution limits.

If you have questions about preparing your site for migration or run into an issue, our support team is here to help. Create a Support Ticket and share the details of what you're experiencing so we can help you get your migration ready.