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

Plugin how-tos · Guide

How to Migrate with All-in-One WP Migration

Short answer

To migrate with All-in-One WP Migration, install the plugin on your old site and on a fresh WordPress install at the new host. Export the old site to a single .wpress file, then open All-in-One WP Migration > Import on the new site and upload that file. After the import finishes, save your permalinks, clear caches and log in with the old site's user details.

Key takeaways

  • All-in-One WP Migration packs a site into one .wpress file with its database, media, themes and plugins.
  • The free plugin exports any size, but your host sets the largest file you can upload on import.
  • Install the plugin on both sites and start with a fresh WordPress install at the new host.
  • After import, save permalinks twice and log in with the username and password from the old site.
  • Keep the old host live for 7 to 14 days, as of November 2026, so you can roll back if needed.

What does All-in-One WP Migration move?

All-in-One WP Migration moves your whole site in one .wpress file, with its database, media, themes and plugins.

The plugin is listed on WordPress.org as All-in-One WP Migration and Backup, and its page says it has been trusted since 2013. WordPress.org also says it is used by over 60 million websites worldwide, as of November 2026.

The import updates URL references and handles serialized data, according to the WordPress.org plugin page. That matters when your domain or host path changes, because plain text replacement can break stored settings.

A migration is a move of a site from one host or domain to another. A backup is a copy you keep so you can restore the same site later.

What movesIncluded in the .wpress fileNotes
DatabaseYesPosts, pages, users, settings and orders
Media libraryYesFiles in the uploads folder
ThemesYesActive and inactive themes
PluginsYesActive and inactive plugins
WordPress core filesNoInstall WordPress fresh at the new host first

What do you need before you start?

You need admin access to both sites, a fresh WordPress install at the new host, and a copy of your .wpress file.

Start with a fresh WordPress install on the new host, then add the plugin there. Do not import into a live site with content you want to keep, because the import replaces matching content.

Check that the new host meets the WordPress needs for your site. The WordPress hosting requirements guide explains the PHP and database versions to look for.

Make a separate backup before you start, and keep it outside the site you are moving. Our how to back up WordPress guide shows the steps for a full backup.

You also need:

  • Your old site login and your new host login
  • Enough disk space for the .wpress file on both hosts
  • The new host's upload limit, shown on the plugin Import screen
  • Time when few visitors are online, if the site takes orders or comments

WordPress.org advises lowering DNS TTL to 300 seconds at least 48 hours before a move. It also advises keeping the old host active for 7 to 14 days as a safety net, as of November 2026.

How do you install All-in-One WP Migration on both sites?

Install and activate the same plugin on the old site and on the fresh install at the new host.

On each site, go to Plugins, then Add New, search for “All-in-One WP Migration”, then click Install Now and Activate. The plugin then appears in the left menu of the WordPress dashboard.

The plugin page lists version 7.113 as the latest version in its changelog, as of November 2026. Version 7.111 made export and import require administrator rights, so use an admin account for the move.

The plugin page also lists PHP 5.3 to 8.4 support and 50 or more languages, as of November 2026. Updates arrive every two weeks or at least once a month, according to WordPress.org.

If the plugin does not appear after activation, check that you are logged in as an admin. On a multisite network, a network admin must install it, and a subsite move needs the separate Multisite Extension.

How do you export your site with All-in-One WP Migration?

Go to All-in-One WP Migration, then Export, then choose File to create one .wpress file.

Open the Export page on the old site. The ServMask user guide says the export creates a backup in the wp-content/ai1wm-backups folder, with a name based on your site name plus the date and time.

Before you export, open Advanced options and check the boxes for items you want to leave out. The free version lets you skip spam comments and post revisions, while some other skip options need a paid extension.

Do not skip the database, media, themes or plugins for a full move. ServMask warns that those choices lead to an incomplete migration, so use them only to find a fault.

The export page also has Find and Replace fields for text in the database. ServMask says normal migration does not need this, because the plugin handles the site URL change on import.

