Note: this is an earlier, still incomplete version of the user guide. Updated documentation is in preparation; some screens and labels may differ from the current application.

Confluence import

Confluence Import transfers one Confluence space XML ZIP export into a new or existing Simbioza Workspace. The workflow validates the archive, selects content, maps users and groups, and runs a controlled resumable job with a durable report.

Contents

1. Requirements and export preparation
2. Upload and archive preflight
3. Current pages, history, drafts and deleted pages
4. User and group mapping
5. Repeat import into an existing or new Workspace
6. Run, progress and result
7. Post-import verification

1. Requirements and export preparation

• Export one Confluence space as an XML ZIP archive.
• Do not extract the archive before upload.
• Provide storage for the ZIP, temporary extraction and privately stored attachments.
• Decide the target name, slug, language and identity-mapping policy before import.
• Back up an existing target or use a new slug for a trial import.

The administrator opens Settings → Workspaces → Confluence import.

2. Upload and archive preflight

1. Select the Confluence XML ZIP archive.
2. Select Upload and validate.
3. Review the source space name/key, Confluence version, current and historical page counts and attachments.
4. Enter the target Workspace name, slug and imported content language.

Preflight does not import content. It validates structure, discovers optional parts and prepares mappings. The managed temporary archive is removed after successful completion or explicit cancellation.

3. Current pages, history, drafts and deleted pages

3.1. Import without history

A current-only import transfers the current published version of each page. It is faster and smaller, and is appropriate when the target is active documentation while historical audit remains in the source system or a separate archive.

3.2. Import with history

A history import also transfers previous published versions. On a large space it may multiply runtime and storage. Verify several pages with known changes and compare version counts after completion.

4. User and group mapping

A Confluence identity must not be automatically linked to a local account merely because the names look similar. Map each identity to a confirmed existing account, leave it unmapped or explicitly create an inactive staged account.

• Existing user: select only when you have confirmed the same person.
• Unmapped: content is imported, but the identity receives no local access.
• Inactive user: creates a non-login account that an administrator can later link to the correct provider or activate under organisational policy.

A source group may map to an existing ordinary group, create a new ordinary group or remain unmapped. Memberships and administrative rights are never assumed merely because a group was recognised.

5. Repeat import into an existing or new Workspace

• Replace the existing imported Workspace: permanently removes the previous imported content and imports the new archive. Back it up first and confirm no manually added content would be lost.
• Keep the existing Workspace and import a new copy: leaves the previous import unchanged and uses a different name and slug. Prefer this for comparison.

6. Run, progress and result

Select Import Workspace only after confirming the target slug and mappings. The job runs in resumable steps. A large space may take time; do not restart the same action just because it does not finish immediately.

After returning to the Confluence Import start page, use the Recent Confluence imports table to check the job status and stage. The arrow button reopens the selected job. A completed row also shows a separate document button; select it to open the durable import report.

7. Post-import verification

1. Open the home page and several deep tree branches.
2. Check internal/external links, attachments, images, tables and code blocks.
3. Open the durable report under Recent Confluence imports. Unsupported macros remain clearly marked static content requiring manual review.
4. Compare current page counts and, when selected, historical version counts.
5. Test mapped ACL and groups as an ordinary user, not only as an administrator.
6. Rebuild the search index when imported content is not immediately discoverable.
7. Delete the trial copy or plan target replacement only after acceptance.