Ready to plan your move?
I’m Abi, Kolekti’s Senior Customer Success Manager.
Whether you're early in your Cloud migration planning or already underway, I’m here to help you transition your Forms workflows with confidence.
Migrate with Forms
When you move from Data Center to Cloud, the structured processes your teams depend on - requests, approvals, feedback, intake - need to come with you. Forms for Confluence is built to make that happen.
Moving to Confluence Cloud is a significant change, and if your teams rely on forms to run everyday workflows, it's natural to wonder what happens to those processes during the transition. That's exactly why this page exists: to help you understand what the move means for your Forms workflows and give you confidence that nothing gets left behind.
Looking for tailored advice for your organisation? Our team will be delighted to help you - please get in touch.
Looking for tailored advice for your organisation? Our team will be delighted to help you - please get in touch.
Migrating Forms? What you need to know
Atlassian is ending support for Data Center products, which means the platform your Forms workflows run on today has a limited future. Now is the time to start planning your move to Cloud.
Waiting doesn't make migration easier. The longer workflows stay on an unsupported platform, the greater the risk of disruption when you do eventually move. Teams that plan early have more time to test, transition smoothly, and avoid last-minute pressure.
The good news: Forms for Confluence is ready for Cloud, and your workflows can come with you. Keep reading to understand what the move looks like and how to get started.
The good news: Forms is ready for Cloud
Migration can feel uncertain, especially when critical workflows are involved. Here's what makes Forms for Confluence Cloud a safe and supported move.
Built on Forge
Forms for Confluence Cloud is built on Atlassian's Forge platform, the foundation Atlassian is investing in for the long term. You're adopting a product that's aligned with where the platform is going, not one that's being left behind.
Enterprise-grade environment
Confluence Cloud brings the security, compliance, and scalability your organisation expects. Forms is designed to work within that environment, so your structured workflows operate with the same rigour your teams are used to.
Your forms carry over
The processes you've built in Forms - request handling, approval chains, structured feedback - won't disappear. They continue to work in Cloud, giving your teams continuity from day one with minimal disruption.
We're here to help
Many customers have already successfully migrated Forms from Data Center to Cloud, but if you need guidance:
Explore documentation and migration FAQs
Reach out to us for support and best practices
How teams are already using Forms in Cloud
Give teams a consistent way to submit service requests, change approvals, and access requests — all captured in Confluence, where they can be tracked and acted on.
Bring structure to budget requests, expense approvals, and cross-team financial workflows. Every submission follows the same format, every approval has a clear trail.
Standardise onboarding intake, internal feedback collection, and process requests across your people team. Reduce back-and-forth, capture the right information the first time.
If a team needs to collect structured information and act on it - whether that's project intake, event requests, or operational reporting - Forms gives them a repeatable, reliable way to do it.
Give teams a consistent way to submit service requests, change approvals, and access requests — all captured in Confluence, where they can be tracked and acted on.
Bring structure to budget requests, expense approvals, and cross-team financial workflows. Every submission follows the same format, every approval has a clear trail.
Standardise onboarding intake, internal feedback collection, and process requests across your people team. Reduce back-and-forth, capture the right information the first time.
If a team needs to collect structured information and act on it - whether that's project intake, event requests, or operational reporting - Forms gives them a repeatable, reliable way to do it.
Give teams a consistent way to submit service requests, change approvals, and access requests — all captured in Confluence, where they can be tracked and acted on.
Bring structure to budget requests, expense approvals, and cross-team financial workflows. Every submission follows the same format, every approval has a clear trail.
Standardise onboarding intake, internal feedback collection, and process requests across your people team. Reduce back-and-forth, capture the right information the first time.
If a team needs to collect structured information and act on it - whether that's project intake, event requests, or operational reporting - Forms gives them a repeatable, reliable way to do it.
What’s better in Cloud?
A smoother, better user experience
Forms for Confluence Cloud is designed to be intuitive from the start. Teams can pick it up quickly without extensive training. Built-in guidance, onboarding resources, and on-demand support are available in-app, so help is always close at hand when you need it.
Let more teams own their workflows
In Data Center, workflow creation often depends on a small number of specialists or admins. Cloud makes it easier for teams across HR, Finance, IT, and operations to build and manage their own structured processes — reducing the bottleneck on admins and speeding up workflows.
Feature comparison
Forms for Confluence Cloud | Forms for Confluence DC | |
|---|---|---|
A variety of form question fields | ✅ | ✅ |
Email notifications | ✅ | ✅ |
Anonymous responses option | ✅ | ✅ |
In-page response tables and visualisations | ✅ | ⚠️ Basic visualisations only |
Embedded multi-form visualisation | ✅ | ❌ |
Polls | ✅ | ❌ |
Quizzes | ✅ | ❌ |
Jira task forms (Create Jira work items from form submissions) | ✅ | ⚠️ Requires ScriptRunner for Confluence |
Improved user experience | ✅ | ❌ |
Enterprise-ready security | ✅ | ❌ |
Live in-app support | ✅ | ❌ |
How to migrate Forms for Confluence
Not sure where to start? We’ve put together some pointers to support you.
Your four-phase migration approach
Click a card to learn what you need to do at each step of the journey.
Your cheatsheet to migrating Forms
Get all the foundational information you need on one page. Download your free guide to get started and migrate with confidence.
I’m Abi, Kolekti’s Senior Customer Success Manager.
FAQs
Do we need to update Confluence before beginning a migration?
It depends on what version of Confluence you’re currently on. If you’re not on Confluence 9.0.0 - 9.5.4 or any Confluence 10 version, we recommend you update your Confluence instance.
Is there a pre-migration checklist?
The following checklist will help ensure you’re ready for your migration:
- Set all form types to Internal Database (single destination).
- Remove all non-form 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: Confluence 9.0.0 - 9.5.4, or any Confluence 10 version
- Forms: Forms for Confluence 9.0.10, or Forms for Confluence 10.0.00 and above
- 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.
Should we open a ticket with Atlassian or Forms for Confluence?
If the issue is with app-specific functionality, e.g., forms data isn’t importing, forms appear empty, or there are configuration problems, open a ticket with us.
When the root cause points to the Atlassian platform infrastructure, e.g., APIs are returning incorrect results, or there are bugs with CCMA, open a ticket with Atlassian.
If the problem sits at the boundary between our app and the platform, open a ticket with Atlassian and us.
Need help with migration?
Planning your DC to Cloud migration? Let's talk about your Forms workflows.