You can protect the export with a password on the same page. Store that password somewhere safe, because ServMask warns that a lost password can lock you out of the backup for good.

When the export finishes, download the .wpress file to your computer. Keep that file safe, and note its size so you can compare it with the new host upload limit.

How do you import the site on the new host?

Go to All-in-One WP Migration, then Import, on the new site and upload the .wpress file.

Open the Import page on the fresh install at the new host. Choose File from the Import From list, then pick the .wpress file you downloaded from the old site.

The import shows a warning that the new backup will replace matching content. Read it, then click Proceed only when you are sure the destination has nothing you need to keep.

After you click Proceed, you cannot stop the import, according to the ServMask user guide. The time it takes depends on the size of your site data, so leave the tab open until it ends.

When the import ends, the plugin shows a success message. ServMask then advises you to open Settings, then Permalinks, and save your permalinks twice to rebuild the rules.

Log in next with the username and password from the old site. ServMask says the old users and passwords move to the new site, so the new install login stops working after import.

How long does a migration take?

A small site can finish in minutes, while a large media-heavy site can take much longer.

The plugin works in 512KB chunks, according to WordPress.org, which helps it run on shared hosting with low memory. Even so, a large uploads folder and a large database add real time to both export and import.

Your upload speed also matters, because you download the .wpress file and then upload it again. A slow home link can add more time than the plugin itself.

Plan the DNS change as a separate step. ServMask says name server changes can take up to 48 hours to take effect, depending on your provider.

For a rough plan, allow:

  • 15 to 30 minutes for a small blog with few images
  • 1 to 2 hours for a medium site with a large media library
  • A full day of checks for a store, with orders paused during the move

Do not close the browser tab during export or import. If the page closes, you may need to start that step again and check what was left behind.

What is the All-in-One WP Migration import size limit?

The free plugin has no upload limit of its own, but your host sets the largest file you can upload.

ServMask states this plainly in its user guide: you can upload a file of any size as long as your server and host permit it. The Import screen shows the limit your host sets.

WordPress.org gives the same answer: your hosting company decides how large a file you can upload, and the Import screen shows that number. That is why old guides that quote a fixed plugin cap are out of date.

If your file is too large, ask your host to raise the limit, or raise it yourself if your host allows it. WordPress.org lists this .htaccess example: php_value upload_max_filesize 512M and php_value post_max_size 512M, plus client_max_body_size 512m for Nginx.

The paid Unlimited Extension is the other path. ServMask lists it at $69 per year for a Standard License covering up to 50 sites, as of November 2026, and says it adds one-click Restore from the Backups page.

Read our All-in-One WP Migration import limit guide before you pay for anything, because a host limit change may fix the same block for free.

How do you check that the migration worked?

Open the home page, log in, click through key pages, and test forms, search and checkout.

Start with the front page and 3 to 5 key pages. Look for missing images, broken styles and links that still point to the old domain.

WordPress.org lists broken images as a common fault after a move. It advises checking that wp-content/uploads/ moved in full, with 755 for folders and 644 for files.

Check these items in order:

  1. Home page loads, with images and styles in place
  2. Admin login works with the old site user details
  3. Posts, pages and media open from the new host
  4. Menus, widgets and forms work as before
  5. Search works, and a store checkout completes a small order

Save permalinks again if pages show 404 errors. WordPress.org says re-saving permalinks under Settings, then Permalinks, rebuilds the rewrite rules.

Clear all caches after the import, including any cache plugin and any host cache. A stale cache can hide a fault, or show the old site after the move.

If you changed domain as well as host, set up 301 redirects from old URLs to new URLs. Our how to change hosting without losing SEO guide covers that step in more detail.

What if the import fails or gets stuck?

Check the file size, the PHP limits, and the import progress, then try the file again from a clean state.

First, compare the .wpress file size with the limit shown on the Import screen. If the file is larger, raise the host limit or use the Unlimited Extension path from the last section.

