Glossary
What Is the Table Prefix in Multisite?
A plain-language explanation for WordPress Multisite admins, with the practical consequences for backups, restores, and migrations.
Short definition
Table Prefix Multisite is a term operators search when planning WordPress Multisite protection or recovery. On Multisite, shared themes/plugins, network tables, and per-site uploads change what a “complete” backup must include.
Multisite Migrate exposes network-wide and subsite backups, backup scope, profiles, optional .venc AES-256 encryption, Free local schedules, Plus BYO cloud destinations (Google Drive, Dropbox, S3-compatible, SFTP), and Pro capabilities such as remote import, empty-server migration, Staging, network split, extract-one-site, shared-users merge, and migration verify / confirmed search-replace. Understanding table prefix multisite helps you pick the right tier and avoid confusing host snapshots with Multisite-aware plugin archives. Write the definition into your runbook next to scope rules, schedule owners, and the Staging restore checklist so vocabulary becomes operational. When in doubt, run one network or subsite job, store an offsite copy on Plus if available, and prove recovery on Staging before you change production DNS or delete older archives.
What “Table Prefix Multisite” means in Multisite practice
Plain language: table prefix multisite in Multisite is about network scope and recovery paths, not just copying files. Shared resources and per-site tables mean restore drills must check more than one blog’s content.
Host snapshots ≠ Multisite plugin archives, and chunked jobs (how a job survives PHP time limits) ≠ incremental backups (what the archive contains). Keep those distinctions clear when comparing tools.
Where it appears in Multisite Migrate
Find the capability behind “table prefix multisite” on backup, schedule, cloud, restore, or Pro migration screens depending on tier. Free covers core backup/restore and one local schedule; Plus adds BYO cloud; Pro adds Staging and advanced migration flows.
If you only need vocabulary, read this page. If you need the workflow, jump to related how-to and troubleshooting guides, then run one job and one Staging restore so the term becomes operational.
Avoid false equivalents
Do not equate provider snapshots with importable Multisite archives. Do not assume OneDrive is a native Plus destination. Do not treat S3-compatible services (B2, R2, Wasabi, Spaces, MinIO) as separate proprietary Multisite Migrate vaults — they connect as S3-compatible endpoints.
When docs or blogs redefine “table prefix multisite”, map their claims back to Free/Plus/Pro screens before you change production schedules.
Steps
- Read the definition
Map table prefix multisite to Multisite architecture (shared vs per-site) before changing backup settings. - Find it in the product
Open backup, schedule, cloud, restore, or Pro migration screens that own the capability. - Compare tiers honestly
Core backup/restore and one local schedule are Free; cloud needs Plus; Staging/split/remote import need Pro. - Write it into the runbook
Add table prefix multisite next to scope rules, schedule owners, and retention so the team shares one definition. - Apply in a drill
Run one job and one Staging restore so the glossary term becomes an operational habit.
Frequently asked questions
Is table prefix multisite Free?
Core backup/restore and one local schedule are Free; cloud and advanced migration tools need Plus/Pro.
Does Multisite change the definition?
Yes — network tables plus sites/ media make Multisite scope different from single-site backups.
Where next?
Pick a related how-to below, then verify with a Staging restore drill.
Host snapshot vs plugin archive?
Snapshots are an extra host-level layer. Plugin archives are portable Multisite-aware artifacts you can import and verify on Staging.
Sources
Related guides and comparisons
Make your first restorable network backup for free.