← DPM DOCUMENTATION / BACKUP & RESTORE

DIGITAL PRODUCT MANAGER PRO

Getting Started

Create a complete portable backup of your DPM store data and DPM-managed files, preview its contents and restore it safely when needed.

Full Backup & Restore gives you a portable backup of the information Digital Product Manager Pro needs to operate your digital product store.

It is designed for DPM migrations, disaster recovery and safe store-level backups. A full backup includes DPM-managed store data together with the DPM-managed files required by your products and licensing system.

Before restoring, DPM provides a preview so you can inspect the backup and understand what will be restored.

1. Open Full Backup & Restore

Go to Digital Products > Full Backup & Restore.

The screen is divided into backup and restore tools. From here you can create a new full DPM backup, select an existing DPM backup package for inspection and preview its contents before committing to a restore.

Full Backup and Restore screen in Digital Product Manager Pro

2. What a Full DPM Backup Is For

A DPM backup is intended to preserve the DPM-managed part of your digital commerce system. Typical uses include:

  • Moving DPM data to another WordPress installation.
  • Keeping a recoverable copy before major site or DPM changes.
  • Recovering DPM store data after a site problem.
  • Preserving product, customer, order and licensing information together.
  • Keeping DPM-managed product and protected-delivery files with the store data that references them.

Because the backup is DPM-specific, it can be used without treating DPM as a separate full-site backup product.

3. What the Backup Preserves

Full Backup & Restore is designed to preserve DPM's commercial data and DPM-managed files as one portable package. This includes the information needed for products, customers, access, orders and licensing to remain connected after restoration.

Importantly, DPM also preserves the Licensing Identity registry. Licensed products use a permanent managed identity rather than depending on a changeable WordPress post ID, so restored products can continue to represent the same commercial licensing identity.

DPM-managed protected product files and generated licensing assets are included where required by the backup system so restored records do not point at missing DPM-managed files.

4. Create a Full Backup

To create a backup, open the Full Backup & Restore screen and use the full-backup action.

DPM collects the supported store data and DPM-managed files into a portable backup package. Keep the resulting backup file somewhere secure, particularly if it contains real customer, order or licensing information.

For an important production store, create a fresh backup before performing a migration, major update or restore operation.

5. Keep Backup Files Secure

A full DPM backup can contain commercially sensitive information. Treat it like any other private business backup.

  • Store backups somewhere only authorised administrators can access.
  • Do not publish backup packages in a public downloads folder.
  • Do not send a production backup to another person unless they are authorised to access its customer and store information.
  • Keep more than one recent backup when the store is commercially important.

6. Select a Backup for Restore

In the restore area, choose the DPM backup package you want to restore.

DPM inspects the package before restoration. This validation step helps prevent an unrelated or unusable file from being treated as a DPM store backup.

Use a backup created by DPM's Full Backup system rather than manually assembling or editing the archive.

7. Preview Before Restoring

DPM provides a restore preview before the final restore action. Use this screen to check that you selected the intended backup and to review the data DPM has found inside it.

The preview is particularly useful during migrations because it gives you a final checkpoint before the destination store is changed.

If the preview does not match the backup you expected, stop and select the correct package rather than continuing.

8. Restore the Backup

Once you have reviewed the preview and are satisfied that the correct package is selected, continue with the restore action and confirm it when prompted.

DPM restores the supported store records, licensing identity information and DPM-managed files contained in the package. Allow the restore to complete before making additional changes to products, customers or licences.

After restoration, review the DPM dashboard and the key administration screens before opening the restored store to customers.

9. Post-Restore Checks

After a restore or migration, check the areas that matter to your store:

  • Products appear with the expected settings and protected files.
  • Customers and Customer Access records are present.
  • Orders and purchase records are available.
  • Software licences are associated with the correct customers and products.
  • Managed Licensing Identities are intact.
  • Licensed WordPress plugin and theme packages remain available where expected.
  • The customer portal displays the correct products, downloads and licence information.
  • A protected download works on the restored site.

For a licensed product store, also perform a controlled licence check or test update before considering the migration complete.

10. Backup Before Restore

If you are restoring into a DPM installation that already contains live data, create a fresh backup of the current store first.

This gives you a recovery point if you selected the wrong backup, discover that the restored package is older than expected or simply need to return to the previous DPM state.

11. DPM Backup vs Full Website Backup

Full Backup & Restore protects the DPM-managed store. It is not a replacement for a complete WordPress hosting or server backup.

Your normal website backup should still protect WordPress itself, Divi or your active theme, non-DPM plugins, the Media Library, site pages, database content outside DPM and any other files managed by the wider website.

For the strongest recovery plan, keep both a normal full-site backup and a recent DPM Full Backup.

12. Migration Guidance

When moving DPM to a new WordPress installation, a safe sequence is:

  1. Create a fresh DPM Full Backup on the source site.
  2. Keep a separate full website/server backup as well.
  3. Install and activate the appropriate DPM edition on the destination site.
  4. Open Full Backup & Restore and select the source DPM backup.
  5. Review the restore preview carefully.
  6. Complete the restore.
  7. Run the post-restore checks above.
  8. Test a customer download and, where applicable, a licence check and protected update.

You're Ready

Full Backup & Restore gives you a practical recovery and migration path for the DPM-managed part of your store without requiring you to rebuild products, customers and licensing relationships manually.

Create backups regularly enough for the importance of your store, keep them secure and always preview a package before restoring it.

DOCUMENTATION
Digital Product Manager Pro for Divi
SIMPLE | POWERFUL | DELICIOUS.