Content Studio / Publishing & Moving Sites

Moving a Published Site

Relocate an existing published site without losing its managed content.

Back Up Before the Move

Create a current backup of the live cyclops-cms-data folder before changing servers, domains, folders, or publishing locations. Keep the backup separate from the files being moved.

Move the Site as a Complete Set

Move the published site files, cyclops-cms application code, and the complete cyclops-cms-data runtime folder. Runtime data includes Posts, Events, settings, credentials, uploaded media, and Smart Image assignments. Preserve the sibling relationship between application and data folders.

Republish at the New Location

Publish the Elements project to the new destination so page files and publisher configuration describe the new location. Content Studio can accept a relocated administration path when the published site contains one clear valid Content Studio instance. If relocation is missing or ambiguous, it preserves the existing authority and assignments instead of guessing.

Recheck Location-Sensitive Settings

Review the configured Preview Page and Logout destination after a folder, path, or domain change. In particular, check custom URLs and any destination that may still refer to the previous location.

Verify the Moved Site

Open public pages, sign in, verify Posts and Events, check Smart Images and Media Manager, and run System Health. Test Preview and Logout behavior. If Content Studio reports that it cannot find the published instance, do not create a replacement runtime; verify the published location and configuration.