Backup and migration: three scopes

Use a personal ZIP to move your own documents and settings. Moving an entire host also requires accounts, execution state, and engine connections beyond that personal export.

Try it · Open the personal backup page and review its scope.

Select files, conversations, services, and settings in Export backup. Projects are included with conversations. Estimate the size, export the ZIP, and record its version and date.

Try it · Select demonstration modules, estimate their size, then export the ZIP.

Media is included by default; excluding it can leave missing images in conversations. API keys are excluded unless selected, and exporting them creates a plaintext key file.

Try it · Read the media and API key export notes and keep the demonstration defaults.

Merge restores missing files and skips existing paths. Overwrite replaces the selected modules and snapshots the old data. It requires your current account password to confirm.

Try it · Compare both modes on the demonstration restore page without overwriting real data.

Panel archives config, data, logs, and users. It excludes the environment file and host management key, and may skip unreadable files. It does not guarantee complete migration.

Try it · Open Panel’s backup action and read its scope and result details.

For a full host migration, stop writes and record versions and actual data locations. Preserve databases, encryption keys, and required connection state, including any configured external directories.

Try it · Prepare a host migration inventory and verify actual deployment paths.

Restore in a test location first. Check documents, projects, connections, services, and tasks. Rebuild missing dependencies, verify WeChat state, and only then resume serving users.

Try it · Review demonstration recovery results before enabling tasks and services.