Next, check PHP memory and run time with your host. WordPress.org advises raising max_execution_time and memory_limit when an import stalls, and it lists at least 512 MB of PHP memory for large multisite moves.

If the import stalls near the start, close the tab and try again with a fresh browser session. Do not run two imports at once on the same site.

For a stuck import, read our All-in-One WP Migration stuck import fix for the step-by-step checks. That guide covers the same plugin, so it fits this move without new tools.

If pages show a white screen after import, turn on WP_DEBUG in wp-config.php to see the real error, as WordPress.org advises. Check that the PHP version matches between the old and new servers.

How do you move the domain to the new host?

Point the domain at the new server, then wait for DNS to spread before you switch off the old host.

You can test the new site before DNS changes by adding the new server IP and your domain to your hosts file. ServMask explains this step in its user guide for a move to a new server.

After the import checks pass, log in to your domain registrar and change the name servers to the ones your new host gave you. ServMask says this change can take up to 48 hours, depending on your provider.

Remove the hosts file line after DNS has moved, so your computer stops forcing the new server IP. ServMask lists this clean-up step in the same guide.

Our how long DNS propagation takes guide explains why some visitors see the new site before others. Keep the old host live until the change has spread.

Do not cancel the old host on the same day. WordPress.org advises keeping it active for 7 to 14 days, so you can roll back if a fault shows up late.

What mistakes should you avoid?

Do not import into a site with content you want to keep, and do not cancel the old host too soon.

The import replaces matching content, so a destination with posts or settings you need will lose them. Start with a fresh WordPress install, as the plugin page advises.

Other common mistakes are:

  • Skipping the database, media, themes or plugins in Advanced options
  • Using Find and Replace for the site URL when the plugin already handles it
  • Closing the browser tab during export or import
  • Forgetting to save permalinks twice after import
  • Forgetting the old site login, which becomes the login after import
  • Losing the backup password, if you set one on export

Keep at least 3 copies of your data in 2 places, with 1 copy off-site, as WordPress.org advises in its backup guidance. That rule is often called 3-2-1, and it gives you a way back if the .wpress file is lost.

Check the site the next day as well as right after the move. A fault in a form, a scheduled post or a store order can show up only when the site is used again.

Frequently asked questions

Is All-in-One WP Migration free to use for a move?

Yes, the free plugin exports a site of any size and lets you import the file on the Import screen. Your host sets the largest file you can upload, so a very large file may need a host limit change or the paid Unlimited Extension.

Do I need WordPress already installed on the new host?

Yes. Install a fresh copy of WordPress on the new host, then install and activate All-in-One WP Migration there. The .wpress file holds your database, media, themes and plugins, but it does not hold WordPress core files.

What login do I use after the import finishes?

Use the username and password from the old site. The import moves users and passwords to the new site, so the login you made on the fresh install stops working after the import.

Why does my site show 404 errors after migration?

The rewrite rules often need a rebuild after a move. Go to Settings, then Permalinks, and save the settings twice. Clear caches after that, then open a few key pages to check they load.

Can I migrate a WooCommerce store with this plugin?

Yes, you export and import a store the same way as any WordPress site. After the move, check payment keys, webhook URLs and checkout with a small order. Pause new orders during the move so no order lands on the wrong host.

How do I move a WordPress multisite network with this plugin?

A full multisite move needs the separate Multisite Extension, and the vendor advises at least 512 MB of PHP memory for large multisite moves. A single subsite can be moved on its own, with table prefixes and media paths changed by the plugin.

Sources

  1. All-in-One WP Migration and Backup WordPress.org
  2. All-in-One WP Migration User Guide ServMask Helpdesk
  3. All-in-One WP Migration Unlimited Extension ServMask
  4. Why All-in-One WP Migration Shows an Upload Limit (And How to Fix It) ServMask Blog
  5. All-in-One WP Migration Changelog WordPress.org

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