Reminder – do not store ‘backups’ on your production SiteWorks site. Always download them and delete them immediately.
Daily backups are available going back 14 days via the SiteWorks Help Desk.

Three reasons for taking a copy of your site are:

  • To try out Plugins before installing them on your production site
  • To train colleagues or try out new designs
  • To have an archive of your site available that can be referred to. Perhaps to lookup deleted past Events or Groups that have closed.

Copy from SiteWorks to Local WP or a new host

The SiteWorks team and SiteWorks sites have by far the most experience with using WPVivid as a tool to copy a site. While we do not formally support WPVivid, we will try and help on a best endeavours basis.

This PDF guide (updated June 2026) has step-by-step instructions on how to backup any SiteWorks site and import backups onto Local WP (or a 3rd part host) using WPvivid.

Note that you cannot copy a SiteWorks site, say from Local WP, to your production SiteWorks server.

The forum (you need to register) is a good place for constructive answers.

Note – if you copy your SiteWorks site to an environment other than Local WP then you must change the Administrator email address (Dashboard -> Settings -> General Settings  …  Administration Email Address). Failure to do so could send emails to the SiteWorks sysadmin team.
Also delete the Main WP Child plugin.