Exporting and importing a site’s setup

Use Tools → Export to copy a Cedros site's setup into a JSON file, then Tools → Import on the destination site to preview and apply it. This is useful for reusing collections, navigation, site settings, and email templates on another site.

A setup export does not contain your site's content or activity history. For recovery that includes site data, use Creating and downloading a backup.

Check what will move

The setup package includes the site's name and metadata, collection definitions, collection rules, any custom schema, site settings, redirects, navigation menus, email templates and snippets, sending-provider definitions, and sender identities.

It excludes content entries, contacts, analytics, and campaign history. It also does not package media files, Vault data, or mailboxes. A menu or template may still refer to a page, image, address, or service on the source site; copying that reference does not copy its destination.

Sending-provider credentials and sender-verification tokens are not included in their exported definitions. Plan to configure and verify email sending on the destination. Do not assume a copied provider definition is ready to send.

The file is readable JSON and can contain settings, email addresses, and custom metadata. Review it before sharing and keep it with people responsible for the destination site.

Both import and export require data operations access. If the controls are unavailable, ask your administrator to check your feature access.

Export the source site's setup

1. On the source site, open Tools → Export. The page normally generates a package when it opens. Wait for Package status: Ready, or select Generate export if no package is available.
2. Select Next to open 2. Review contents. Confirm the site name, included sections, counts, and Generated time.
3. If the source setup has changed since generation, return to 1. Create export, select Regenerate export, and review the new package.
4. Select Next to open 3. Copy or download. Use Inspect artifact JSON to review the complete Site setup package. This view is read-only.
5. Select Copy JSON for pasting into the destination, or Download JSON to save a file. For a download, check that the browser finished saving it.

The filename follows the pattern my-site-setup-export-2026-10-02.json. Keep the source and destination exports clearly labeled so you do not import the wrong one.

If a package cannot be generated, resolve the displayed error before proceeding. After a failed regeneration, do not assume a previously displayed package contains your latest changes; check its Generated time.

Understand what import can replace

Before changing an existing destination site, save its current setup and an appropriate backup. Prefer trying the import on a test site first when the destination already serves visitors.

Import can update the destination's site name, metadata, and included site settings. That may include branding, descriptions, locale, and the canonical site address. Check these values carefully when copying between domains.

Included redirects can update matching source paths. An included navigation menu replaces the existing items in the matching menu. Email templates and snippets with matching names can be updated. Leaving a section out does not make import a complete reset of the destination.

Under Advanced options, Replace existing collection rules with the ones in the setup controls collection rules only:

• On: Apply the imported collection rules. This option starts enabled.
• Off: Keep existing collection rules instead of applying the imported rules.

Turning it off does not prevent changes to site settings, menus, redirects, or email templates. If you only want a small part of a site's setup, have the package reviewed for that purpose before applying it.

Reset to Defaults is a separate operation. You do not need it before importing a setup, and it is not an undo button for an import.

Preview on the destination site

1. Confirm you are signed in to the intended destination site, then open Tools → Import.
2. Paste the exported JSON into Setup contents. If you downloaded a file, open it in a text editor and copy the complete JSON. Do not paste a backup ZIP or a WordPress export here.
3. Wait for Setup details to show the parsed Setup summary. Check the source site name and section counts. Resolve any Invalid import JSON message before continuing.
4. Open Advanced options and turn on Preview the import without making any changes. Preview is not enabled by default.
5. Set Replace existing collection rules with the ones in the setup to your intended choice, then select Preview Import.
6. Wait for Preview — nothing was changed and review the reported section counts and whether collection rules would be kept or replaced.

The initial Setup summary describes the package you pasted; it is not a completed preview. The preview report shows what that import would process, not a field-by-field comparison of every old and new value.

If you edit the JSON or change the collection-rule option, run Preview Import again. A report already on screen may belong to the earlier input. A successful preview does not reserve the destination's state against changes made by another administrator.

Apply and check the setup

1. Confirm the destination, JSON, and collection-rule choice still match what you previewed.
2. Turn off Preview the import without making any changes. The action changes to Import Setup.
3. Select Import Setup only when ready to change the destination. This applies the import directly; there is no additional import confirmation dialog.
4. Wait for Import complete and the Imported report, then inspect the affected settings on the destination site.

Check the site name, branding, canonical address, navigation, redirects, and any custom collections you expect to use. Open representative menu links and verify that their content exists on the destination.

Review email templates and snippets for source-site links and sender details. Newly imported sending providers start inactive, and newly created sender identities start unverified. Existing records can behave differently, so inspect the destination's actual configuration before sending. See Connecting and managing service providers for connection setup.

If a warning says the operation's history could not be saved, read it alongside the import result. A history warning does not by itself mean the import failed. Check the destination before repeating an operation that may already have completed.

Resolve common problems

Next or export actions are disabled. Wait for generation to finish and confirm your access. Review and download require an available package.

Copy JSON does not work. Try Download JSON and copy the saved file's contents instead. Check the browser's clipboard permissions if needed.

Invalid import JSON. Re-copy the entire setup package. A syntactically valid JSON object can still be rejected by the server if it is not a supported Cedros setup export.

The export format is newer than the destination supports. Ask your site operator to update the destination to a compatible version. Do not change the format number just to bypass the check.

The custom schema is rejected. The setup conflicts with the destination's existing schema. Ask your site operator to review the reported incompatibility before applying changes.

The button still says Preview Import. Preview remains enabled. Turn it off only after reviewing the result and deciding to apply the setup.

The request failed or the page disconnected. Read the error and check the destination before retrying. If the result is uncertain, ask your operator to verify whether the import completed.