Atlassian

Approvals for Confluence: The Ultimate Guide to Moving from Data Center to Cloud

Share:

Moving from Confluence Data Center to Cloud raises some important questions about your existing approval processes.

Will the features your teams rely on still be available? What’s different in Cloud? And what happens to your approval data during migration?

If your organization uses Approvals for Confluence to review documents, collect sign-offs, or manage recurring approvals, you’ll want to understand how those processes will work in your new environment.

This guide covers what you need to know about Approvals for Confluence Cloud, the key differences between the Cloud and DC (Data Centre) versions, and how to prepare for a successful transition.

Why is it time to plan your move to Cloud?

Atlassian has confirmed that Confluence Data Center and its associated Marketplace apps will reach end of life on March 28, 2029. 

After this date, affected Data Center licenses will expire and the products will become read-only.

What if you need more time to migrate?

For organizations that need more time, Atlassian also offers an Extended Maintenance Program. This provides continued paid support beyond March 28, 2029, by exception for approved customers facing specific migration challenges. 

However, it isn’t a general extension of Data Center availability, and participation doesn’t automatically guarantee continued support for third-party Marketplace apps. If your organization expects to remain on Data Center beyond the deadline, speak with Atlassian about your eligibility and confirm app support arrangements with the relevant vendors.

What does moving to Cloud mean for Approvals for Confluence?

Moving to Cloud involves more than transferring your Confluence pages. It’s also an opportunity to review the applications your teams rely on, understand how their functionality compares, and make sure important business processes continue working as expected.

While Atlassian’s Confluence Cloud Migration Assistant (CCMA) can help migrate your Confluence pages and spaces, Approvals for Confluence doesn’t currently support automated app data migration through CCMA.

Instead, AppFox provides a support-assisted process to restore your existing page approval statuses in Cloud. This involves exporting your approval data from Data Center and sending it to our Support team, who will import it into your Cloud environment once your Confluence content has been migrated.

While the process isn’t entirely automated, the good news is that Approvals for Confluence Cloud comes with additional functionality alongside the features you already use.

For more on Atlassian’s announcement and what it means for Marketplace apps, read our guide to the Data Center end-of-life announcement.

Can you continue using your existing approval processes in Cloud?

If your teams already use Approvals for Confluence on Data Center, you won’t need to rethink every approval process simply because you’re moving to Cloud.

Both versions support the core approval activities that help organizations manage document reviews and sign-offs inside Confluence.

Getting documents reviewed and approved

Whether you’re working on a project proposal, internal policy, or technical document, you can continue requesting approvals from designated reviewers directly within Confluence.

With Page Approvals, you can send an entire page for review, select the people responsible for approving it, and track its status.

Approval Teams are also available in both versions, allowing you to group reviewers rather than selecting the same people individually for every request.

Collecting approvals from different specialists

Some documents need input from multiple departments, but not everyone needs to approve the entire document.

For example, an engineering specification might require technical approval from one team and safety approval from another.

Section Approvals let you assign reviewers to individual sections of a Confluence page, so each person can focus on the content they’re responsible for.

This functionality is available in both Data Center and Cloud, making it possible to continue managing more complex document reviews without splitting content into separate pages.

Learn more about using Section Approvals in Confluence.

Keeping approved documents up to date

Getting a document approved isn’t always the end of the process.

Policies, procedures, and other controlled documents may need periodic review. And when approved content changes, the original sign-off may no longer be valid.

Approvals for Confluence supports expiry and reapproval processes in both environments, helping teams make sure documents are reviewed again when required.

You can configure approvals to expire after a defined period or when content is edited, depending on the approval settings.

Keeping track of pending approvals

For managers and reviewers handling multiple requests, being able to find outstanding approvals is essential.

Both versions provide ways to locate approvals awaiting action, helping teams stay on top of requests without searching through individual Confluence pages.

The main takeaway? Many of the approval processes you already use in Data Center can continue in Cloud.

The bigger differences become apparent when you look at approval history, visibility, and administration.

What happens to your existing approvals when you migrate?

When you migrate your Confluence pages to Cloud, the associated Approvals for Confluence data doesn’t automatically move with them.

That’s because Approvals for Confluence doesn’t have an automated migration path through Atlassian’s Confluence Cloud Migration Assistant.

However, AppFox can help you restore the current page approval statuses from your Data Center instance.

Before migration, you’ll need to export your page approval data and send it to AppFox Support. Once your Confluence content has been migrated and Approvals for Confluence Cloud is configured, our team can import the exported data into the Cloud app’s database.

