All-in-One WP Migration — larger uploads on Bitnami

Intermediate
⏱️ 8 min read
📚 Updated: Aug 2025
WordPress / PHP / EC2
Increasing upload limit for All-in-One WP Migration on WordPress

What you’ll learn

The All-in-One WP Migration plugin (ServMask) exports and imports whole WordPress sites. Large imports hit PHP upload limits and sometimes a plugin-side cap.

This guide targets a Bitnami WordPress on EC2 layout (see WordPress on AWS (Bitnami)): install the plugin, verify the AI1WM_MAX_FILE_SIZE constant if needed, raise upload_max_filesize and post_max_size in php.ini, restart the stack, and confirm the new ceiling in wp-admin.

What is All-in-One WP Migration?

It is a popular WordPress plugin for packaging themes, plugins, uploads, and the database into a single archive for migration or backup. Imports can flow from the filesystem, cloud storage, or other extensions depending on what you install.

Install All-in-One WP Migration

  1. Sign in to wp-admin.
  2. Open Plugins → Add New.
  3. Search for All-in-One WP Migration (vendor ServMask).
  4. Choose Install Now, then Activate.

You should now see All-in-One WP Migration in the admin menu.

Increase maximum upload size

The effective import limit is the minimum of PHP settings, reverse-proxy body limits, and any cap from the plugin or its add-ons. The UI may show a default such as 80 MB; your server can differ. The steps below raise PHP to 300 MB as an example—set values that match your archive size plus headroom.

  1. In wp-admin, open All-in-One WP Migration → Import and note the advertised maximum upload size.

    All-in-One WP Migration Import screen showing upload size limit
    WordPress

  2. Optional: confirm the plugin constant AI1WM_MAX_FILE_SIZE is not stuck at a low value. On current releases the definition may live under the plugin’s constants.php (or equivalent)—paths change between versions, so compare with the vendor documentation before editing anything inside wp-content/plugins/.

    WordPress plugin file editor context for migration plugin
    WordPress

  3. Connect to the instance with FileZilla (or SSH) and open Bitnami’s PHP configuration, commonly:

    Path (Bitnami)
    /opt/bitnami/php/etc/php.ini

    If your stack is not Bitnami, locate php.ini with php --ini over SSH or your AMI docs.

    Locating php.ini for Bitnami PHP on the server
    SFTP / FileZilla

  4. Edit upload_max_filesize and post_max_size (for example set both to 300M). Keep post_max_size at least as large as upload_max_filesize. Save and upload the file back to the server.

    php.ini (example)
    upload_max_filesize = 300M
post_max_size = 300M
    php.ini with increased upload_max_filesize and post_max_size
    Editor

  5. Restart Bitnami services so PHP picks up changes. Over SSH as a user with sudo:

    Terminal (EC2)
    sudo /opt/bitnami/ctlscript.sh restart
    Terminal restarting Bitnami stack with ctlscript.sh
    Ubuntu

  6. Reload All-in-One WP Migration → Import and confirm the displayed limit reflects your new PHP settings (and any premium extension caps).

    All-in-One WP Migration showing increased maximum upload file size
    WordPress

Key takeaways

1

Imports are capped by PHP, the web server, proxies, and the plugin—raise the bottleneck layer.

2

On Bitnami, /opt/bitnami/php/etc/php.ini is the usual place to set upload_max_filesize and post_max_size.

3

Restart services after php.ini edits; avoid long-lived hacks inside plugin files that updates will erase.

Frequently asked questions

PHP rejects oversized POST bodies when post_max_size is too small, even if upload_max_filesize is large. Set post_max_size to at least your largest expected upload (often match both directives for simplicity).
The free tier of the plugin may still advertise a ceiling. ServMask sells extensions that raise or remove that cap while keeping support. Check the current product page for limits that are enforced in software rather than only by PHP.
Locate the active php.ini or drop-in overrides for your AMI (Apache, Nginx, or php-fpm pools). Restart the correct service (for example systemctl restart php8.2-fpm) so changes apply.

Next: S3 from your laptop

Use the AWS CLI to sync large media or exports to and from buckets once PHP limits are sorted.

Download files from S3 →
Did you know?

Edits inside the plugin’s PHP source are overwritten on every plugin update. For a durable cap, use the vendor’s premium extensions, filters documented by ServMask, or manage limits in php.ini / web server config that you control outside the plugin tree.

About the author

Mari Selvan M P
Mari Selvan M P 🔗

Developer, cloud engineer, and technical writer

  • Experience 12 years building web and cloud systems
  • Focus Full Stack Development, AWS, and Developer Education

I write practical tutorials so students and working developers can learn by doing—from databases and APIs to deployment on AWS.

AWS Certified Developer – Associate (Credly)

8 people found this page helpful

WordPress on AWS (Bitnami) Download files from S3