Content Studio / Publishing & Moving Sites

Backups

Plan and maintain backups for Content Studio content, settings, and media.

What to Back Up

Back up the complete current cyclops-cms-data folder. It contains the authoritative Posts, Events, settings, templates, credentials, uploaded media, Smart Image assignments, and initialization state for the published site.

The Elements Project Is Not Enough

The Elements project contains the site design, pages, and component configuration. It does not contain client changes made after publication. Protect both the Elements project and the live runtime, but do not treat one as a replacement for the other.

When to Back Up

Create a fresh runtime backup before moving the site, installing a major Content Studio update, changing hosts, making structural publishing changes, or performing manual server-file operations.

Keep Backups as Complete Sets

Keep each runtime backup intact and clearly associated with its site and capture time. Do not mix selected files from unrelated or different-age backups unless a documented recovery procedure specifically requires it.

Restoring Safely

The current Content Studio interface does not provide an in-app restore command. Restore a matching complete runtime set using the hosting or file-management method appropriate to the site. Avoid restoring over newer live data unless that rollback is deliberate and authorized.

Verify a Restore

After restoring, run System Health, sign in, and verify Posts, Events, Smart Images, Media Manager, and public pages. Confirm that the restored runtime is writable before returning the site to normal use.