This is the documentation for ConfiForms CLOUD app
ConfiForms app on Atlassian marketplace
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 form and views configurations are migrated automatically as they are part of Confluence pages
- ConfiForms migration service (part of Confluence Cloud Migration Assistant) migrates your form's data to cloud, automatically fixing pages, attachments and user references
- ConfiForms migration process also fixes forms' configurations for smart fields and ConfiForms IFTTTs (page references, user/group references)
Important
ConfiForms expects you to migrate the WHOLE instance, as only this way it can fix the usernames to be user accounts, fix user groups, change pages to match the pages on cloud and re-link attachments and fix form configurations (smart fields)
Especially the ones that span across multiple Confluence spaces
ConfiForms relies on Confluence search to find the pages with ConfiForms forms
Make sure you have search index in-sync and up to date. See more Content Index Administration.
Please raise a ticket if something is still un-migrated or broken after the migration and we will try to fix it.
IMPORTANT
Make sure you have updated ConfiForms app to version 2.21.6 or later (and preferably to most recent version available)
See our Release Notes and versions https://marketplace.atlassian.com/apps/1211860/confiforms-data-forms-workflows?hosting=datacenter&tab=versions
Important note. Please read before migration
Migration initiated through CCMA could not complete on certain configurations, see this blocking bug https://jira.atlassian.com/browse/MIG-837
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
https://jira.atlassian.com/browse/MIG-839
https://jira.atlassian.com/browse/MIG-856
https://jira.atlassian.com/browse/MIG-855
Pre-migration
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
ConfiForms relies on the data provided by Confluence search API.
Make sure you have search index in-sync and up to date. See more Content Index Administration.
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
https://YOUR_SERVER/admin/vertuna/confiforms/config.action