Move Confluence into orboto docs

Added in v0.232.0 The Atlassian site import moves a whole Atlassian Cloud site into orboto: the Jira projects (see Move a whole Jira site to orboto) and the Confluence spaces, in one run. Links between Jira issues and Confluence pages keep working after the move: a ticket that linked to a Confluence page opens the imported doc, and a page that linked to a Jira issue opens the imported ticket.

You need the admin:import permission. The run reads the site with an Atlassian API token; orboto checks it, keeps it encrypted for at most 24 hours and deletes it when the run ends.

Before you start

• Create an API token for an Atlassian account that can read every space you want to move (id.atlassian.com, Security, API tokens).
• Decide whether you move Jira and Confluence together or one of them. Both is the default and keeps the links between them.

Run the import

1. Open Admin -> Import -> Jira and Confluence site.
2. Enter the site URL (for example https://your-site.atlassian.net), the account email and the API token. Leave Jira and Confluence ticked, or untick the one you do not move.
3. orboto discovers the site: Jira projects and people, and every Confluence space with its number of pages and folders. Large sites take a few minutes; you can leave the page and come back.
4. Review the plan:
   • Spaces: every space is selected. Each becomes a docs space whose key is the Confluence space key (letters and digits, up to 32). You can change the key and the name, and make a space restricted so only the people with read access in Confluence see it. orboto proposes restricted for a space that not all users can read in Confluence and tells you why; your choice wins. A space marked cut at the page limit has more pages than the limit allows: raise jira_site_max_pages and discover the site again.
   • Earlier versions: how many earlier versions of a page orboto keeps as revisions (default 10, up to 50). Choose 0 to keep only the current version. You can also leave out comments or attachments.
   • People: the same people mapping as for Jira. A Confluence author who has no Jira account appears here too.
5. Start the import. The progress view shows each space and its pages.
6. Download the report when the run is done.

From the command line: orboto import jira-site start --url https://your-site.atlassian.net --email you@example.com --token-stdin --products jira,confluence, then orboto import jira-site plan <run> and orboto import jira-site apply <run> --wait.

What moves

Page content keeps its structure: headings, lists, tables, code blocks, info, note, warning and tip panels, expand sections, status labels, the table of contents, task lists, mentions and emoji. A macro orboto cannot show keeps its text, and the report lists it by name.

Links

• A link to another Confluence page or attachment opens the imported doc or file.
• A Jira issue link or Jira macro on a page opens the imported ticket; tickets keep their Jira keys.
• A Confluence link in a Jira ticket opens the imported doc. This also works when the ticket was imported before the page.
• A link to something that was not imported stays the original link and is listed in the report, so you can check it.

A docs space with the same key already exists

If an orboto docs space already uses the key, the import would add the pages to that space. orboto never does this silently: the plan shows the existing space and how many docs it holds, and the import starts only after you tick I want to merge into the existing docs space and type the space key. On the API and the CLI the plan space needs confirmMerge: true and the typed confirmSpaceKey. You can also choose another key instead.

Interruptions and second runs

The import works in steps and continues after a restart or a deploy without creating anything twice. If Atlassian asks orboto to slow down, the run waits and continues on its own. A later run of the same site imports only pages that are new since the last run and fixes links that the earlier run could not resolve yet.

What does not move

• Blog posts, whiteboards, databases and embeds
• Edit restrictions, and access granted through Confluence groups (orboto has no groups: a restricted page opens for the people named on it)
• Likes, watchers, favourites and page analytics
• Versions beyond the number you chose, and earlier versions of attachments
• Comment reactions
• Templates, blueprints, space themes and logos
• Archived, draft and trashed pages
• Changes made in Confluence after a page was imported

Limits

Admins change them under Admin -> Backup -> Import and sync limits.