Mench Migrate

Yes. There is no archive size limit and no paid step to import or restore. Large sites are exported, uploaded and imported in short resumable steps.

Yes. Mench Migrate imports .wpress archives made by All-in-One WP Migration, as long as they were exported without encryption and compression. Mench Migrate is not made by or affiliated with the makers of All-in-One WP Migration.

Optional paid plugins from menchplugins.com: Cloud Storage (S3-compatible), Schedules and Site-to-Site. You buy one, download its ZIP from your menchplugins.com account and upload it under Plugins → Add New → Upload Plugin. This plugin works fully without them and does not contact menchplugins.com.

They stay. Deleting the plugin removes its settings, scheduled events and any leftover import tables. Turn on Settings → "Delete all backups when the plugin is uninstalled" to remove the backups folder too.

nginx ignores the .htaccess guard. The folder name is random and contains an index.php, and the dashboard warns when files in it can be fetched over the web; add a rule denying that folder to your nginx configuration.

Your own object-cache.php, advanced-cache.php, db.php, db-error.php, maintenance.php and sunrise.php drop-ins stay (they belong to this server, and the compatibility check lists any the backup carried). mu-plugins are merged: the backup's entries replace those of the same name, and this site's others stay.

• Very large files lists need PHP memory: about 250 bytes per file (500,000 files fit in 256 MB). Beyond that, raise memory_limit; the error says so.
• A hand-crafted or damaged .wpress database dump with huge statements can exhaust memory while it is read. The import stops before anything on the site changes.
• On MySQL servers with lower_case_table_names=1 (Windows, some Azure hosts), tables with capital letters in their name (such as wp_wfConfig) cannot be imported; the import stops before the switch.
• When the old table prefix appears inside the new one (wp_ to wp_wp_), prefixed option and user meta keys may be rewritten twice; use clearly different prefixes.
• Files reached through a symlinked folder inside wp-content are backed up, even when the link points outside it.
• Encryption uses Argon2id with 256 MB of memory outside PHP's memory_limit; hosts that cap process memory below that may stop an encrypted export or import.
• If the WordPress salts are stored in the database (no salt constants in wp-config.php), the import replaces them, so you are asked to sign in again to finish the import.