Migration FAQs

Q. What versions of Confluence Data Center and Forms for Confluence should we be on before migrating to Cloud?

A.  You can migrate from either Confluence 9 or Confluence 10. You should use the version of Confluence for Forms that matches. These are our current recommendations. 

Q. Do we need to upgrade Confluence before beginning a migration?

A.  It depends what version of Confluence you are currently on. Please see the table above for our recommended Confluence versions and the matched version of Forms for Confluence.

Q. Which version of the CCMA should I use?

A. We recommend using the latest version of the CCMA.

Q. Does using the recommended versions of Confluence DC, Forms for Confluence and the latest version of the CCMA guarantee a successful migration with no errors?

A. Migrations are not simple and the results often depend on the exact contents of each instance. Having the recommended versions alone does not guarantee a migration will succeed without errors, however it will give you the best results. While having compatible versions is a prerequisite, there are several known limitations and potential issues that can still arise even with everything correctly versioned.

Q. What is the recommended process for migrating Forms for Confluence from DC to Cloud?

A.  We recommend performing the following steps. 

1. Before you migrate.

   • Make sure you have a Confluence Cloud site set up.

   • Install Forms for Confluence Cloud on that site from the Atlassian Marketplace.

     • If you did this some time ago, make sure you are on the latest version before starting.

   • Ensure Forms for Confluence on Data Center on one of the recommended versions.

   • Identify which spaces contain forms and any important response data, and clean up any test/obsolete forms where possible.

   • Set all form destinations to Internal Database.

2. Run a test migration.

   • Use CCMA to run a test migration of a few representative spaces that contain forms.

   • After the test completes, verify on Cloud that:

     • Forms appear correctly on the migrated pages.

     • Forms can be edited and submitted.

     • Response data has migrated as expected (where supported).

3. Production migration.

   • Exporting your responses (e.g. to CSV) from Data Center before the final migration. This ensures you have all your data.

   • Repeat the steps you used for your test migration for your production instance.

   • There may be some cases where certain legacy or unusual configurations don’t migrate perfectly and need manual adjustment or recreation on Cloud. 

Q. Is there anything we can do to prepare for the migration?

A. We have the following recommendations on preparing your instance:

• Set all form destinations to Internal Database.

  • Navigate to  User Management → Forms for Confluence.
    Change any form types that are not set to "Internal Database" - other destination types will not be migrated to Cloud.

• Remove unsupported fields and nested non-form macros.

Some forms will work as expected after migration, while others will need further editing in Cloud. Doing the cleanup in DC beforehand significantly reduces the effort required after migration.

Q. Is there a pre-migration checklist?

A. The following is a checklist you can use to make sure you are ready for your migration.

• Set all form types to Internal Database (single destination).

• Remove all non-forms macros from inside your forms macros.

• Remove or replace unsupported form fields.

• Ensure you are using the recommended versions of Confluence and Forms for Confluence.
  

  Confluence Version	Confluence 9.0.0 - 9.5.4	Any Confluence 10 version
  Forms for Confluence  Version	9.0.10	10.0.0 or later

• Ensure the CCMA is on the latest versions.

• Perform a test migration to know what to expect. Forms that worked in DC often need post-migration editing in Cloud.

Q.  We’re migrating later this year—can we get a short-term DC renewal / promo code to bridge the gap?

A. Promo codes and short-term DC renewal discounts can't be issued through Adaptavist's product support. These requests need to go through Atlassian's Partner Service Portal directly. You can submit the request through the Atlassian Partner Service Portal.

Q. We tried a test migration and it failed. What troubleshooting steps can we take?

A. There are a few common issues that cause the migration of Forms to fail. To identify the issue start with a single failing page or space. Ensure that you have:

• Set all form types to Internal Database (single destination).

• Remove all non-forms macros from inside your forms macros.

• Remove or replace unsupported form fields.

Once you have checked these items, try a smaller migration of just the chosen page or space.

If the smaller migration still fails you should raise a support ticket so we can help identify the problem. To help us assist you quickly please attach the CCMA logs, DC support zip, and the page storage formats to the ticket.

Q. Our migration didn't go as planned. How can we tell if the issue is with Atlassian/CCMA or Forms for Confluence?

A. Migrations can be complicated and there are many points at which issues can arise. 

These are signs the problem sits with Atlassian's migration infrastructure:

• The CCMA skips Forms entirely despite being marked Needed in cloud.

• The CCMA assessment screen has the following error: No automated migration path

• Re-run option greyed out after the 12-day window - this is a CCMA-imposed limit.

• Migration stuck at 0% or hanging indefinitely with no Forms-specific errors in the logs.

• All apps failing, not just Forms suggests a broader CCMA or Confluence issue.

• Page conversion prompt - when Confluence forces a page conversion from legacy to V2 editor and this corrupts the form structure, the root cause is the Atlassian editor migration, not Forms itself.

For these issues you should raise a ticket with Atlassian Support.

Q. When should we open a ticket with Atlassian vs Forms for Confluence (or both)?

A. Open a ticket with us if the issue is with app-specific functionality. eg.  Forms data not importing, forms appearing empty, app errors or configuration problems.

Open with Atlassian when the root cause points to Atlassian platform infrastructure. eg. APIs returning incorrect results, CCMA bugs, Confluence Cloud platform issues.

Open both when the problem sits at the boundary between the app and the platform, this is very common with migrations.