Plugin profile · observed daily since 02 Aug 2026
XServer Migrator
Active installs10,000+ rounded
Current authorXServer
Owner changesNone while we have been watching
Last release1 month ago 30 Sep 2026
Support— no recent threads
Releases on record5
Rating— no ratings yet
Added to directory30 Nov 2018
Requires WP4.2.29
Requires PHPfalse
Version lag0 up to date
Tested up toWP 7.1.4 up to date
PluginsPedia reports published data and observable changes. It does not rate plugin quality or safety, infer intent, or make recommendations. These are observations rather than a verdict. How this works
Ownership
Held by XServer throughout, with no change of ownership observed since daily tracking began on 02 Aug 2026.
Full observed history, including every field transition
Committing accounts
Read from the plugin’s public release log, so these predate this registry. A committing account is not an owner. Thirty accounts commit to WooCommerce and it has never changed hands.
| Account | Releases | First | Last |
|---|---|---|---|
| xserverjp | 4 | 06 Aug 2024 | 09 Jan 2025 |
This registry did not observe a transfer; it read these names off a public log. Whether that reflects a change of ownership is not something the directory publishes.
Adoption
How widely the plugin is installed, and what the people running it think of it. WordPress.org rounds install figures to one significant digit, so they describe an order of magnitude rather than a headcount.
Widely adopted: 10,000+ active installs. Among the more broadly installed plugins in the directory.
293 downloads a day over the last 7 days, falling 28% against the 7 days before. Downloads are counted exactly and without a ceiling, so they show movement the rounded install figure cannot.
11 Sep 2026peak 4,539/day31 Oct 2026
No ratings on record, so there is no sentiment to report.
Daily record
Every field we record, one column per observation. Fields that never moved are named once rather than repeated across every column. A row of identical numbers would be padding.
| Field | 18 Oct | 19 Oct | 20 Oct | 21 Oct | 22 Oct | 23 Oct | 24 Oct | 25 Oct | 26 Oct | 27 Oct | 28 Oct | 29 Oct | 30 Oct | 31 Oct |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Downloads that day | — | 80 | 158 | 163 | 494 | 1,184 | 673 | 313 | 227 | 423 | 309 | 284 | 267 | 231 |
Unchanged throughout: ratings total (0) · active installs (10,000+) · version (1.6.7) · support threads (0) · threads resolved (0)
81 days of observation, most recent 14 shown.
Maintenance
When it was last released, and how far its declared compatibility has drifted from current WordPress.
Added to directory7.5 years ago 30 Nov 2018
Requires WP4.2.29
Requires PHPfalse
Version lagcurrent
Is anyone still maintaining this?
- Last released 30 Sep 2026, 40 days ago.
- Declares compatibility with WordPress 7.1.4, which is current.
- The same account maintains 2 other plugins, 1 of which was updated in the last 90 days. the account is active.
A plugin that does one thing correctly may need no changes for years; a long gap is not, by itself, evidence of neglect.
History
Everything dated that this registry holds about the plugin, most recent first. Releases carry the author’s own release date; everything else is dated to when it was observed.
Entries marked from the release log predate this registry, and daily observation began 02 Aug 2026. They were read from the plugin’s public SVN history after the fact, not watched as they happened. Everything else was observed directly.
- 02 Oct 20261 month agoReturned to the WordPress.org directoryThe plugin resumed returning data from the plugin API after a recorded closure. WordPress.org does not publish reasons for closures or reinstatements; none is asserted here.
- 30 Sep 20261 month agoVersion 1.6.7 released
- 30 Sep 20261 month agoReleased after a long silenceA new release arrived 629 days after the previous one (2025-01-09). A break in dormancy is a maintenance observation, not a judgement about the release or the owner.
- 22 Sep 20262 months agoRemoved from the WordPress.org directoryThe plugin stopped returning data from the plugin API for three consecutive daily passes. WordPress.org does not publish a reason when a plugin is closed; none is asserted here.
- 02 Aug 20263 months agoFirst observed by PluginsPediaDaily snapshots of this plugin’s directory record begin here. Everything above this line is observed; anything before it comes from fields the API itself reports.
- 03 Jul 20264 months agoDormancy threshold crossed540 days since the last release (2025-01-09). Dormancy is a maintenance observation, not a judgement about the owner.
- 09 Jan 202522 months agoVersion 1.6.6 released
- 28 Nov 202423 months agoVersion 1.6.5 releasedfrom the release logCommitted by xserverjp.
- 09 Aug 20242 years agoVersion 1.6.4 releasedfrom the release logCommitted by xserverjp.
- 06 Aug 20242 years agoVersion 1.6.3 releasedfrom the release logCommitted by xserverjp.
- 30 Nov 20187.5 years agoAdded to the WordPress.org directoryReported by the plugin API as the date this plugin was added.
What we know, and what we don’t
Everything on this page in one place, including the gaps, so that nothing here is mistaken for a clean bill of health.
What we know
- It has been held by XServer for all 81 days we have observed it.
- It was last released 1 month ago (30 Sep 2026).
- Its author declares it tested up to WordPress 7.1.4, which is current.
- WordPress.org reports 10,000+ active installs.
What we don’t know yet
- Nobody has rated it. The first rating that arrives shows up here.
- No forum threads were open in the two months we measure, so how responsive its support is cannot be said. One new thread starts answering that.
What can’t be known
- Whether the quiet is neglect or a finished plugin. That is the author’s intent, which no dataset records, and a stable plugin can need no changes for years.
Every record on this site, this one included, works under the same limits. We read what WordPress.org publishes about a plugin, never the plugin’s own code, so nothing here says whether a plugin is well built or safe. Install counts reach us already rounded; a change smaller than a band step doesn’t show. We don’t track security advisories yet. For anything older than our first observation we rely on the plugin’s public release log, where one exists. What this registry can and cannot see
Reach out about this record
Corrections, missing context, or anything else about XServer Migrator: a person reads every submission, and corrections get a reply within 5 business days.