Record its active theme, plugins, custom code, users, media paths, mapped domain and integrations. Identify features supplied by network-active or must-use plugins. Check licence ownership and whether configuration is stored per site or shared across the network. Confirm the destination hosting supports the site's actual requirements.

A WordPress WXR export can transfer supported content into a clean installation, with separate work for files, settings and plugin-specific data. A specialised migration tool may handle more of the subsite, but verify its current Multisite extraction support. Do not assume exporting tables with a matching prefix includes every dependency.

1. Back up the network and create a protected independent destination.
2. Install the required theme and plugins from trusted sources, with appropriate licences.
3. Transfer the selected content and data through the tested method, including the actual media files.
4. Map user access deliberately so unrelated network users and their private data are not copied unnecessarily.
5. Update URLs through a serialisation-aware process and configure the standalone site's settings.
6. Test public pages, administration, forms and business workflows with live integrations isolated.

Not necessarily. Identity, passwords, roles and plugin memberships depend on the transfer method. Decide which users should exist on the independent site and test their access. Do not grant all imported users administrator privileges to bypass mapping problems.

For a site receiving transactions, pause writes and perform a final coordinated sync before changing DNS or domain routing. Verify the latest records and enable production integrations only on the intended live copy. Keep redirects from the former address where required.

Only after the destination is verified, its own backups work and the agreed recovery window has passed. Archive the old subsite first if appropriate, and avoid deleting shared network users or plugin data used by other sites. Preserve a record of the transfer and resolve any remaining external service ownership before retiring the network copy.

• Planning backups for a WordPress Multisite network
• Performing a serialisation-safe WordPress search and replace
• Migrating a WordPress site that receives orders or registrations
• Archiving a Multisite subsite instead of deleting it

• WordPress: Administration
• WordPress: Migrating
• WordPress: Tools Export Screen
• WordPress: Tools Import Screen
• WordPress: Backup