--- title: Export slug: export description: Package up your site's setup as a portable JSON artifact so you can copy it to another Cedros site. productSlug: cedros productLabel: Cedros sectionKey: tools sectionLabel: Tools --- # Export The Export wizard packages up your site's setup so you can copy it to another site. It bundles your structural configuration — collections, rules, settings, navigation, redirects, and email scaffolding — into a single read-only JSON file. You can then hand that file to another Cedros site's import flow to clone a working setup, seed a starter configuration in a new environment, or keep a portable recovery artifact. The export is a structural template only. It does not include your content — entries, contacts, analytics, or campaign history are intentionally left out. If you need to move a whole deployment, use a full backup instead. To run an export or download the artifact, you need the **data:ops:write** permission. Without it, the wizard is read-only and shows a hint near the header; the **Generate export** button is disabled. ## What's on this page The wizard is laid out as three steps, shown in the **Export progress** card at the top with chips for each step. Each step's short description also appears as a subtitle below the step title (for example, "Generate a current setup package from this Cedros site." under **1. Create export**): - **1. Create export** — Generate a current setup package from this Cedros site. - **2. Review contents** — Confirm the destination site will receive the expected setup and records. - **3. Copy or download** — Move the read-only JSON artifact into another Cedros site's import flow. The currently active step is highlighted. Use **Back** and **Next** to move between steps. (Both are disabled while a package is still generating or before any artifact exists.) ### Step 1 — Create export A status grid showing: - **Package status** — **Not generated**, **Generating**, or **Ready**. - **Artifact type** — **Read-only setup JSON**. - **Destination** — **Tools > Import**. Below the grid, a short note explains the step: "Generate a fresh setup package before reviewing or handing it off. This export is meant for cloning a working setup, handing a starter configuration to another environment, or keeping a portable recovery artifact." When you open the wizard, it auto-generates a fresh package for you (if you have permission and none is cached). To make a new one, click **Generate export** — the button reads **Refresh export** once a package already exists. If you lack the **data:ops:write** permission, that button is disabled and shows a **Requires data:ops:write** tooltip. ### Step 2 — Review contents A summary grid that confirms exactly what the package contains: - **Site** — The site name (shows **Unnamed deployment** if none is set). - **Collections** — Number of collections included. - **Contracts** — Number of collection rules included. - **Site settings** — **Included** or **Not set**. - **Redirects** — Number of redirects included. - **Nav menus** — Number of navigation menus included. - **Email templates** — Number of email templates included. - **Email snippets** — Number of email snippets included. - **Sending providers** — Number of sending providers included. - **Sender identities** — Number of sender identities included. - **Custom schema** — **Included** or **Not used**. - **Generated** — Timestamp of when the package was built. Below the grid, a note restates what's covered: "Structural template only — site settings, routing, navigation, and email scaffolding. Content (entries, contacts, analytics, campaign history) is intentionally excluded; use a full backup if you need to migrate the whole deployment." ### Step 3 — Copy or download The handoff step. It shows: - **File name** — The name the download will use. - **Next step** — **Open Tools > Import on the destination site**. - **Inspect artifact JSON** — A collapsible section with a read-only JSON editor showing the full **Site setup package**. View-only — you can't edit it here. Two actions: - **Copy JSON** — Copies the artifact to your clipboard. - **Download JSON** — Saves the artifact as a file. The name follows the pattern `[site-slug]-setup-export-[YYYY-MM-DD].json` (for example, `my-site-setup-export-2025-06-04.json`). ## Common things you can do here ### Clone a working setup into a new site 1. On the source site, open the Export wizard. It auto-generates a package; if not, click **Generate export**. 2. Move to **2. Review contents** and confirm the collections, settings, and email scaffolding are what you expect. 3. On **3. Copy or download**, click **Download JSON** (or **Copy JSON**). 4. On the destination site, open [Import & Export](import-export.md) and paste or load the artifact to import it. ### Hand a starter configuration to another environment 1. Generate the export and review the contents. 2. Download the JSON file and share it with whoever manages the destination environment. 3. Have them open Tools > Import on that site and run the import. ### Keep a portable recovery artifact 1. Generate a fresh export whenever your setup changes. 2. Download the JSON and store it somewhere safe. 3. If you ever need to rebuild structure, import the saved artifact on the target site. ## Tips - **Refresh before handing off.** If you changed collections, settings, navigation, or email scaffolding after generating, click **Refresh export** so the package reflects your latest setup. Check the **Generated** timestamp in Step 2. - **This is structure, not content.** Entries, contacts, analytics, and campaign history are excluded by design. Use a full backup to migrate an entire deployment. - **Copy is faster for site-to-site work.** If you're pasting straight into another tab's import flow, **Copy JSON** skips the download. - **The artifact is read-only.** The JSON shown under **Inspect artifact JSON** is for review only — edit your setup in the relevant admin screens, then regenerate. - **The file name is automatic.** It's built from your site name and the current date, so each download is easy to tell apart. ## Troubleshooting - **Buttons are disabled and there's a read-only hint?** You're missing the **data:ops:write** permission. Ask an admin to grant it before generating or exporting. - **Package status stuck on "Generating"?** The wizard is still building the package; the review and handoff steps show "Generating the latest site setup export..." until it finishes. Wait a moment, then check Step 2. - **Review or handoff step says to generate first?** No artifact exists yet. Go back to **1. Create export** and click **Generate export**. (You'll see "Generate an export before reviewing package contents." or "Generate an export before copying or downloading the artifact.") - **"Clipboard copy is not available in this browser context."?** Your browser blocked clipboard access. Use **Download JSON** instead, or try again over a secure (HTTPS) connection. - **A count looks wrong in Step 2?** The summary reflects exactly what's in the package. If something's missing, fix it in its admin screen, then click **Refresh export** and review again. - **Need to bring the export into another site?** That happens on the destination side — see [Import & Export](import-export.md).