Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting · Troubleshooting

How to Fix an All-in-One WP Migration Import Stuck at 100%

Short answer

An All-in-One WP Migration import stuck at 100% usually means your browser finished sending the .wpress file, but the server stopped the restore. Wait a few minutes, then open your site in a new tab to check whether the content arrived. If it did not, raise max_execution_time and memory_limit, check disk space, and retry the import.

Key takeaways

  • The 100% bar shows upload progress in your browser, not the restore running on the server.
  • Check your live site in a new tab first, because the import may have finished without a final response.
  • ServMask lists max_execution_time of 600 seconds and memory_limit of 512M for stuck imports.
  • The free plugin has no fixed import cap; the limit you see comes from your host PHP settings.
  • Cloudflare Free and Pro plans cap uploads at 100 MB, even when PHP allows more.
  • Restoring from the Backups screen is a paid feature, so the free path is the browser import.

What does an import stuck at 100% mean?

An import stuck at 100% means your browser finished sending the file, but the server has not finished the restore.

The progress bar tracks the upload from your computer to the server. It does not track the restore steps that run after the upload, such as unpacking files and restoring the database. ServMask explains in its migration troubleshooting guide that the bar is browser-side and does not always reflect the server.

That gap explains why the screen can sit still for minutes. Check which case you are in before you change anything.

All-in-One WP Migration is used by over 60 million websites worldwide as of November 2026, according to its WordPress.org plugin page. It processes files in 512KB chunks, but a large site can still hit a server limit during the restore.

How do you tell if the import already finished?

Open your site in a new browser tab and look for the migrated content.

Do not close the stuck tab yet. Open a second tab, visit your home page, and open 2 or 3 pages that only exist on the source site. If the new content is there, the import likely finished and only the final response failed.

Also log in to wp-admin in that new tab and check Posts, Pages, and Media against the source site. If the content is present, the restore worked even though the progress screen never moved on.

If the site still shows the old content or a login that does not work, the import did not finish. Note what you see, then move to the PHP checks below instead of importing again at once.

Why does the import stop at 100%?

The most likely cause is a PHP time or memory limit that stops the restore after the upload ends.

ServMask says large migration files can exceed the server PHP execution time or memory limits, causing the import to be killed by the server before it finishes. That is the first cause to check.

Other causes follow in order of likelihood:

  • The .wpress file is larger than post_max_size, so PHP drops the request after the browser sends it.
  • The server disk is full, so the plugin cannot unpack the archive or write the database.
  • A firewall or CDN layer in front of PHP rejects the large request, even when PHP allows it.
  • A security or cache plugin on the destination site blocks the restore step.
  • The .wpress file is damaged, so the plugin stops during the restore.

Work through the causes in that order. Fixing the PHP limits first solves most stuck-at-100% cases.

What PHP limits should you raise first?

Raise max_execution_time, max_input_time, and memory_limit first, then check the two upload size values.

ServMask lists these values for a stuck import in its migration troubleshooting guide: upload_max_filesize 512M, post_max_size 512M, max_execution_time 600, max_input_time 600, and memory_limit 512M. Those values are a starting point for a large site.

SettingWhat it controlsServMask value for stuck imports
upload_max_filesizeLargest single uploaded file512M
post_max_sizeLargest whole POST request, file included512M
max_execution_timeSeconds a PHP script may run600
max_input_timeSeconds PHP may spend reading input data600
memory_limitMemory one PHP request may use512M

The PHP manual states that post_max_size must be larger than upload_max_filesize, and that memory_limit should generally be larger than post_max_size, as shown in the PHP runtime configuration reference.

PHP ships with defaults of 2M for upload_max_filesize and 8M for post_max_size, so a host that never raised them will block most real site backups.

For large multisite migrations, WordPress.org notes a recommendation of at least 512 MB of PHP memory on the All-in-One WP Migration plugin page. That is a useful number to give your host.

How do you check your current PHP limits?

Open Tools, then Site Health, then Info, then Server in your WordPress admin.

That screen lists the PHP values your site is really using. ServMask explains in its upload limit guide that the Import screen shows the smaller of upload_max_filesize and post_max_size, so compare that number with the two Site Health values to find the bottleneck.

The Site Health screen is built into WordPress, and the Site Health API handbook describes its Status and Info tabs. Use the Info tab here, because it lists facts about your server.

Write down the 5 values from the table above before you change anything. If post_max_size is smaller than your .wpress file, that is your cause.

