RSVP Data Center to Cloud Migration

This manual explains how a Confluence administrator exports RSVP data from RSVP for Confluence Data Center and imports it into RSVP for Confluence Cloud.

The migration is deliberately split into two parts: migrate or create the Cloud pages first, then import RSVP rows into the matching Cloud pages after reviewing page mappings.

Last reviewed: 19 June 2026

Audience and scope

Use this guide if you administer a Confluence Server or Data Center site that uses RSVP for Confluence and you are moving RSVP history to Confluence Cloud.

This guide covers:

• Exporting RSVP data from the Data Center app.

• Uploading the export in the Cloud app migration console.

• Reviewing Data Center page to Cloud page mappings.

• Importing only accepted mappings.

• Verifying the migrated RSVP data.

This guide does not migrate Confluence page content. Move the pages to Cloud first, then use this guide to move RSVP data.

What migrates

The Data Center export contains a deterministic JSON artifact with:

• RSVP rows, including display name, email address, comment, RSVP timestamp, legacy row ID, Data Center page ID, and RSVP ID.

• Page identity metadata, including Data Center page ID, space key, space name, title, and page URLs.

• Per-page and per-RSVP ID macro manifest summaries.

The Cloud import uses the artifact to create a mapping review session. RSVP rows are imported only for page mappings that an administrator accepts.

What does not migrate automatically

• Confluence page content.

• Cloud page mappings without administrator review.

• Skipped or undecided pages.

• Notification history.

• Any cleanup after importing rows to the wrong Cloud page.

If any mapping is uncertain, skip it and resolve it before importing. Re-running an accepted import is designed to upsert the same source rows, but importing with the wrong mapping can still place RSVP data on the wrong Cloud page.

Prerequisites

Before starting, confirm that:

• The Data Center app version includes the RSVP Migration Console.

• You are a Confluence administrator or system administrator on the Data Center site.

• RSVP for Confluence Cloud is installed on the target Cloud site.

• You are a Confluence administrator on the Cloud site.

• Target Cloud pages already exist for the Data Center pages you plan to migrate.

• You know whether this is a full migration or a smaller validation import.

• You have a secure place to store the export artifact. The file can contain personal data.

Recommended first pass: run a small validation export for one space or one page, import it into a test Cloud site or a small target set, and verify the result before running a full-site export.

End-to-end workflow

1. Prepare the Cloud pages.

2. Export RSVP data from Data Center.

3. Open the RSVP Migration Console in Cloud.

4. Initialize Forge storage if it is not already initialized.

5. Upload the Data Center export and generate mapping suggestions.

6. Review and accept only the correct Cloud page mappings.

7. Import accepted mappings.

8. Verify RSVP data on the target Cloud pages.

1. Prepare Cloud pages

Migrate or create the Confluence Cloud pages before importing RSVP data. The importer maps each Data Center page to an existing Cloud page. It does not create Cloud pages.

For each migrated page, confirm that:

• The page exists in the target Cloud site.

• The page title and space make it easy to identify during mapping review.

• Any RSVP macro content that should remain visible has been migrated or recreated.

• The page can be opened by the administrators who will verify the import.

2. Export from Data Center

Open the Data Center migration console from either location:

• Confluence administration > Configuration > RSVP Migration

• Direct URL: <DC base URL>/plugins/servlet/rsvp-admin/migration

The page is admin-only and generates the migration artifact from Data Center storage.

Export options

Use no filters for a full migration export. Use filters only for validation, staged migration, or troubleshooting.

Do not combine Single page ID and Multiple page IDs. At least one of Include pages metadata or Include rows RSVP entries must remain enabled.

Download now vs background export

Use Download now for small and medium exports.

Use Queue background export for full-site or large exports that may take longer. When the job completes, download it from the recent jobs list in the migration console.

Important gzip note

The Cloud upload expects a JSON file. If the Data Center console downloads a .json.gz file, decompress it first and upload the resulting .json file in Cloud.

For a direct browser upload to Cloud, the simplest path is to clear Compress export with gzip before downloading the Data Center artifact.

Optional REST export

Administrators can also export through the REST endpoint:

GET /rest/rsvp/1.0/migration/export
GET /rest/rsvp/1.0/migration/export?spaceKey=ABC
GET /rest/rsvp/1.0/migration/export?pageId=123456
GET /rest/rsvp/1.0/migration/export?pageIds=123,456,789

The export schema version starts at dc-rsvp-export-v1.

3. Open the Cloud migration console

In Confluence Cloud, open RSVP Migration Console from the app configuration or Confluence global settings. The Cloud app exposes the console as an admin settings page.

Only Confluence administrators can open the migration console.

Select Server / Data Center -> Cloud before uploading a Data Center export.

4. Initialize storage

In the Cloud migration console, run Initialize schema if the console says Forge SQL is not initialized for the site.

If the console already shows the schema as initialized, continue to the upload step.

5. Upload export and generate mappings

In the Upload export and generate mappings step:

1. Choose the Data Center .json export file.

2. Confirm the summary: file name, page count, macro count, and RSVP row count.

3. Select Generate mapping suggestions.

Generating mappings creates a review session. No RSVP rows are imported at this step.

6. Review page mappings

Use Review page mappings to decide which Data Center pages should import into which Cloud pages.

For each row, review:

• Data Center page title.

• Data Center page ID.

• Data Center space key.

• RSVP row count.

• Suggested Cloud pages.

Actions available during review:

Only accept mappings you can verify. Skipped and undecided pages are not imported.

7. Import accepted mappings

After accepting the mappings you want to import, select Import accepted mappings.

The importer writes RSVP rows only for accepted mappings. It leaves skipped and undecided pages out of the run.

After the import completes, note the imported row count and imported page count shown by the console.

8. Verify in Cloud

Verify a sample of imported pages before considering the migration complete.

Recommended checks:

• Open each high-value Cloud page with an RSVP macro.

• Confirm attendee names, comments, and counts match the Data Center source.

• Confirm separate RSVP macros on the same page show the expected attendees.

• Export or view attendee data from the Cloud macro if needed for comparison.

• Confirm new RSVP submissions still work on the imported Cloud pages.

• Confirm ordinary Cloud app behavior such as Notify, attendee actions, and settings still works.

For full migrations, validate at least:

• One page from each migrated space.

• One page with multiple RSVP macros.

• One page with comments.

• One page with a larger attendee list.

• One recently updated RSVP.

Troubleshooting

Screenshot placeholders

Add screenshots at these locations before publishing externally. Until screenshots are attached, the capture locations below identify exactly what should be shown.

Existing product screenshots that can help with non-migration verification are available in the Cloud repo at docs/user-manual/screenshots/. Existing Data Center product screenshots are available in the Data Center repo at src/main/resources/images/highlights/. Migration console screenshots still need to be captured from a running Data Center and Cloud environment.

Data handling

Treat the export artifact as sensitive. It can contain names, email addresses, RSVP comments, timestamps, and page references.

Recommended handling:

• Store the export in a restricted location.

• Avoid sending the artifact through email or chat unless your organization permits it.

• Delete temporary local copies after validation and support handoff are complete.

• Keep a record of the export scope, timestamp, and administrator who performed the migration.

Support handoff checklist

When asking Krosoft Support for help, include:

• Source Confluence version and Data Center app version.

• Target Cloud site URL.

• Export scope used: full site, space key, single page ID, or multiple page IDs.

• Whether gzip was used.

• Any Cloud mapping that looked ambiguous.

• Data Center page IDs and Cloud page URLs for problem pages.

• Screenshot of the Cloud migration console error or import result.