BackupsFree + Pro
All-in-One WP Migration MCP: is there a finished export, and can we make one?
Plenty of sites have no scheduled backup at all, only the .wpress exports someone made with All-in-One WP Migration before a move or a redesign. The All-in-One WP Migration MCP abilities let an AI client read those: when the newest complete export finished, how large it is, how many there are, and whether an export or import is running right now. Reading is in GoBuildWP Free. GoBuildWP Pro can also start a full export with the plugin's own export steps, advanced by WP-Cron and backup-status reads, and a finished one counts as the recent backup that safe updates and the fresh-backup hold ask for. Nothing here restores, imports, downloads or deletes an archive.
Verified against All-in-One WP Migration 7.112. Reading needs GoBuildWP Free 1.18.1 or later; starting an export needs GoBuildWP Pro 1.12.2, which checks what the install has rather than its version, and starting one from GoBuildWP Cloud also needs GoBuildWP Free 1.18.2 or later. Scheduled and off-site backups are paid extensions and are not read.
We are switching themes this afternoon. Make sure there is an All-in-One WP Migration export from today first.
wppilot/backup-statusReadFinds three verified exports, the newest from last Tuesday at 1.8 GB, nothing running, and the trigger marked as supported.
wppilot/backup-triggerWriteWith GoBuildWP Pro, starts a full export; the disk has 9 GB free against the 3.6 GB the check wants, and the answer comes back running.
wppilot/backup-statusReadRead again every minute or two until no job is running and the newest verified export is later than the start time.
wppilot/backup-listReadCompares the new archive's size with last Tuesday's to catch an obvious size anomaly. Similar sizes do not prove complete contents or a successful restore.
- Edition
- Free 2 + Pro 1
- Abilities
- 3
- Requires
- WordPress 6.9+, PHP 8.0+
Data model
A folder of .wpress files instead of a backup log
There is no history table to query. The plugin's backups folder, wp-content/ai1wm-backups unless a setting moves it, holds one .wpress archive per export, and the plugin's own file listing gives each one's time and size. While an export is being built it lives in a separate job folder under the plugin's storage directory; only when the last block is written is the archive renamed into the backups folder. A file's time there is therefore when that export finished, and an export that crashed halfway simply never shows up.
A running job is recognised by its job folder changing in the last fifteen minutes, since the archive grows with every step. A folder left behind by an abandoned run stops changing, stops counting as running, and is cleared by the plugin's daily cleanup a day later. The answer cannot tell an export from an import in progress, so it says export or import.
Labels a person typed against a backup in the plugin's screen come back with it. The status response does not establish which contents are inside an existing archive. A new export started through GoBuildWP requests a full export; restore-test the result before relying on it.
Abilities
Three backup abilities, provider ai1wm
| Ability | What it does here | Undo and limits |
|---|---|---|
backup-statusFree | The newest file and the newest verified export, the number of verified exports and of unverified files, any export or import in progress, the plugin version, and whether this site could start an export from GoBuildWP Pro, with the reason when it could not. With GoBuildWP Pro it also reports the export Pro started: running, stalled, failed with the reason, or finished. | Read-only in GoBuildWP Free. With GoBuildWP Pro, while an export Pro started is still running, each backup-status read also runs a short slice of that export, so the call moves the export on as well as reporting it. The free plugin has no schedule, so there is never a next run to report. |
backup-listFree | Exports newest first with finish time in site time and UTC, size, label and an id that is a hash of the file name. | Read-only. A file that fails the archive check is listed as unverified with result unknown, and file names, folders and links never appear. |
backup-triggerPro | Runs the plugin's own export steps on the server, in its order and with its parameters: a first slice as the export starts, then short slices on WP-Cron and before every backup-status answer, so the export does not rely on requests the site makes to itself. Answers running. | GoBuildWP Pro, from MCP, WP-CLI or WP-Cron. No plugin version is checked; a start is refused, with the reason, only when the install lacks something the runner needs. Also refused while a job runs, within an hour of the last start, and when free disk space is under twice the newest export, or 1 GB with none to go by. |
Reference: /docs/reference/backups
Shared module across these plugins; do not add this count across them. Edition and effect labels describe the source catalogue. The installed schema, dependency versions, licence, WordPress capability, safety profile and per-ability policy determine availability; labels alone do not prove confirmation or recovery.
Read example: wppilot/backup-status
Discover this ability and its live schema first. The input below illustrates a bounded read from the source declaration; replace the example ID or name with an object returned by your site. It is not a recorded execution result.
| Parameter | Type and meaning |
|---|---|
provider | string, one of updraftplus, duplicator, backwpup, ai1wm. Only this backup plugin. Defaults to every active one. |
{
"provider": "ai1wm"
}Input and output schema from the plugin source
1 input field. Required: none; see schema alternatives and runtime validation. Optional parameters can affect response size and object selection.
{
"input": {
"type": "object",
"default": [],
"properties": {
"provider": {
"type": "string",
"enum": [
"updraftplus",
"duplicator",
"backwpup",
"ai1wm"
],
"description": "Only this backup plugin. Defaults to every active one."
}
},
"additionalProperties": false
},
"output": {
"type": "object",
"properties": {
"active_providers": {
"type": "array",
"items": {
"type": "string"
}
},
"supported_providers": {
"type": "array",
"items": {
"type": "string"
}
},
"providers": {
"type": "array",
"items": {
"type": "object"
}
},
"newest_successful_backup": {
"type": [
"object",
"null"
]
}
}
}
}Source: wppilot/includes/kits/backup-status/src/abilities/backup-status.php
A successful read should identify the requested object and expose the structure described by the output schema. Compare it with the native editor before proposing a change. Troubleshoot missing or refused operations.
Worked example
A same-day export before a theme switch
Expected outcome to verify on the installed stack; this sequence has not been recorded as a runtime test.
The theme switch goes ahead with a finished export from this afternoon behind it. On GoBuildWP Free the agent stops after the first read and reports that the newest export is several days old, leaving the export to a person in wp-admin.
Read backup-status before starting: an export or import already running, a start within the last hour or a disk short of space each refuse the trigger. After a start, read backup-status every minute or two until a verified export newer than the start time appears; each read also moves the export on. If providers[].export says failed, report its reason; if it says stalled, keep reading before retrying.
backup-statusFinds three verified exports, the newest from last Tuesday at 1.8 GB, nothing running, and the trigger marked as supported.
backup-triggerWith GoBuildWP Pro, starts a full export; the disk has 9 GB free against the 3.6 GB the check wants, and the answer comes back running.
backup-statusRead again every minute or two until no job is running and the newest verified export is later than the start time.
backup-listCompares the new archive's size with last Tuesday's to catch an obvious size anomaly. Similar sizes do not prove complete contents or a successful restore.
What All-in-One WP Migration records
What counts as an All-in-One WP Migration backup
All-in-One WP Migration keeps no backup history of its own. A backup is a .wpress file in its backups folder, and an export is only moved there once its last block is written, so every file in that folder is a finished export dated by when it finished. A failed export leaves nothing behind, which means there is no failure to report, only the absence of a new file.
Anything that can write a file could drop a .wpress there, so a file counts only when it sits in the folder itself, is at least 1 MB, is not dated in the future and ends in a complete archive block, checked with the plugin's own archive test. Any other file is listed as unverified and never satisfies a fresh-backup check.
File names are never returned. Their random suffix is the only thing protecting an archive on servers that ignore the folder's .htaccess, such as nginx or OpenLiteSpeed, so a name is as good as a download link. Each backup is identified by a hash instead.
Limits
Where this integration stops
- A finished, verified .wpress file shows the export completed. It does not show that the archive will import cleanly on another server, so test a restore on staging before relying on it for a migration.
- The free plugin never deletes exports. Each one started from here stays on the web server until someone removes it under All-in-One WP Migration, Backups, which is why starts are spaced an hour apart and checked against free disk space.
- An export moves on only while something drives it: WP-Cron, a backup-status read, or GoBuildWP Cloud's once-a-minute check. On a quiet site with WP-Cron switched off and nobody reading the status, it waits; after three minutes without a finished step backup-status says stalled, and after fifteen the export fails and its half-built job folder is deleted.
- Exports land on the same server as the site. Off-site copies, schedules and cloud destinations are paid extensions that are not read here.
- GoBuildWP runs whatever export steps the installed release registers, and other plugins' callbacks on those steps run as the plugin runs them; WooCommerce's bundled Jetpack connection, for example, locks its tokens while the database is exported.
Questions
All-in-One WP Migration questions
Can Claude restore or import an All-in-One WP Migration backup?
No. Restoring and importing replace the whole site, and they stay in the plugin's own screens. The abilities read exports and, with GoBuildWP Pro, start a new one.
Why does an export show as unverified?
The file is under 1 MB, sits in a subfolder, is dated in the future, or does not end in a complete archive block. It might be a partial copy or a file someone placed there, so it never counts as a backup.
Why won't the agent start an export?
Starting is GoBuildWP Pro, and any All-in-One WP Migration version will do as long as the install has what the export runner calls. It is refused while an export or import is running, within an hour of the last start, and when the disk is short of space. backup-status says whether this site can start one, and the refusal names the reason.
Does GoBuildWP Cloud see these exports?
Yes, once the site runs the GoBuildWP Free release that added All-in-One WP Migration. The Cloud Backups page shows each site's newest verified export, and Cloud can start one on a site whose GoBuildWP Free and GoBuildWP Pro are both recent enough, under the same checks; the requirements on this page name the releases.
Why are file names hidden?
On nginx or OpenLiteSpeed the backups folder's .htaccess is ignored, so knowing a file's name is enough to download the whole site. Answers use a hash of the name instead.
Where these facts come from
GoBuildWP behaviour is taken from the plugin source and the ability reference; third-party details from the vendor documentation below, checked by the GoBuildWP team.
All-in-One WP Migration is a separate product; no partnership or endorsement is implied.