How-to guide
Network Admin Backup Workflow for Multisite
A practical walkthrough for WordPress Multisite: what to prepare, which options to choose in Multisite Migrate, and how to confirm it worked.
Short answer
Network Admin Backup Workflow is a common Multisite operations need. Networks share core files and users while each site keeps its own tables and uploads/sites paths, so single-site plugins often miss network scope.
Multisite Migrate backs up full networks or individual subsites with include/exclude scope, Jobs in Chunks for shared hosting, Free local scheduling, Plus BYO cloud (Drive/Dropbox/S3-compatible/SFTP), and Pro tools for remote import, empty-server installs, Staging, network split, extract-one-site, shared-users merge, and migration verify. For “network admin backup workflow”, start in Network Admin (or the subsite dashboard when appropriate), pick the right profile, run or schedule, store offsite on Plus, then prove recovery on Staging before production pressure.
Why “Network Admin Backup Workflow” is different on Multisite
Shared themes/plugins, network tables, and per-site media mean a “complete” backup is a network decision — not a single blog export. Host snapshots help, but they are not the same as an importable Multisite plugin archive you can verify on Staging.
When operators search for network admin backup workflow, they usually need a repeatable path: correct scope, a job that survives PHP limits, an offsite copy when Plus is available, and a restore drill that checks URLs, media, and logins.
Product path: Free, Plus, and Pro
Map “network admin backup workflow” to the right tier. Free covers core network/subsite backup and restore plus one local schedule. Plus adds BYO cloud upload and cloud schedules. Pro adds remote import, empty-server installer, Staging, WP-CLI, network split, and related migration tools.
This workflow aligns with Free where those capabilities appear. Do not invent destinations the product does not ship: native Plus targets are Google Drive, Dropbox, S3-compatible storage, and SFTP — not OneDrive and not a proprietary Multisite Migrate vault.
Operational checklist
1) Confirm role (Network Admin vs subsite manage_options). 2) Set scope and exclusions. 3) Run or schedule with chunked resume. 4) Keep a local archive; push offsite on Plus. 5) Restore once on Staging and verify HTTPS, mapping, media, and users.
If the job stalls, read the last log line before raising limits — many failures are disk, locks, or blocked AJAX.
Steps
- Confirm role and scope
Network Admin for fleet jobs; subsite admin for one site. Decide whether “network admin backup workflow” needs the whole network or a subset. - Configure the job
Set options that match network admin backup workflow — schedule, cloud destination, encryption, or split — without packing unrelated noise into the archive. - Run or schedule with chunks
Watch progress. Allow Jobs in Chunks to resume on large networks instead of restarting from 0% after a PHP kill. - Store a recoverable copy
Keep local retention. On Plus, confirm the Drive/Dropbox/S3-compatible/SFTP object exists and is readable. - Verify recovery
Import or restore on Staging. Check URLs, media, logins, and critical plugins before DNS or production cutover.
Frequently asked questions
Does Free cover network admin backup workflow?
Local Multisite backup and one schedule stay Free. Cloud upload/schedules need Plus; remote import and Staging need Pro.
Is this only for Multisite?
Single-site is supported; Multisite networks are the harder case this guide targets.
Where are official docs?
Open the linked Multisite Migrate docs below for UI screenshots and field-level options.
What should I verify after restore?
Mapping, media, logins, and critical plugin data. A backup is only proven after a Staging restore drill.
Sources
Related guides and comparisons
Make your first restorable network backup for free.