Transfer diagnostics and pre-flight checks for WordPress hosts

The frustrating thing about PHP memory limit and Nginx timeout errors in WordPress migrations is that every single one of them is detectable before the import starts. The server's configuration is readable. The file size is known. The math on whether max_execution_time is long enough to complete the upload is straightforward. And yet users are regularly surprised mid-transfer when these mismatches surface as a silent stall at 10% or a hang at 100%.

This gap exists because the migration plugin authors don't control the destination server, so they can't fix what they can't touch — and the host's support team doesn't know the user is about to attempt a migration until the ticket arrives after the failure. Nobody is sitting between those two parties.

What's needed is a preflight checker that a developer runs before initiating a migration: it inspects the destination environment's PHP configuration, Nginx or Apache upload limits, and disk write speeds against the known size and structure of the source site, then outputs a concrete list of what will cause the import to fail and what value each parameter needs to be changed to. Not a generic checklist — a site-specific calculation. 'Your max_execution_time is 30 seconds; this import needs at least 420 seconds. Here is the php.ini line to add.' Right now, users discover these mismatches by failing, waiting, failing again, and eventually posting in forums.

This is a business because every hosting environment is different, WordPress sites keep getting larger, and developers move sites repeatedly across their careers. The knowledge of which parameters matter exists, but it's fragmented across Stack Overflow threads and hosting documentation — and it has to be re-assembled manually for every new destination environment. A tool that codifies that knowledge and applies it to a specific migration attempt saves real diagnostic time on a recurring basis.

What to build

Build a web-based preflight checker where a developer pastes destination server credentials (read-only SSH or a lightweight PHP probe script), inputs the source site's export file size and structure, and receives a server-specific configuration report listing every PHP, Nginx, and disk parameter that will cause the import to fail along with the exact corrected values.

Where to start

Launch as a free web tool with no login required for the basic preflight report, then charge for the saved configuration profiles and automated re-checking feature that agencies need when they're managing multiple destination environments for different clients.

The hard part

Collecting server configuration data requires either SSH credentials (which some users won't share with a third-party tool) or a PHP probe script installed on the destination server — and persuading a non-technical user to install that probe before they understand the value of the preflight check is a cold-start trust problem.

How it makes money

Free for single-use preflight checks; $19/month for agency accounts that store environment profiles, get automated re-checks before each migration, and receive a shareable report link to hand to a client's hosting provider.