{"id":2536,"date":"2026-01-14T20:33:45","date_gmt":"2026-01-14T20:33:45","guid":{"rendered":"https:\/\/docs.wpvivid.com\/?p=2536"},"modified":"2026-02-10T17:58:44","modified_gmt":"2026-02-10T17:58:44","slug":"wpvivid-works","status":"publish","type":"post","link":"https:\/\/docs.wpvivid.com\/wpvivid-works.html","title":{"rendered":"How WPvivid Works"},"content":{"rendered":"<div class=\"wpvivid-doc-hero-intro\">\nThis document explains the core workflow of WPvivid and how backups, migration, and restore are handled internally.<\/div>\n<h2>Core Workflow Explained<\/h2>\n<p>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:<\/p>\n<h4>1. Data Collection<\/h4>\n<p>WPvivid first collects the data required for the operation:<\/p>\n<ul>\n<li>WordPress files, including themes, plugins, uploads, and core files.<\/li>\n<li>The WordPress database and\/or external database<\/li>\n<li>Optional exclusions defined by the user (for example, specific folders or files).<\/li>\n<\/ul>\n<p>This step determines what data will be included in the backup or migration package.<\/p>\n<h4>2. Package Creation<\/h4>\n<p>After data collection, WPvivid prepares a backup package:<\/p>\n<ul>\n<li>Files and database data are processed and organized.<\/li>\n<li>A structured backup package is generated for storage or transfer.<\/li>\n<\/ul>\n<p>This package is the core unit used by WPvivid for backup, migration, and restore operations.<\/p>\n<h4>3. Storage or Transfer<\/h4>\n<p>Once the package is created, it is either stored or transferred:<\/p>\n<ul>\n<li>Saved to local server storage.<\/li>\n<li>Uploaded to a configured remote storage location.<\/li>\n<li>Transferred to another WordPress site during migration.<\/li>\n<\/ul>\n<p>The same package format is used regardless of where the data is stored or sent.<\/p>\n<h4>4. Restore or Deployment<\/h4>\n<p>When restoring or migrating a site, WPvivid applies the package:<\/p>\n<ul>\n<li>Files are extracted to the target location.<\/li>\n<li>Database data is imported.<\/li>\n<li>Existing site data is replaced based on the selected restore or migration action.<\/li>\n<\/ul>\n<h2>Key Components Involved<\/h2>\n<p>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.<\/p>\n<h4>Backup Engine<\/h4>\n<p>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.<\/p>\n<h4>Database Handling<\/h4>\n<p>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.<\/p>\n<h4>File System Handling<\/h4>\n<p>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.<\/p>\n<h4>Storage Connectors<\/h4>\n<p>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.<\/p>\n<h4>Restore Engine<\/h4>\n<p>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.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>This document explains the core workflow of WPvivid and how backups, migration, and restore are handled internally. 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 [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"off","_et_pb_old_content":"","_et_gb_content_width":"","footnotes":""},"categories":[35],"tags":[],"class_list":["post-2536","post","type-post","status-publish","format-standard","hentry","category-kb"],"_links":{"self":[{"href":"https:\/\/docs.wpvivid.com\/wp-json\/wp\/v2\/posts\/2536","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/docs.wpvivid.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/docs.wpvivid.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/docs.wpvivid.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/docs.wpvivid.com\/wp-json\/wp\/v2\/comments?post=2536"}],"version-history":[{"count":6,"href":"https:\/\/docs.wpvivid.com\/wp-json\/wp\/v2\/posts\/2536\/revisions"}],"predecessor-version":[{"id":2544,"href":"https:\/\/docs.wpvivid.com\/wp-json\/wp\/v2\/posts\/2536\/revisions\/2544"}],"wp:attachment":[{"href":"https:\/\/docs.wpvivid.com\/wp-json\/wp\/v2\/media?parent=2536"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/docs.wpvivid.com\/wp-json\/wp\/v2\/categories?post=2536"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/docs.wpvivid.com\/wp-json\/wp\/v2\/tags?post=2536"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}