Cross-domain Confluence sync for segregated environments

The problem

Teams maintain a “real” wiki in one domain and a stale copy in another. Someone exports PDFs or pastes pages by hand. Auditors ask which version is authoritative — and nobody can answer confidently.

How Churrie Sync helps: map origin spaces to destination instances on a controlled route. One-way sync (default) keeps the source of truth at home while consumers receive updates — not a second authoring surface.

When cross-domain sync fits

  • Production wiki publishes outward to partner or downstream environments
  • Segregated networks where two-way editing would violate policy
  • Same organization, multiple Confluence DC instances that must stay aligned
  • Restricted networks using the optional middle-man REST relay

How to set it up

  1. In admin, create a Destination with URL, Bearer/PAT auth, and conflict policy.
  2. Run Test connection & deliver with a real payload.
  3. Under Space Authorization, map origin space → destination space → destination instance.
  4. Run Full Sync on first authorization to bulk-load existing content.
  5. Authors use the Churrie Sync pill to opt pages in or out per destination.

What syncs automatically

Pages, blog posts, comments, attachments, labels, and permission groups (where destination groups exist) — on create, update, delete, move, trash, and restore.

Pair with classification restrictions when sensitive content must not cross a boundary. See the full Churrie Sync features reference.