Marketplace Apps in AGC: How to Assess Compatibility, Risk and Migration Impact

Marketplace apps can have a major impact on an Atlassian Government Cloud (AGC) migration.

Government teams often depend on apps for reporting, workflow controls, forms, automation, integrations, administration and other business-specific processes. But moving to AGC changes the app discussion.

Not every Data Center or commercial Cloud app is available in AGC. Even when an app is available, its data may not move automatically and government customers are still responsible for reviewing the app’s security posture.

That means the right question is not simply:

“Can we install this app in AGC?”

It is:

“Do we still need it, is it available, can its data move, what depends on it and does it meet our security requirements?”

Start With a Complete App Inventory

The first step is understanding what is already installed.

Large Data Center environments often contain apps added over several years. Some may support critical processes, while others may no longer be used.

For each app, document:

• App name and vendor
• Product where it is used
• Business owner
• Technical owner
• Projects or spaces that depend on it
• Data stored by the app
• Integrations connected to it
• Current usage
• Business impact if it is removed

This helps separate business-critical apps from those that may not need to move into AGC.

Confirm AGC Availability Early

Once the inventory is complete, confirm whether each app is available in Atlassian Government Cloud.

AGC supports a specific set of Marketplace apps and not every Data Center app has a Government Cloud version.

Each app will generally fall into one of three categories:

Available in AGC
Move into security, data and testing review.

Not available in AGC
Consider a replacement, native Atlassian capability or workflow redesign.

No longer needed
Retire it before migration.

This decision should happen early. Building the target environment around an app that cannot run in AGC can create rework later.

Check What App Data Can Actually Move

Availability does not mean data migration is automatic.

Some apps may require a separate migration process, vendor support or manual configuration.

For each critical app, ask:

• Is app data migration supported?
• What data can move?
• What cannot move?
• Is the migration manual or tool-assisted?
• Who performs the migration?
• What validation is required afterward?

This is especially important for apps that store forms, reporting data, workflow information, configuration records, test data or other business-critical content.

App data planning should be part of the main migration plan, not an activity left until the end.

Map Dependencies Before Making Decisions

An app rarely works by itself.

It may be tied to:

• Custom fields
• Workflows
• Automation
• Dashboards
• Reports
• APIs
• External systems
• User permissions

That means removing or replacing an app can affect more than one process.

For each important app, identify where it is used and what depends on it.

A dependency map can reveal that an app used by one project is also referenced by multiple automation rules, reports or integrations.

This is why app assessment should include both technical and business owners.

Put Every App Through a Security Review

Compatibility is only one part of the decision.

Government organizations also need to assess whether the app meets internal security and compliance requirements.

Review areas such as:

• Data residency
• Data egress
• Authentication
• Authorization
• Encryption
• External hosting
• Logging
• Data retention
• Vendor security practices
• Third-party connections

Do not assume that an app is automatically suitable for government use simply because it is available in AGC.

The security review should reflect the agency’s own policies, risk tolerance and data-handling requirements.

Decide Whether to Keep, Replace, Redesign or Retire

Once compatibility, migration, dependencies and security have been reviewed, every app should have a clear decision.

A simple model is:

Keep
The app is available, still needed and meets security requirements.

Replace
Another AGC-compatible app can support the requirement.

Redesign
The process can be supported with native Jira, Jira Service Management, Confluence, automation or a different approach.

Retire
The app no longer supports an active business need.

The goal should not be to recreate the existing Data Center app stack exactly as it is today.

Migration is a good opportunity to reduce unnecessary dependencies.

Test the Full Business Process

An app should not be considered validated just because it installs successfully.

Testing should confirm that the full process still works.

Check:

• App-specific fields
• Workflows
• Historical data
• Permissions
• Automation
• Integrations
• Reports
• User actions

Business users should also participate in testing.

A technical team may confirm the app is running, while a daily user may notice that an approval, field or report behaves differently.

Include Apps in Cutover Planning

Marketplace apps need a defined place in the production cutover plan.

For each app, identify:

• Installation timing
• Configuration sequence
• Data migration timing
• Vendor involvement
• Validation owner
• Dependency order
• Contingency plan

Some apps may need to be configured before migrated projects are tested. Others may require data to move after the main Jira or Confluence migration.

Knowing the order in advance reduces last-minute decisions.

Keep App Governance Going After Migration

The app review should continue after go-live.

Government teams should establish a process for:

• Requesting new apps
• Reviewing security
• Approving business use
• Tracking owners
• Reviewing app usage
• Monitoring vendor changes
• Removing apps that are no longer needed

This keeps the AGC app portfolio manageable as the environment grows.

Why Clovity for AGC App and Migration Planning

Clovity brings direct experience from early Atlassian Government Cloud adoption.

Clovity was the first Atlassian partner to deploy Atlassian Government Cloud and was named Atlassian Partner of the Year 2026 – Government Americas.

Clovity also has its own Marketplace app available for Atlassian Government Cloud, giving our team first-hand experience not only with AGC migration and implementation, but also with the app-readiness, security, compatibility and operational requirements that come with supporting apps in the Government Cloud environment.

That experience gives Clovity a broader view of AGC app planning from both the customer and app-provider side.

Clovity can support:

• App inventory and usage analysis
• AGC compatibility reviews
• Dependency mapping
• App migration planning
• Security review support
• Alternative app evaluation
• Workflow redesign
• Migration testing
• Cutover planning
• Post-migration app governance

Marketplace apps should not be treated as a small item at the end of an AGC migration.

They can affect data, workflows, integrations, security and day-to-day operations. Reviewing them early gives government teams more time to make informed decisions before production migration.

📧 Contact us at info@clovity.com or visit 🌐 www.clovity.com to get started today