This means your migrated pages can retain their existing approval statuses, rather than requiring teams to start every approval again from scratch.

It’s important to distinguish restoring current approval statuses from migrating complete approval histories. The standard process focuses on current page approval statuses and doesn’t automatically transfer historical approval records.

What’s different in Approvals for Confluence Cloud?

Although the two versions share much of their core functionality, Cloud offers some additional capabilities that may be particularly valuable for teams managing large volumes of documents or needing greater visibility over approval decisions.

There are also a few differences you’ll need to plan for.

More visibility into approval history

One of the notable differences is how approval history is managed.

The Cloud version provides Page Approval History and Section Approval History, allowing users to review previous approval activity.

Rather than relying solely on the current approval status, users can inspect recorded decisions, dates, comments, and changes associated with an approval.

This can be especially useful for document controllers, quality managers, and teams that need to demonstrate that the right people reviewed and approved content.

For example, when reviewing a controlled procedure, a quality manager may need to establish when it was approved, who made the decision, and whether subsequent changes triggered another review.

Cloud’s approval history provides a record that can help answer those questions. Approval history can also be exported to CSV for further review or recordkeeping.

Explore the documentation for Page Approval History and Section Approval History.

Greater oversight of approvals across Confluence

Another useful difference is the ability to search beyond your own approvals.

In Data Center, the feature comparison identifies searching your own approvals as supported, but not searching other people’s approvals.

Cloud provides broader approval search functionality, allowing users to find approval requests across their Confluence environment.

Search filters help narrow results by factors such as approval type, status, space, and expiry.

For administrators or document owners responsible for overseeing reviews across multiple teams, this makes it easier to identify outstanding approvals and understand where attention is needed.

Cloud also includes an Approvals Dashboard, bringing useful approval information together, including pending requests and approvals approaching expiry.

Continued improvements to the Cloud experience

Approvals for Confluence Cloud has also received updates to support how teams work in Confluence.

Recent releases have introduced page approval titles and descriptions, improvements to the section approval experience, and support for approvals in Confluence live docs.

For existing customers, these changes can provide additional context around approval requests and support newer ways of creating and reviewing Confluence content.

You can explore the latest functionality in the Approvals for Confluence Cloud documentation.

One difference to prepare for: Custom approval terminology

Not every Data Center setting has a direct equivalent in Cloud.

In Data Center, administrators can customize approval status terminology. This isn’t currently supported in the Cloud version.

If your organization has changed the default approval status names to match internal processes, those custom names won’t be retained when you move to Cloud. Instead, the Cloud version uses its standard terminology.

For most teams, this may be a small adjustment. However, organizations using specific terminology in internal procedures or training materials should account for the change.

Review the language used in your existing approval processes and make sure users understand the standard Cloud statuses before the transition.

Approvals for Confluence: Cloud vs Data Center at a glance

While there are some differences between the two versions, many of the core features remain the same. Here’s how the main capabilities compare:

FeatureCloudData Center
Section ApprovalsYesYes
Section Approval HistoryYesNo
Page ApprovalsYesYes
Page Approval HistoryYesNo
TeamsYesYes
Email notificationsYesYes
Page templates (macro)YesYes
Search your own approvalsYesYes
Search other approvalsYesNo
Customize terminologyNoYes

The biggest differences are in approval history and visibility. Cloud offers additional ways to review previous decisions and find approvals across Confluence, while Data Center provides greater flexibility to customize approval terminology.

The core page and section approval functionality remains available in both versions, helping teams continue managing familiar review and sign-off processes after migration.

Overall, Cloud preserves the main approval experience while providing additional visibility and history capabilities. Understanding these differences early will help you decide which settings need attention and what to communicate to your teams.

AppFox provides a migration process that allows administrators to export their existing page approval information and request its restoration once the Cloud environment is ready.

This is particularly important for organizations working with controlled documentation, where the status of an approved document may influence whether it can be relied upon or needs further review.

It’s also important to distinguish restoring approval statuses from transferring complete historical approval records. The documented migration process focuses on page approval statuses. If your organization needs to retain historical decision information or migrate section approvals, discuss those requirements with AppFox Support before proceeding.

The sooner you identify which approval information matters to your organization, the easier it will be to plan the migration around those requirements.

How to migrate Approvals for Confluence from Data Center to Cloud

Migrating Approvals for Confluence is best approached as part of your wider Confluence Cloud migration, rather than as an entirely separate project.

