DFYFortuneAI Knowledge Base

Set Up Your WordPress Download

Restore your DFYFortuneAI website backup into a fresh WordPress installation with WPvivid, then secure and verify the restored site.

Updated August 11, 2026

Required workflow: install a fresh WordPress site, add WPvivid Backup Plugin, upload the backup supplied on your product download page, and run Restore. The backup is a complete prepared website—not a plugin ZIP—and restoring it can replace existing WordPress data.

1. Prepare a fresh WordPress target

  • Create a new WordPress installation on the intended domain or subdomain.
  • Confirm that the host meets any PHP, disk-space, upload-size, and server requirements stated on the product download page.
  • Enable SSL/HTTPS and confirm that you can enter the new site’s temporary wp-admin dashboard.
  • Download the correct product backup and keep a second untouched copy outside the target site.
Never treat a live site as fresh. WPvivid restoration can replace the target database and files, including users, posts, pages, settings, active theme, plugins, and uploads. If the site contains anything you need, do not restore the DFYFortuneAI package there. Use a separate fresh installation.

2. Install WPvivid Backup Plugin

  1. In the fresh dashboard, go to Plugins → Add New Plugin.
  2. Search for WPvivid Backup Plugin.
  3. Install and activate the plugin.
  4. Open WPvivid Backup → Backup & Restore and select the Upload tab.

Do not use WordPress’s plugin or theme uploader for the full website backup. Those screens accept installable component ZIPs, not a WPvivid backup archive.

3. Upload and restore the product backup

  1. Select the backup file downloaded from the protected product page.
  2. Wait until the upload reaches completion and the backup appears in WPvivid’s backup list.
  3. Select that backup and start Restore.
  4. Confirm the restore action only after checking that this is the intended fresh site.
  5. Leave the tab open while WPvivid restores the database and files. Do not refresh the page or interrupt the process.

Most standard WordPress hosting can run this workflow. Large-upload limits, low execution time, insufficient disk space, file permissions, WAF/security rules, or server caching can still interrupt it. When the product download page provides a different upload method for the supplied file, use that product-specific method.

4. Log in after restoration

The restore replaces the fresh installation’s database, so the temporary administrator created by your host may be replaced. Open the product download page and use the default WordPress credentials listed for that product and edition. Keep those credentials private.

  1. Open the restored site’s /wp-admin/ URL.
  2. Enter the default username and password from the product download page.
  3. After the first successful login, change the administrator password immediately.
  4. Confirm the administrator email address and remove any unused account.

5. Secure and verify the restored website

Post-restore checklist
  • Confirm WordPress Address, Site Address, HTTPS, timezone, and permalink structure.
  • Open the homepage, dashboard, product pages, and any protected customer routes.
  • Review installed themes and plugins, then apply only compatible updates after keeping a restore point.
  • Replace example API keys, email addresses, branding, forms, and third-party settings with your own values.
  • Configure SMTP, caching, security, backup schedules, and cron according to the product documentation and hosting environment.
  • Test the main workflow with non-sensitive sample data before launch.

6. If upload or restoration fails

Do not repeatedly restore over a partially working live site. Record the backup filename and size, hosting provider, PHP version, available disk space, step that failed, exact WPvivid message, and whether the failure occurred during upload, extraction, database restore, file restore, or the first login.

Follow the troubleshooting checklist or submit a support ticket. You may attach up to two screenshots, but crop or redact the default password, security key, protected download URL, API keys, customer records, and payment information.

Keep exploring