All-in-One WP Migration Unlimited Extension 2.84

All-in-One WP Migration Unlimited Extension is the “stop fighting file size limits” add-on for people who actually move WordPress sites, not just talk about it. I use it when a site is 2–30 GB, full of uploads and page builder junk, and I want a single portable archive instead of a manual DB dump + rsync dance.

It’s not a magic wand, though. Unlimited removes the plugin’s internal cap; your server still has opinions (PHP memory, timeouts, disk I/O, reverse proxy limits). That’s where most “it’s stuck at 18%” stories come from.

What it changes under the hood (and where the data lives)

This extension piggybacks on the core All-in-One WP Migration Unlimited Extension workflow: export builds an archive, import unpacks it, then the plugin swaps the database + files and runs search/replace on URLs/paths.

Practical anatomy:

• Backups/archives live in: wp-content/ai1wm-backups/
• The import UI is in WP Admin under All‑in‑One WP Migration.
• During import, it extracts in chunks and writes a lot of temp data; you’ll see disk spikes and tons of small file operations. On slow shared hosting, that’s the real bottleneck, not CPU.

What’s editable: basically nothing in templates; it’s a functional plugin. Settings are minimal; your “tuning knobs” are PHP/server limits and where you place the archive.

Where it usually breaks (real causes + fast fixes)

1) Import “stuck” at some percent (often 10–30–70%).
Mechanics: PHP hits max_execution_time, memory limit, or the server kills long requests (Nginx/Apache/Cloudflare timeouts). Sometimes it’s I/O: extracting millions of files on cheap storage.

Fast fixes I actually do:

• Increase server limits: memory_limit (512M+ on big sites), max_execution_time (300–900), and if possible max_input_time.
• Bypass browser upload entirely: upload the .wpress file via FTP/SFTP directly into wp-content/ai1wm-backups/, then import from the plugin screen. This avoids HTTP 413/timeout drama.
• Temporarily disable WAF/mod_security rules that block large POSTs.

What I check:

• Browser DevTools → Network: look for 413 Request Entity Too Large, 504 Gateway Timeout, or failed admin-ajax.php calls.
• Server error logs for PHP fatal/timeout.

2) “Upload failed” even with Unlimited installed.
Unlimited ≠ your host allowing huge uploads. If upload_max_filesize / post_max_size are small, the browser upload dies before the plugin even starts.

Fast fix:

• Same workaround: SFTP the archive into ai1wm-backups and import from there.
• Or raise upload_max_filesize and post_max_size if you control php.ini.

3) Imported site loads, but media/links are broken (mixed URLs, weird redirects).
Mechanics: the plugin does URL replacement, but edge cases happen with hardcoded builder data, serialized blobs, or aggressive caching.

Fast fix:

• Clear all caches (plugin/server/CDN).
• Re-save permalinks (Settings → Permalinks → Save).
• If a builder still references old URLs, run a targeted search/replace (carefully, with serialization-safe tooling).

License / activation / updates (how it behaves in practice)

This extension is activated and working (I verified it). Functionally: the core plugin runs without it, but imports/exports hit a size limit; Unlimited removes that cap.

Without activation (in general): you typically lose auto-updates and vendor support.
Manual updates:

• Upload ZIP via Plugins → Add New → Upload Plugin, or replace via FTP.
• Don’t patch plugin files; updates overwrite them.

FAQs (only the annoying stuff)