The AppFox migration process can be understood in three main phases.

Phase 1: Prepare and export your approval data

Before migrating, review your existing Approvals for Confluence setup, including approval statuses, assigned reviewers, and any space-specific settings.

You’ll also need to export your current page approval data from Data Center. This creates the file AppFox will use to restore approval statuses in Cloud.

The migration guide explains the available export methods, including the REST API approach recommended for larger instances.

If you use Section Approvals or have specific historical recordkeeping requirements, contact AppFox Support before migrating to discuss the available options.

Phase 2: Migrate your Confluence content

Next, migrate your Confluence pages and spaces to Cloud using your organization’s chosen migration method, such as Atlassian’s Confluence Cloud Migration Assistant.

Remember that CCMA migrates your Confluence content, but it doesn’t automatically migrate Approvals for Confluence data.

During the process, you may see a message stating that Approvals for Confluence doesn’t have an automated migration path. This is expected and means that your approval statuses must be restored separately with AppFox Support.

Phase 3: Restore your approvals in Cloud

Once your Confluence pages have been migrated, install and configure Approvals for Confluence Cloud.

Next, raise a support request with AppFox and provide the page approval data you exported from Data Center.

Our team will use this information to restore the current approval statuses to your migrated pages in Cloud.

Once the restoration is complete, check a sample of pages against your exported records to confirm that the correct approval statuses are displayed. You should also test new approval requests and make sure your teams understand any differences between the versions.

Getting the most from Approvals after migration

Once your approval processes are working in Cloud, there’s an opportunity to review how your organization manages approvals more broadly.

Migration doesn’t have to mean recreating every existing process exactly as it was.

For example, if document owners previously struggled to track review requests across several teams, Cloud’s dashboard and approval search capabilities may give them a better way to monitor outstanding work.

Similarly, teams managing controlled documents can explore how approval history and expiry settings support their ongoing review requirements.

It’s worth considering three areas as part of your post-migration review: whether the right people are responsible for approvals, whether approved documents are reviewed often enough, and whether teams know how to find the approval information they need.

Make sure users know what’s changed

Even where functionality is familiar, the interface, available settings, and terminology may be different. A short introduction for document owners and approvers can help avoid confusion after migration.

You can direct users to the Approvals for Confluence Cloud User Guide for more information on managing their approvals.

And as your teams settle into Cloud, reviewing how approvals are being used can help you identify where processes could be made clearer or more consistent.

Frequently asked questions

Approvals for Confluence doesn’t currently support automated app data migration through Atlassian’s Confluence Cloud Migration Assistant (CCMA).

You can use CCMA to migrate your Confluence content, but restoring the current approval statuses on your pages requires a separate process.

Export your page approval data from Data Center before migrating, then send it to AppFox Support. Our team can import the data to restore the current page approval statuses in Cloud.

The standard AppFox migration guide covers page approval statuses, not section approvals.

If your organization uses section approvals and needs to migrate their associated data, contact AppFox Support to discuss your requirements and the available options before proceeding.

You shouldn’t assume that your existing approval history will transfer automatically.

The documented migration process focuses on restoring page approval statuses. Organizations with specific historical recordkeeping requirements should confirm what can be retained and restored with AppFox Support before migrating.

No. Custom approval status terminology available in Data Center isn’t currently supported in Approvals for Confluence Cloud.

If your organization uses customized labels, you’ll need to prepare users for the standard Cloud terminology and update relevant internal documentation.

Contact the AppFox Support team.

The migration documentation recommends getting in touch if your export doesn’t cover everything you need or you’re unable to generate the necessary file. The team can help you investigate the available options.

Ready to make the move to Cloud?

Moving from Data Center to Cloud is an important change, but it doesn’t mean leaving your established document approval processes behind.

With Approvals for Confluence Cloud, you can continue managing document reviews and sign-offs inside Confluence, while taking advantage of additional approval history and visibility capabilities.

The key is to understand the differences, preserve the approval information you need, and plan the migration process before making the move.

If you’re preparing for a migration, explore our detailed migration guide or contact AppFox Support to discuss your requirements.

And if you’d like to see how the Cloud version works before migrating, you can book a demo of Approvals for Confluence.

In this article:
Picture of Kelly Newcomb
Kelly Newcomb
Kelly Newcomb has spent nearly 15 years launching B2B software across technology and regulated industries. Her articles combine insights from working directly with customers and deep product expertise to help users get the most out of AppFox products.