Migration
All-in-One WP Migration upload limits: find the layer blocking your import
Separate PHP upload caps, proxy restrictions, and restore failures before changing settings or buying an extension.
The upload limit displayed by All-in-One WP Migration is not necessarily a fixed limit imposed by the free plugin. ServMask’s current guidance says that the import screen reports WordPress’s PHP upload cap. A web server, proxy, or security layer can impose a lower effective limit that the screen does not show.
Start by identifying where the import fails. A file rejected before transfer, an HTTP 413 response, and an import that stalls after reaching 100% are different problems.
Compare the file with the reported PHP settings
Open Tools → Site Health → Info → Server and compare upload_max_filesize and post_max_size with the import screen. ServMask’s upload-limit guide explains that the displayed cap reflects the smaller PHP value, while other infrastructure limits are separate.
Record the archive size, exact error, plugin version, and how far the transfer gets. Check that the downloaded .wpress file completed successfully. Renaming another archive format to .wpress does not convert it.
Follow the symptom to the right layer
| Symptom | What to investigate |
|---|---|
| Import screen says the file is too large | Effective PHP upload and POST limits for this site. |
| HTTP 413 or transfer rejected immediately | Request-body limits at the web server, CDN, or proxy. |
| Timeout or disconnect during transfer | Connection stability, request duration limits, and corresponding server logs. |
| Upload completes but extraction or restore fails | Free working space, memory, permissions, archive integrity, and application errors. |
These are investigation paths, not a diagnosis from the progress bar. If support can correlate the failure timestamp with a server log, that is more useful than repeatedly changing several settings at once.
Change supported settings, then recheck
Use the host’s PHP configuration interface or its documented per-site configuration method. Set an appropriate upload value and a POST limit with room for the full request. Ask support when those settings are locked, and verify the effective values afterward.
Do not assume a value written in a random configuration file is active. Different PHP handlers load different files. In particular, ServMask’s current guide warns that runtime ini_set() calls in wp-config.php cannot change these per-directory upload directives.
Raising memory or execution time blindly can leave the actual body-size limit unchanged. Likewise, increasing PHP’s limit will not change an upstream proxy’s cap. Request a supported transfer path from the host if that layer cannot accommodate the archive.
Consider an extension for the workflow it provides
ServMask documents chunked transfer in its Unlimited Extension for situations where infrastructure limits block a normal upload. Check current compatibility, licensing, and restore options before buying. An extension does not create disk space or repair an incomplete backup.
A different migration method may also be appropriate: the destination host’s transfer service, a supported server-side import, or a manual file-and-database migration by someone familiar with WordPress. Compare the work and risk rather than choosing solely by the largest number on an upload screen.
Protect the destination before importing
The All-in-One WP Migration user guide describes export and import as a site-transfer workflow. Restoring an archive replaces destination content; use a recoverable copy and expect the source site’s user credentials to matter after import.
Disable live payment actions, mail delivery, and scheduled business jobs on an isolated destination. After import, inspect media, links, administrator access, and business functions. Follow the restoration acceptance steps before switching visitors to the recovered site.