If max_execution_time is 30 seconds, that is also a likely cause for a large restore. For help on the PHP side, see our guide on how to update PHP for WordPress.

How do you raise the PHP limits on your host?

Change the values in your host control panel first, and use .user.ini or php.ini only if your host tells you to.

Many hosts let you change PHP settings without editing files. In cPanel, open Software, then Select PHP Version, then Options.

In SiteGround, open Site Tools, then Devs, then PHP Manager. In Hostinger, open Advanced, then PHP Configuration. Those paths come from ServMask, and labels can differ by host as of November 2026.

If your host uses .user.ini, create or edit that file in your WordPress root folder and add these lines:

upload_max_filesize = 512M
post_max_size = 512M
memory_limit = 256M
max_execution_time = 300
max_input_time = 300

If your server runs Apache and reads .htaccess for PHP values, add the same values with php_value in front of each line instead. ServMask lists both forms, with 256M for memory and 300 seconds for the two time values.

Do not try to raise upload_max_filesize or post_max_size with @ini_set() in wp-config.php. ServMask states those two settings are PHP_INI_PERDIR, so PHP will not change them at runtime.

After any change, reload the Site Health Server screen and the Import screen. If the numbers did not move, you edited the wrong file, the host overrode your change, or PHP needs a restart. Ask your host which file it reads before you edit a second file.

What if the file is larger than the server or CDN cap?

Check the layers in front of PHP, because they can block an upload that PHP would allow.

The plugin does not set the upload limit. ServMask states the limit you see is your host PHP cap, and layers in front of PHP can block large uploads on top of that. The free plugin has no fixed import cap, and the older AI1WM_MAX_FILE_SIZE constant was removed years ago.

Cloudflare is the most common outer layer. Its default cache behavior docs list a max upload size of 100 MB on Free and Pro plans, 200 MB on Business, and up to 5 GB on Enterprise as of November 2026.

A .wpress file over 100 MB can fail on a Cloudflare Free site even when Site Health shows 512M.

Nginx adds another layer. Its core module docs describe client_max_body_size, which defaults to 1 MB. A host that never raised it will reject large uploads before PHP sees them, usually with a 413 error.

If an outer layer is the blocker, ask your host whether it can raise it. Do not keep retrying the same browser upload, because the same layer will block it each time. Our guide to the All-in-One WP Migration import limit explains the PHP side of this limit.

How do you retry the import safely?

Make a fresh backup of the destination site first, then retry once with the raised limits.

A failed import can leave part of the site restored and part still old, so do not retry on a live site without a way back. Use a backup of the destination site, and keep the original .wpress file safe. For the backup step, see how to back up WordPress.

Then follow these steps in order:

  1. Clear the destination site cache and turn off any cache or security plugin that could block the restore.
  2. Confirm the new PHP values in Tools, then Site Health, then Info, then Server.
  3. Check that the server has free disk space at least 2 times the size of the .wpress file.
  4. Go to All-in-One WP Migration, then Import, and upload the same .wpress file again.
  5. Leave the tab open and wait. A large restore can take several minutes after the bar reaches 100%.

If the bar sticks at 100% again, wait a few minutes, then check the site in a new tab. If the content is still missing, read the plugin error log and the WordPress debug log before a third try.

For the full migration flow, see how to migrate with All-in-One WP Migration.

What should you do if the browser import keeps failing?

Use the WP-CLI restore route if you have the Unlimited Extension, or split the job into a smaller file.

ServMask says the WP-CLI import bypasses browser and web server timeout limits, with the command wp ai1wm restore backup.wpress. WordPress.org adds that WP-CLI commands are part of the Unlimited Extension, and running them without it only prints a notice.

If you do not have the extension, shrink the .wpress file instead. Export again from the source site and exclude large media folders or old backups that you can move by FTP later. A smaller file is more likely to pass the PHP, post size, and CDN limits in one request.

Uploading the .wpress file by FTP to wp-content/ai1wm-backups and restoring it from the Backups screen is not a free fix. ServMask states that restoring from the Backups screen is a paid feature.

The free import path is the browser upload on the Import screen. The Unlimited Extension costs $69 per year for 50 sites as of November 2026, according to ServMask, and it uses chunked transfer.

A 504 error during the retry points to a server timeout rather than a plugin fault. See our guide on how to fix the 504 gateway timeout error if that error appears.

How do you know the import worked?

Check the home page, the admin counts, and the permalink settings before you call the move done.

Open the home page and 3 or 4 inner pages in a new tab. Check that images load and menus point to the new domain.

