Core Workflow Explained

WPvivid follows a structured workflow to handle backups, migrations, and restores. While the user interface may present different actions, the underlying process is consistent and can be understood in four logical stages:

1. Data Collection

WPvivid first collects the data required for the operation:

• WordPress files, including themes, plugins, uploads, and core files.
• The WordPress database and/or external database
• Optional exclusions defined by the user (for example, specific folders or files).

This step determines what data will be included in the backup or migration package.

2. Package Creation

After data collection, WPvivid prepares a backup package:

• Files and database data are processed and organized.
• A structured backup package is generated for storage or transfer.

This package is the core unit used by WPvivid for backup, migration, and restore operations.

3. Storage or Transfer

Once the package is created, it is either stored or transferred:

• Saved to local server storage.
• Uploaded to a configured remote storage location.
• Transferred to another WordPress site during migration.

The same package format is used regardless of where the data is stored or sent.

4. Restore or Deployment

When restoring or migrating a site, WPvivid applies the package:

• Files are extracted to the target location.
• Database data is imported.
• Existing site data is replaced based on the selected restore or migration action.

Key Components Involved

WPvivid is built on several core components that work together during backup, migration, and restore operations. Each component has a clear responsibility within the overall workflow.

Backup Engine

The backup engine coordinates the entire process. It controls data collection, package creation, and the sequence of operations, ensuring that backup, migration, and restore actions follow a consistent and predictable workflow.

Database Handling

This component is responsible for processing the WordPress database. It exports database data during backups and migrations, and imports it during restore or deployment, ensuring data integrity throughout the process.

File System Handling

File system handling manages WordPress files, including themes, plugins, uploads, and core files. It handles file collection, packaging, extraction, and placement during restore or migration.

Storage Connectors

Storage connectors manage how backup packages are stored or transferred. They provide a unified way to save backups locally, upload them to remote storage services, or transfer them between WordPress sites during migration.

Restore Engine

The restore engine applies the backup package to a target environment. It coordinates file extraction, database import, and data replacement based on the selected restore or migration action.