RSVP for Confluence Cloud is moving to Atlassian Forge, Atlassian's cloud app platform.
This page explains what site admins, page owners, and attendees should expect as RSVP moves from the legacy Cloud app platform to Forge.
Last reviewed:
Summary
For most users, RSVP continues to work on the same Confluence pages. Existing RSVP macros remain in page content, and the main workflow stays familiar: view responses, respond, edit or remove your own response, and export responses when you are an organizer.
The important change is behind the scenes: the Forge version stores RSVP data in Atlassian Forge SQL and uses Forge app infrastructure. The rollout is controlled so historical RSVP data is not silently lost or shown as an empty RSVP list before it has been verified or imported.
What is changing
-
RSVP runs on Atlassian Forge instead of the legacy Cloud app platform.
-
RSVP data for the Forge app is stored in Forge SQL.
-
The macro UI is more Confluence-native and may look slightly different.
-
Some admin and migration actions are handled in the RSVP Migration Console.
-
Existing Cloud and Server/Data Center migration paths are handled separately.
What is not changing
-
Existing RSVP macros stay on their Confluence pages.
-
Page links and normal page editing are unchanged.
-
Attendees can still submit, update, or remove their own RSVP where allowed.
-
Organizers can still view and export responses.
-
Historical RSVP data is protected during migration instead of being treated as missing just because it is not yet in Forge.
What most users may notice
After a site is using the Forge version, users may see:
-
A refreshed RSVP macro layout.
-
Response statuses such as Attending, Declined, and Waitlisted.
-
Capacity and remaining-spot indicators when configured.
-
Standard or compact response rows, depending on macro settings.
-
Custom RSVP questions when an organizer has configured them.
-
Search and status filters when enabled for the response list.
Organizers may also see additional controls such as CSV export, check-in, Ask Rovo, and Notify. Some organizer-only controls are visible only to page managers, page authors, or Confluence admins.
Historical data protection
Forge does not assume that an old RSVP macro is empty simply because no Forge rows have been imported yet.
During rollout, an existing legacy macro can be in one of these states:
-
Historical responses have already been imported and the macro shows them normally.
-
The macro is known to have had no historical responses and can show the normal empty state.
-
The macro may still have historical responses to verify or import.
When RSVP cannot yet prove that a legacy macro is safe to show as empty, the macro may show a migration or pending-import message instead of a misleading empty response list. In that state, unsafe changes can be blocked until the data is verified or imported.
New Forge-native RSVP macros can work normally even while older legacy macros on the same site are still being checked.
Migration paths
Existing Cloud customers
Existing Cloud customers using the legacy RSVP app are moved through a controlled Connect-to-Forge path.
For reviewed sites, historical RSVP rows and legacy macro information may be imported as part of the staged rollout. If a site or macro needs manual attention, the app or Krosoft Support may direct a Confluence admin to the RSVP Migration Console.
Do not delete and recreate RSVP macros to fix missing historical responses. Contact Krosoft Support first.
New Cloud installs
New Forge installs do not have legacy Cloud RSVP data to import.
Admins normally do not need to use the migration console unless they are importing from Server/Data Center or Krosoft Support asks them to check migration state.
Server/Data Center to Cloud
Server/Data Center to Cloud migration is a separate workflow.
At a high level:
-
Export RSVP migration data from the Server/Data Center app.
-
Open the Cloud RSVP Migration Console.
-
Upload the migration artifact.
-
Review suggested Cloud page mappings.
-
Accept or skip mappings.
-
Import the accepted RSVP data into Forge.
Ambiguous or unresolved page mappings can be skipped and handled later.
What Site Admins may need to do
Most users do not need to take action. A Confluence admin may need to act only when the app or Krosoft Support indicates that migration attention is required.
Admin actions can include:
-
Opening the RSVP Migration Console from Connected Apps or Confluence administration.
-
Initializing Forge RSVP storage for the site.
-
Reviewing migration status for the installation.
-
Importing historical Cloud RSVP data when instructed.
-
Uploading and reviewing Server/Data Center migration files.
-
Confirming that migrated macros show the expected responses.
If a macro shows a pending-import or migration message, review the migration console or contact Krosoft Support before editing affected RSVP pages.
Licensing and migration messages
If the app license is inactive, existing responses remain visible, but new sign-ups, exports, and other mutation actions can be disabled until the license is restored.
If a macro shows a migration message, it means RSVP is protecting historical data or waiting for migration state to be verified. The message should be resolved through the migration console or Krosoft Support rather than by recreating the macro.
Historical data tetention
Historical legacy Cloud RSVP data can be retained for migration during the support window communicated by Krosoft. If you need historical data imported, or if you want retained legacy data removed early, contact Krosoft Support.
When to contact Support
Contact Krosoft Support before editing affected pages if:
-
Historical RSVP responses appear to be missing.
-
A macro shows a pending-import or migration message and you are unsure why.
-
A migration import fails or page mappings look wrong.
-
You need help importing Server/Data Center RSVP data.
-
You need confirmation that a site has completed its RSVP migration.
-
You want retained legacy RSVP data removed early.
For help, contact support@krosoft.nl or visit the Krosoft Support Portal.