Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
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
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Backups & maintenance · Info

How Long Does All In One WP Migration Take? The Short Answer

How Long Does All In One WP Migration Take? The Short Answer

Short answer

Most small WordPress sites export and import with All-in-One WP Migration in under 15 minutes. Sites of several gigabytes can take an hour or more, mainly because of upload speed, server resources and database size. A bar frozen for over 30 minutes usually means the job is stuck.

Key takeaways

  • Small sites usually finish in a few minutes.
  • Upload speed is often the slowest step.
  • Imports take longer than exports because of URL replacement.
  • Exclude media or clean the database to save time.
  • A bar frozen for 30 minutes or more is likely stuck.
  • Very large sites may move faster by SFTP or host tools.

How long does All-in-One WP Migration take?

A small WordPress site usually exports and imports with All-in-One WP Migration in a few minutes, while sites of several gigabytes can take from half an hour to a few hours.

There is no fixed time. The plugin packs your database, media, plugins and themes into a single .wpress file, then unpacks it on the new site. How long that takes depends mostly on file size and server speed.

As a rough guide, most blogs and brochure sites under 500 MB finish the whole job in well under 15 minutes. Large WooCommerce stores and media-heavy sites take much longer.

The rest of this article explains each stage, what affects the timing, and how to tell a slow migration from a stuck one.

What are the stages of a migration?

A migration has three stages: exporting the backup on the old site, moving the file to the new site, and importing it there, and each stage has its own speed limits.

Here is what happens in each one:

  • Export: the plugin reads the database and files and writes them into one archive. This is limited by disk speed and PHP limits.
  • Download and upload: you download the archive to your computer, then upload it to the new site. This depends on your internet connection.
  • Import: the new site unpacks the archive, restores the database and replaces URLs. This depends on server resources.

For many people the upload is the slowest part. A 2 GB file over a slow home connection can take longer than the export and import combined.

If you have not done a migration with this plugin before, our step-by-step guide on how to migrate with All-in-One WP Migration covers the full process.

How long does each site size usually take?

Small sites usually take minutes, mid-size sites take ten to thirty minutes, and very large sites can take an hour or more, mainly because of upload time.

The table gives typical ranges on decent shared or managed hosting. Your times may be faster or slower.

Site size (archive)ExportUpload (typical broadband)ImportTotal rough time
Under 100 MBUnder 1 min1-2 min1-2 minUnder 5 min
100-500 MB1-3 min3-10 min2-5 min5-20 min
500 MB-2 GB3-10 min10-40 min5-15 min20-60 min
2-10 GB10-30 min40 min to several hours15-60 min1 hour or more

Treat these as estimates, not promises. Upload speed varies a lot between connections, and busy shared servers can slow every stage.

What affects how long the migration takes?

Archive size, server CPU and disk speed, PHP limits, your upload bandwidth, and the number of files all affect how long All-in-One WP Migration takes.

The biggest factors are:

  • Media library size. Images and videos usually make up most of the archive.
  • Number of files. Thousands of small files take longer than a few large ones.
  • Database size. Large order, log or revision tables slow the export and the URL replacement.
  • Server resources. Cheap shared plans often limit CPU and disk speed.
  • PHP settings. Values like max_execution_time and memory_limit affect long tasks. The PHP manual lists these in its runtime configuration page.
  • Your connection. Upload speed decides how quickly the file reaches the new site.

Security plugins and server firewalls can also slow uploads by scanning each chunk as it arrives.

Why does the import take longer than the export?

The import often takes longer because the new site has to write every file, rebuild every database table and search and replace old URLs across the whole database.

Writing data is slower than reading it on most servers. On top of that, the plugin replaces the old domain with the new one in every table.

Serialized data, such as widget settings and theme options, has to be handled carefully during that replacement. That extra work adds time on sites with big options tables.

The Restoring database step is often where people think the process is frozen. On large sites it can sit on the same percentage for several minutes while it works through one big table.

Is the upload size limit making it slower?

The free plugin has an import size limit set by the plugin and your server, and working around it with the wrong method can make the process slower or fail.

The free version of the All-in-One WP Migration plugin limits how large an import file can be. Bigger files need either the paid extension or a different upload method.

