Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

Since ConfiForms version 2.20 we now support automatic migration of your forms and data from server to cloud

Please see Differences between ConfiForms server/data center and ConfiForms cloud, as the functionality of cloud version differs from server/data center version

What to expect

  • ConfiForms configuration is migrated automatically as it is part of Confluence pages
  • ConfiForms (part of Confluence Cloud Migration Assistant) migrates your form's data to cloud, automatically fixing the page, attachments and user references
  • ConfiForms migration process also fixes forms' configurations for smart fields and ConfiForms IFTTTs (page references, user/group references)

Please raise a ticket if something is still un-migrated or broken after the migration and we will try to fix it. 

ConfiForms (FormView) Registrations Control
pageTitleCONFIFORMS:ConfiForms Backlog
registrationButtonLabelGet support


Make sure you have updated ConfiForms app to version 2.21.6 or later

Recommended is version to use is ALWAYS the latest one available - Release Notes,

titleImportant note. Please read before migration

Migration initiated through CCMA could not complete on certain configurations, see this blocking bug

serverAtlassian JIRA

We are waiting for Atlassian to get it fixed / implemented

While this is getting fixed, the workaround would be as follows: you go through the CCMA migration and then go to your cloud instance and make sure all the pages that have ConfiForms Form Definition macros are accessible to ConfiForms app system user (for example it is accessible to confluence-users group) and then re-run the migration for ConfiForms as shown in step #6 below

We have been notified by another bug in CCMA that affects us

serverAtlassian JIRA

serverAtlassian JIRA

serverAtlassian JIRA


Make sure you read and understand the differences and accept that the plugin functionality on cloud could not be as versatile as on server/data center. And this is mainly due to differences in hosting platforms and APIs we are allowed to use

Differences between ConfiForms server/data center and ConfiForms cloud

Also, please run the  pre-check report on your Confluence server to understand what forms and pages will have differences in functionality

This is available in the Confluence administration → ConfiForms configuration → Cloud Migration

Direct link

Code Block

Migration process 

1. You need to install ConfiForms on cloud instance and generate API token (ConfiForms app configuration - accessible through Confluence administration)

2. Register your cloud instance to receive migration events

3. This token needs to be registered in ConfiForms server app (ConfiForms app configuration, Manage apps → ConfiForms → Configure)

4. Make sure ConfiForms app user is set to be administrator of your Confluence instance for the time of migration at least 

5. Start your migration process using Confluence Cloud Migration Assistant (CCMA). Follow documentation on and dont forget to select ConfiForms as required in Cloud when you assess your installed apps (

More on Atlassian CCMA


As CCMA is currently in beta you need to enable "dark feature" as per documentation on

Screenshot below:

6. ConfiForms migration process will start automatically by CCMA. But you can always re-run it if necessary through the ConfiForms app configuration / migration section


Your Confluence server must have access to

At the moment we have the following IP addresses


Confluence search index

ConfiForms relies on the data provided by Confluence search API. Make sure you have it in sync and up to date. See more Content Index Administration.

Migration compatibility report

Migration compatibility report might be incomplete, as ConfiForms is very flexible at what you can do and how forms could be built and configured.

At the moment we dont support configurations in user macros (which is perfectly supported by the plugin itself). This is work in progress.

Also expressions using virtual functions via [entry.field_name] notations which are not used within macro parameters, but, for example, in macro body (PlainViews or ListViews/CleanViews) are not analyzed / processed.

Current issues


There is a blocking issue with space permissions for the automatic migration path. Atlassian is aware of that and trying to come up with a solution.

We offer a way to "re-run" the migration after it has been ran by CCMA by starting a long running task. This allows you to fix the possible permissions issues and allow ConfiForms app system user to access and  update the pages it needs to update (to fix possible configuration issues with smart fields, to move the data from server to cloud)

How to give permissions to ConfiForms app user

ConfiForms full system user name is 

Code Block

ConfiForms App user in cloud has a new name

Shown then as a normal user in the restrictions