WING Website Migrator
A website migration plugin for ConoHa WING hosting service.
Use with caution
WING Website Migrator works, but test it on a staging site before relying on it in 2026. It runs on 500+ sites and was last updated 4 months ago, and scores 55/100 on our health check.
- Momentum — downloads up 45.6% vs the previous 30 days
- Small user base (500+ active installs)
- Very few reviews so far
How does it stack up?
Side-by-side on installs, updates, ratings & supportDaily downloads
Download spikes usually follow a new release — each site that auto-updates counts as a download.
Rankings
Where WING Website Migrator stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| backup | >100 |
| migration | >100 |
| restore | >100 |
| wing | #1 |
Version adoption
Share of active sites per release.
About WING Website Migrator
From the official readme · v2.1.5Description
This plugin enables the “Easy Migration” feature for WordPress on ConoHa WING.
It allows you to migrate a WordPress site running on another server to your ConoHa WING server.
Target Users
This plugin is available free of charge for ConoHa WING subscribers.
To use the plugin, you need to enter the source WordPress site information from the ConoHa WING control panel.
Please note that this plugin will not function on servers other than ConoHa WING.
Support
For usage instructions, please refer to the ConoHa WING user guide.
ConoHa WING Customer Support: https://support.conoha.jp/wing/
Installation
This plugin requires an active ConoHa WING subscription.
The plugin is automatically installed when you select “Use WordPress Easy Migration” from the “Application Installation” menu in the ConoHa WING control panel and start the WordPress installation after entering the required information.
Changelog
2.1.5
- Fix:
find_running_backup()now ignores stalepending/processinglocks older than 1 hour instead of treating them as an in-progress backup. An abnormally interrupted backup previously left a TTL-less lock inwp_options, blocking every subsequent backup on the same site within_progress(409) forever (orphan lock).AbstractAction::save_job_info()now stampsupdated_aton every write so the staleness check can distinguish a genuinely progressing backup (refreshed each batch cron cycle) from an orphaned lock. Root-cause prevention (persisting the batch-side backup_key before run_backup) is handled on the batch side; this change makes existing orphan locks be ignored once they are older than 1 hour (thewp_optionsrows themselves are not deleted), lifting the permanent block (Issue #57).
2.1.4
- Fix: Force-update
siteurl/homeoptions at the end of DB restore so that/wp-admin/no longer redirects to the source FQDN. The 2026-02-13 design switch delegated URL replacement entirely to the batch-side/usr/local/tools/replace-wp, but in practice that tool does not always land onwp_options.siteurl/home, leaving them at the source URL. WordPresswp_login_url()readssiteurl, so accessing/wp-admin/on the destination redirected to the source domain’swp-login.php. The original reasoning for removing the delegation (“REST API calls aren’t possible after DB restore because nonce/session are invalidated”) still holds for next requests, but synchronous in-request execution via$wpdb— the same pattern ascleanup_restore_files()— is unaffected.RestoreFinishTask::update_target_urls()is now invoked synchronously insideRestoreAction::execute_restore_database()‘s completed branch to set both options totarget_site_url(Issue #54).
2.1.3
- Fix: AbstractAction::save_job_info() now flushes the WordPress object cache before calling update_option(). The 2.1.1 fix only flushed on SQL import completion in RestoreDatabaseTask, but SQL import is split into BATCH_SIZE=100-statement chunks across multiple HTTP requests (needs_continue) to avoid PHP max_execution_time. This affects any restore where the source site’s SQL dump exceeds ~100 statements — a standard WP install with 15-30 tables (DROP + CREATE + INSERT each) plus chunked INSERTs for large tables typically exceeds this, so the bug can fire even on a first restore if the source is sized normally. Symptom: wp_options gets DROPed/CREATEd/INSERTed during a chunk, save_job_info is called at the chunk boundary, update_option reads the stale cached value as $old_value, $wpdb->update() returns 0 rows, add_option fallback is also skipped (cache says value exists), so restore_info is never persisted. The next GET /restore/{id} returns 404 Not Found. Flushing before each save_job_info call fixes this and also guards against future tasks that touch the DB (Issue #49).
2.1.2
- Fix: Backup now excludes
wp-content/object-cache.php,wp-content/advanced-cache.php(WordPress drop-ins), andwp-content/mu-plugins/from archives. Previously these were copied from source and overwrote destination-specific files — the source provider’s Redis/Memcached drop-in config would clash with the destination’s cache plugin config (PHP fatal -> 500), and source-provider-specific mu-plugins (WAF, CDN, security) would overwrite destination-provider mu-plugins that the destination hosting ships (Issue #42). - Fix: BackupDatabaseTask now emits mysqldump-compatible session setup at the head of the dump file (SET NAMES utf8mb4, TIME_ZONE=’+00:00′, FOREIGN_KEY_CHECKS=0, UNIQUE_CHECKS=0, SQL_MODE=’NO_AUTO_VALUE_ON_ZERO,ALLOW_INVALID_DATES’, SQL_NOTES=0) and restores @OLD_* variables in the footer. This fixes restore failures when migrating from MySQL 5.7 to 8.0, where stricter default SQL_MODE rejected
0000-00-00dates (post_date_gmt on legacy sites) and AUTO_INCREMENT=0 rows, and where an implicit TIME_ZONE mismatch shifted datetime values between source and destination (Issue #43).
2.1.1
- Fix: RestoreDatabaseTask now flushes the WordPress object cache after completing SQL import. Without this, update_option() on freshly restored wp_options sees stale cached values as $old_value and skips the add_option() fallback, leaving $wpdb->update() returning 0 rows. As a result, RestoreAction::save_job_info() failed to persist restore_info to the actual DB, causing GET /restore/{id} to return 404 right after restore completion (Issue #36).
2.1.0
- Fix: restore download fully downloads multi-GB archives by looping Range-chunk reads within a single request. The loop exits when remaining time is below DOWNLOAD_TIMEOUT so it never starts a 30s wp_remote_get with only a few seconds of task budget left.
- Fix: backup excluded the plugin’s own work directories (uploads/{brand}-backup, uploads/{brand}-restore) only via a regex that did not match brand names containing underscores (e.g., wing_mig) — rewrote to use Config::get_brand() so backups no longer pull in their own archives (snowball growth).
- Fix: handle_backup / handle_restore now return an error if deleting a stale FAILED job fails, instead of silently proceeding to start() with leftover state.
- API change: POST /backup and POST /restore now accept an optional backup_id / restore_id from the caller. The plugin reuses an existing job if one exists, or starts a new job with the supplied id otherwise. Omitting the id keeps the previous behavior (auto-generated id). This lets the batch layer tie a job to wordpress_migrations.backup_key so retries resume the same work directory instead of creating a new one each time.
- Security: sanitize_job_id now rejects invalid IDs (returning empty string) instead of silently stripping disallowed characters, to prevent accidental ID collisions (e.g.
a/bandabboth reducing to the same job) and path traversal via externally supplied ids. - Cleanup: remove the unused
continuefield from RestoreDownloadTask::download_chunk() now that the loop is driven by the task’s remaining time.
For developers
Is this your plugin? Show off the numbers.
Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.
Best WING Website Migrator alternatives
All backup plugins →FAQ
WING Website Migrator: quick answers
Straight answers, pulled from live WordPress.org data.
Source: WordPress.org
Is WING Website Migrator free?
Yes. WING Website Migrator is free to download and use from the official WordPress.org plugin directory.
Is WING Website Migrator safe to use in 2026?
WING Website Migrator works, but test it on a staging site before relying on it in 2026. It runs on 500+ sites and was last updated 4 months ago, and scores 55/100 on our health check.
How many websites use WING Website Migrator?
WING Website Migrator is active on 500+ WordPress websites and has been downloaded 61,401 times since it launched in October 2018. It was downloaded 549 times in the last 30 days.
Does WING Website Migrator work with WordPress 7.1?
WING Website Migrator is officially tested up to WordPress 7.0.8, while the latest release is 7.1.4. It may still work, but try it on a staging site first.
What PHP version does WING Website Migrator need?
WING Website Migrator requires PHP 7.4 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was WING Website Migrator last updated?
The latest version, 2.1.5, was released on July 29, 2026 (4 months ago).
Who makes WING Website Migrator?
WING Website Migrator is developed and maintained by ConoHa by GMO.
What are the best alternatives to WING Website Migrator?
The most popular alternatives to WING Website Migrator are All-in-One WP Migration and… (5M+ installs), UpdraftPlus: WP Backup & Mi… (4M+ installs) and Jetpack (3M+ installs).
Powered by PageForge
One template and a spreadsheet. A real page for every search.
PageForge turns each row of a CSV into a WordPress page with its own title, URL, SEO fields and schema, built on the layout you already designed. Free on WordPress.org.
- CSV and XLSX, plus Google Sheets on Professional and Enterprise
- Its own title, URL, SEO fields and schema for every page
- Works with the block editor, Elementor, Divi and Avada
- Free on WordPress.org, no credit card