Our guide to the All-in-One WP Migration import limit explains the limit and the options for raising it.

Uploading through the browser is the most common method. For very large archives, placing the file in the plugin's backup folder by FTP and restoring from the Backups page is often faster and more reliable.

How can you make the migration faster?

Shrink the archive before exporting, use the export filters to skip what you do not need, and move large files by FTP rather than through the browser.

Practical ways to speed things up:

  • Delete unused themes and plugins before exporting.
  • Remove old post revisions, spam comments and expired transients.
  • Use the export options to exclude the media library or cache files if you will move them separately.
  • Exclude large log or backup folders created by other plugins.
  • Run the import when the new server is not busy.
  • Upload the archive by FTP into the backups folder for big files.

Cleaning the database first can make a real difference. Our guide on how to optimize the WordPress database covers safe cleanup steps.

Excluding the media library is a big time saver on image-heavy sites. You can then copy the wp-content/uploads folder by SFTP, which often handles huge folders better.

How do you tell slow from stuck?

A migration is slow if the percentage keeps creeping up over several minutes, and it is probably stuck if the same percentage stays frozen for 20 to 30 minutes or more.

Watch the progress bar. Large tables and big media folders cause long pauses, but the number should move eventually.

Signs that it is really stuck include:

  • No change in percentage for 30 minutes or more.
  • The browser tab showing a network error.
  • A blank or white screen in place of the progress window.
  • The same step restarting from the beginning.

ServMask, the plugin developer, keeps a troubleshooting knowledge base for common stuck points. Our own guide on fixing All-in-One WP Migration when it gets stuck walks through the usual fixes.

Should you use a different method for very large sites?

For sites with archives of many gigabytes, a manual migration or a host-provided tool is often faster and safer than any single-file plugin.

Single-archive plugins work well for most sites. But very large sites push against PHP time limits, upload limits and browser timeouts.

Alternatives include:

  • Your hosting company's free migration service.
  • A manual move: copy files by SFTP and the database with a dump and import.
  • Other plugins that split backups into parts, such as UpdraftPlus.

The WordPress developer handbook has a general guide to moving WordPress by hand. For a plugin option built around large sites, see our guide to a Duplicator large site migration.

What should you check after the migration finishes?

Once the import reaches 100 percent, log in, save your permalinks twice, clear caches and check key pages, forms and checkout before switching DNS.

Quick post-migration checklist:

  1. Log in with the user details from the old site.
  2. Go to Settings, then Permalinks, and click Save Changes.
  3. Clear plugin, server and CDN caches.
  4. Check the homepage, a few posts and any shop pages.
  5. Test contact forms and checkout if you have them.
  6. Look for broken images or links.

If links still point to the old domain, our guide on fixing broken links after migration can help.

Plan for the whole job, not just the import. Leave time for testing and DNS changes so the move does not feel rushed.

Frequently asked questions

Why is All-in-One WP Migration so slow on my site?

The usual reasons are a large media library, a bloated database, slow shared hosting or a slow upload connection. Cleaning up revisions, excluding unneeded folders and uploading the archive by FTP instead of the browser can cut the time a lot.

How long should restoring the database take?

On small sites it takes a minute or two. On large stores with big order or log tables it can take ten minutes or more, and the percentage may pause for a while. If it does not move for 30 minutes, treat it as stuck.

Can I close the browser during an import?

It is best not to. The import runs in steps triggered from the open page, so closing the tab or letting the computer sleep can interrupt the process. Keep the page open and the computer awake until you see the finished message.

Does the paid extension make migrations faster?

The paid extensions mainly remove size limits and add features such as restoring from cloud storage. They do not make your server faster. Speed still depends on archive size, server resources and your connection.

Is it faster to migrate without the media library?

Often, yes. Excluding media makes the archive much smaller, so export, upload and import all finish sooner. You then copy the uploads folder separately by SFTP, which handles large folders well.

Sources

  1. All-in-One WP Migration and Backup WordPress.org
  2. Troubleshooting ServMask Help Center
  3. Runtime configuration PHP Manual
  4. Moving WordPress WordPress Developer Resources

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

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.