Confluence Divestiture: Keep Cloud Sites in Sync During Separation

You’re spinning off a business unit onto its own Confluence Cloud site. Legal separation has a closing date. Content separation doesn’t.

Divestitures move on a legal timeline: sign, close, stand up the new entity. Confluence doesn’t move on that timeline. The spun-off business unit needs its own Cloud site before close, but both sides still depend on content that was never meant to live in two places.

The standard approach is a one-time export at cutover — pull the relevant spaces, import them into the new site, done. That solves day one. It does nothing for day ninety. Once both sites exist independently, anything that changes on either side — a revised technical spec, an updated TSA milestone, a corrected project record — silently diverges from its counterpart, because there’s no native mechanism keeping the two Cloud sites aligned after the split. That’s the gap Space Sync for Confluence is built to close.

What this looks like in practice

A mid-size medical device manufacturer is divesting its diagnostics imaging division — 210 employees, its own product lines, its own engineering team — to a private equity buyer. Legal close is set for October 1. IT stands up a new Confluence Cloud site for the diagnostics entity three weeks before close so the new company has somewhere to operate from on day one.

Three sets of content have to stay aligned across both sites for the length of a 9-month Transitional Services Agreement (TSA): historical project records for shared product lines developed before the split, technical documentation for IP the parent still licenses to the divested unit under the deal terms, and the TSA tracker itself — the space that documents what support (IT, quality, regulatory) the parent is still obligated to provide and through what date. All three keep changing after close. Engineering makes a correction to a device spec. Legal updates a TSA milestone. Someone on the parent’s regulatory team adds a new compliance filing to a shared project record.

IT’s first move is what most teams do at cutover: a Confluence space export from the parent site, imported into the new diagnostics site, done in an afternoon. That handles the one-time copy. It does not handle October 15, when the parent’s regulatory team updates a filing on their copy and nobody remembers to update the diagnostics entity’s copy — because there’s no ongoing link between the two sites, just two exports that started identical and immediately began drifting.

What breaks without ongoing sync

• The TSA tracker shows different support end-dates on each site, so the divested entity’s IT lead can’t confirm whether the parent is still obligated to provide a service they’re relying on.
• A device spec gets corrected on the parent’s site after a safety review, but the diagnostics entity keeps building against the outdated version because their copy was never updated.
• Regulatory filings tied to shared product lines exist on one site but not the other, so an FDA audit request pulls incomplete records depending on which entity gets asked first.
• The parent’s engineering team fields the same technical questions twice — once from their own staff, once from the spun-off team working off a stale copy of the same documentation.
• Nobody on either side can say with confidence which site holds the current version of a shared record, so both teams start keeping personal notes instead of trusting the space.

The longer the TSA period runs, the wider the gap gets — nine months is enough time for dozens of small edits to accumulate into two documentation sets that no longer agree with each other.

How Space Sync for Confluence fixes this

Space Sync for Confluence connects specific spaces between the parent’s Confluence Cloud site and the divested entity’s new site, and keeps them synced for as long as the separation requires — through TSA end, not just through cutover. An admin sets up sync pairs for the spaces that matter: shared project records, licensed technical documentation, the TSA tracker itself. From there, edits on either side propagate automatically, so both entities are working from the same content without anyone owning a manual re-export process.

Each site stays fully independent — separate admins, separate permissions, separate user directories, exactly as the legal separation requires. Only the specific spaces named in the sync pair carry over. When the TSA period ends, the sync pair gets switched off and each entity’s Confluence Cloud site stands entirely on its own.

Key capabilities for this scenario:

• Cross-site sync between separate Confluence Cloud instances → shared project records and licensed IP documentation stay identical on both sites without repeat exports
• Scoped sync pairs → only the spaces named in the TSA (project records, technical docs, TSA tracker) sync — nothing else on either site is exposed
• Automatic sync on a schedule → a spec correction or TSA milestone update reaches both sites without someone remembering to re-export
• Manual/on-demand sync option → a compliance-critical update, like a new regulatory filing, can be pushed immediately instead of waiting for the next scheduled run
• Attachment and macro sync included → technical drawings, status-tracking tables, and audit tables carry over intact, not just page text

What changes for your team

Before Space Sync for Confluence, a TSA status review meeting between the parent’s transition office and the diagnostics entity’s leadership started with someone comparing screenshots of the TSA tracker from both sites, because the two copies had already drifted since the last review. Confirming which support obligations were still active ate the first ten minutes of every meeting.

After Space Sync for Confluence, the TSA tracker is the same document on both sites, because it’s synced rather than copied. The parent’s transition office updates a milestone once, and the divested entity sees it without a manual handoff. The monthly TSA review starts with the actual status of the separation instead of a document reconciliation exercise.

Built for the people running this

Multi-site Confluence Admin — You stood up the new entity’s Confluence Cloud site under a close-date deadline, and now you own keeping it aligned with the parent’s site for as long as the TSA runs. Space Sync for Confluence lets you scope sync to exactly the spaces the deal terms require, without merging tenants or granting cross-site access you can’t govern.

Confluence Space Admin — You’re responsible for the shared project records or technical documentation space that both entities depend on, and you’re the one who gets asked which version is current. Space Sync for Confluence keeps your space and its mirror on the other site identical, so that question stops coming up.

A one-time export gets you through closing day. It doesn’t get you through the TSA.

Ricksoft, Inc., is ISO/IEC 27001:2022 certified. Space Sync for Confluence complements the Confluence Cloud sites both entities already run, keeping named spaces aligned without merging tenants or changing how either side manages access.