Then log in to wp-admin and compare the Posts, Pages, Media, and Users counts with the source site. A missing batch of media means the restore stopped early.

Next, go to Settings, then Permalinks, and click Save Changes without changing anything. WordPress.org notes that after restoring a backup you should clear all caches and re-save permalink settings. That step rebuilds the rewrite rules.

Also check the site in an incognito window, so a cached copy does not hide a broken page. If the front end, the admin, and the permalinks all look right, the import worked.

When should you contact your host or ServMask support?

Contact your host when the PHP values will not change, the disk is full, or an outer layer blocks the upload.

Your host can raise upload_max_filesize, post_max_size, max_execution_time, and memory_limit when the control panel or .user.ini will not move them. Give the host the 5 Site Health values, the size of your .wpress file, and the exact point where the import stops.

Ask the host these 3 questions:

  • Which PHP file does this site read, and are my new values active?
  • Is Nginx client_max_body_size, mod_security, or a firewall rule blocking large uploads?
  • How much free disk space does this account have right now?

Contact ServMask support when the import still fails after the host confirms the limits, disk space, and outer layers are clear. Include the plugin version, the WordPress version, and the .wpress file size.

Also include any error from the plugin log. ServMask releases updates every 2 weeks or at least once a month as of November 2026, according to WordPress.org.

What mistakes should you avoid?

Do not close the tab, edit plugin files, or retry the same upload without changing a limit.

Closing the tab during the restore can leave the site half restored, with new files and an old database. Editing the plugin constants.php file to raise a limit will not help, because ServMask says the old size constant was removed years ago.

Avoid these 5 mistakes:

  • Retrying the same large file with the same PHP limits and expecting a different result.
  • Raising only upload_max_filesize while post_max_size stays smaller than the file.
  • Using @ini_set() in wp-config.php to raise the two upload size settings.
  • Restoring on a live site with no backup of the destination site first.
  • Importing a .wpress file from an untrusted source without checking that it is your own backup.

Each mistake wastes a retry and can leave the site worse off. Fix one limit at a time, check Site Health after each change, and keep the original .wpress file until the new site is fully checked.

Frequently asked questions

How long should I wait when the import is stuck at 100%?

Wait a few minutes, because the restore can keep running on the server after the browser bar fills. Then open your site in a new tab and check whether the new content is there. If nothing changed after several minutes and the tab still shows the same bar, the restore has likely stopped and you should check the PHP limits and disk space before you retry.

Is it safe to close the tab while the import is stuck at 100%?

No, do not close it until you know whether the restore finished. Closing the tab can leave the site half restored, with new files and an old database. Open the site in a new tab first and check the content. If the import did not finish, keep the tab open while you check the logs, then close it only when you are ready to retry with fixed limits.

Does the free version of All-in-One WP Migration limit imports to 512 MB?

No, the free plugin has no fixed import cap. The limit you see comes from your host PHP settings, mainly upload_max_filesize and post_max_size. ServMask states the older size constant was removed years ago. If your file is larger than the PHP limit, raise those settings or ask your host to raise them, because editing the plugin will not change the limit.

Why does my import fail even though Site Health shows 512M?

Site Health only shows PHP values, not the layers in front of PHP. Nginx, a firewall, or Cloudflare can reject the upload before PHP sees it. Cloudflare Free and Pro plans cap uploads at 100 MB, for example. Ask your host whether any of those layers blocks large uploads, and check whether the file is larger than the smallest cap in the chain.

Can I restore a .wpress file from the Backups screen for free?

No, restoring from the Backups screen is a paid feature in the Unlimited Extension. The free import path is the browser upload on the Import screen. Uploading the file by FTP to the backups folder does not give you a free restore. If the browser upload keeps failing, raise the PHP limits or use the paid extension route.

What should I do after a successful import?

Clear all caches, then go to Settings and Permalinks and click Save Changes without changing anything. That rebuilds the rewrite rules. Then check the home page, several inner pages, the media library, and the user list in a new tab and in an incognito window. If the counts match the source site and the pages load, the move is done.

Sources

  1. 15 Common WordPress Migration Errors and How to Fix Them ServMask
  2. Why All-in-One WP Migration Shows an Upload Limit ServMask
  3. All-in-One WP Migration and Backup WordPress.org
  4. Default Cache Behavior Cloudflare Docs
  5. PHP Runtime Configuration PHP Manual
  6. Site Health Developer WordPress
  7. NGINX Core Module NGINX Docs

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test