What Happens to Confluence Marketplace Apps After Data Center End of Life
Confluence Data Center's confirmed end of life in March 2029 does not only affect your Confluence installation — it terminates every Data Center Marketplace app alongside it. All Data Center Marketplace app licenses expire on the same date as the underlying platform license: March 28, 2029. There is no grace period, no extended maintenance window, and no mechanism for app vendors to continue supporting Data Center independently. If your teams rely on third-party apps for diagramming, workflow automation, reporting, or structured data management, the end of Data Center is simultaneously the end of those tools. Planning for this requires a systematic inventory, an honest assessment of what functionality you actually use, and a clear understanding of your options — including the XWiki extension ecosystem that provides equivalent capabilities without per-user licensing or vendor lock-in.
The Marketplace App Timeline
Atlassian has structured the Marketplace wind-down in stages that mirror the broader Data Center end-of-life timeline. Understanding each stage helps you anticipate when specific disruptions will begin.
December 16, 2025: No New Data Center App Submissions
As of this date, the Atlassian Marketplace no longer accepts new app listings for the Data Center platform. The ecosystem is frozen — no new vendors will enter the Data Center app market. If a workflow gap exists today that no current Marketplace app addresses, no new app will appear to fill it. This signals to the developer community that building for Data Center is no longer a viable investment, and the effects ripple outward from this point.
March 30, 2026: Marketplace Ecosystem Contraction Begins
When new Data Center subscriptions close to new customers, the addressable market for Data Center app vendors shrinks permanently. App vendors who maintained both Cloud and Data Center versions of their products will increasingly prioritize their Cloud offerings. Bug fixes and feature development for Data Center versions will slow, and some vendors will announce early end-of-support dates for their Data Center apps well before the 2029 deadline. This is not speculation — it is the predictable economic response to a shrinking customer base with a confirmed expiration date.
2027–2028: Accelerating App Abandonment
As the Data Center deadline approaches, expect an increasing number of app vendors to formally end support for their Data Center products. Vendors with limited engineering resources will consolidate on their Cloud versions. Apps that are maintained by small teams or individual developers — which describes a significant portion of the Marketplace — may simply stop receiving updates. Security vulnerabilities discovered in these apps during this period may go unpatched, creating risk that compounds on top of the platform's own declining support.
March 28, 2029: Total Marketplace Shutdown
Every Data Center Marketplace app license expires on this date. Apps that were still functioning will stop. There is no mechanism for individual app vendors to extend their Data Center licenses independently — the licensing infrastructure itself is being retired. This is not a gradual sunset; it is a cliff edge where every third-party tool stops working on the same day.
Why This Matters More Than You Think
Most Confluence Data Center deployments are not running on the base product alone. A typical enterprise Confluence instance has between five and twenty Marketplace apps installed, and some have significantly more. These apps often provide functionality that teams consider essential to their daily work — functionality that is deeply embedded in existing pages, templates, and workflows.
Content Dependency
Many Marketplace apps store their own content types within Confluence pages. Diagramming tools embed diagram data. Structured data apps create database-like records. Workflow engines attach approval states and transition histories. When these apps stop working, the content they created does not simply disappear — it becomes inaccessible or renders as raw macro placeholders. Pages that looked polished and functional become broken layouts with missing components.
Workflow Dependency
Apps that automate processes — approval workflows, page review cycles, notification rules, automated publishing — will cease functioning entirely. Teams that built operational processes around these tools will need to rebuild those processes from scratch on whatever platform they migrate to. The earlier you identify these dependencies, the more time you have to plan equivalent workflows on your target platform.
Integration Dependency
Some Marketplace apps serve as bridges between Confluence and other systems: Jira integration enhancers, CI/CD pipeline connectors, CRM data pullers, and monitoring dashboard widgets. Losing these apps does not just affect Confluence — it breaks connections to other parts of your technology stack.
How to Audit Your Marketplace App Dependencies
A thorough app audit is a prerequisite for any migration plan. Rushing this step leads to nasty surprises during or after migration when teams discover that functionality they relied on daily has no equivalent in the new environment.
Step 1: Generate a Complete App Inventory
In Confluence Data Center, navigate to Administration > Manage apps to see every installed app. For each app, document the app name and vendor, the version installed, whether it is actively licensed or expired, and what functionality it provides. Do not skip apps that appear unused — they may be generating content types or macros that are embedded in existing pages even if no one actively configures the app itself.
Step 2: Identify Content-Generating Apps
Search your Confluence content for macros provided by each app. The easiest method is to use the Confluence REST API to search for macro names across all spaces. Apps that generate their own macros are the highest-risk category because their content will break visually when the app is removed. Common examples include draw.io, Gliffy, Lucidchart, Balsamiq, Table Filter, Scroll Versions, and Comala Document Management.
Step 3: Assess Business Criticality
For each app, determine how many pages use it, which teams depend on it, and what would happen if it disappeared tomorrow. Categorize each app as critical (teams cannot work without it), important (significant inconvenience if lost), or nice-to-have (minimal impact if removed). This categorization drives your migration priority and determines where you need to invest time finding equivalent functionality on your target platform.
Step 4: Research Equivalents on Your Target Platform
Whether you are migrating to Atlassian Cloud or to an open-source alternative like XWiki, you need to map each critical and important app to an equivalent on the target platform. Not every app will have a direct one-to-one equivalent, but most core functionality categories are well-served on mature platforms.
Confluence Marketplace Apps and Their XWiki Equivalents
One of the most common questions organizations ask when evaluating migration from Confluence to XWiki is whether the Marketplace apps they depend on have equivalents in the XWiki ecosystem. XWiki's extension repository contains over 900 extensions, many of which directly address the same use cases as popular Confluence Marketplace apps — without per-user licensing fees.
Diagramming
Confluence apps: draw.io (Diagrams for Confluence), Gliffy, Lucidchart, Creately.
XWiki equivalent: The draw.io integration for XWiki embeds the same open-source draw.io/diagrams.net editor directly into wiki pages. Diagrams are stored as editable SVG within the page, and the editing experience is identical to what draw.io users already know. There is no per-user licensing — the extension is free. For organizations currently paying for Gliffy or Lucidchart subscriptions on top of their Confluence license, this eliminates an entire cost layer.
Workflow and Approval
Confluence apps: Comala Document Management, ServiceRocket Workflows, Scroll Versions, Ad Hoc Workflows.
XWiki equivalent: XWiki includes a built-in document lifecycle and publication workflow system. Pages can move through draft, review, and published states with configurable approval chains. The XWiki Workflow Publication extension supports multi-step approval processes with role-based transitions. For document versioning and controlled publication, XWiki's native versioning tracks every change with full diff history, and the publication workflow ensures that only approved content becomes visible to the intended audience.
Structured Data and Reporting
Confluence apps: Table Filter, Pivot Table, SQL Connector, Advanced Tables, Metadata for Confluence.
XWiki equivalent: XWiki's structured data capabilities are built into the platform rather than bolted on as third-party apps. The App Within Minutes feature allows non-technical users to create custom data applications — essentially database-backed forms with automatic list views — without writing code. LiveTable provides dynamic, sortable, filterable data views. For advanced reporting, XWiki's scripting engine (Velocity, Groovy, or Python) can query structured data and generate custom reports directly within wiki pages.
Content Organization and Navigation
Confluence apps: Scroll Viewport, Refined for Confluence, MultiExcerpt, Content Formatting Macros, Tabs for Confluence.
XWiki equivalent: XWiki supports true hierarchical page organization with unlimited nesting depth — a structural advantage over Confluence's flat page tree. The skinning system allows custom navigation, branded portals, and content-specific layouts without third-party tools. Tab and accordion layouts, content inclusion (similar to MultiExcerpt), and page templating are all native XWiki capabilities that require no extensions.
PDF and Document Export
Confluence apps: Scroll PDF Exporter, Scroll Word Exporter, PDF Export Plugin.
XWiki equivalent: XWiki includes built-in PDF export with customizable templates and styling. For organizations that need professional-quality document generation from wiki content — compliance documentation, SOPs, training manuals — the PDF export engine supports custom headers, footers, page layouts, and CSS styling. Multi-page export allows generating complete manuals from page hierarchies in a single operation.
LDAP, SSO, and Authentication
Confluence apps: Atlassian Access (required for SAML SSO in Cloud), various LDAP management tools, re:solution SAML SSO.
XWiki equivalent: XWiki includes native LDAP, Active Directory, SAML 2.0, and OpenID Connect authentication at no additional cost. There is no equivalent of Atlassian Access — you do not need to pay extra for enterprise SSO. Group synchronization, automatic user provisioning, and multi-factor authentication integration work out of the box. We cover the full configuration process in our XWiki LDAP and SSO guide.
Multilingual Content
Confluence apps: Scroll Translations for Confluence, Language Macros.
XWiki equivalent: XWiki supports over 40 languages natively, with built-in page translation management. Each page can have translations in multiple languages, and users see content in their preferred language automatically. Translation workflow support is included — no third-party app required.
Monitoring and Administration
Confluence apps: Better Content Archiving, Space Admin, Usage Statistics.
XWiki equivalent: XWiki provides built-in administration panels for space management, user activity tracking, and content statistics. For advanced monitoring, XWiki integrates with Prometheus and Grafana through JMX metrics export, providing real-time dashboards for application health, user activity, and resource utilization.
What About Apps With No Direct Equivalent?
Not every Confluence Marketplace app has a one-to-one counterpart in XWiki's ecosystem. For niche or highly specialized apps, you have several options. First, assess whether the functionality is truly needed — app audits frequently reveal that some installed apps are used by only a handful of people or not at all. Second, check whether XWiki's scripting engine can replicate the functionality. XWiki supports Velocity, Groovy, and Python scripting within wiki pages, which allows building custom functionality without developing a formal extension. Third, consider whether the underlying need can be met by a different integration pattern — for example, connecting XWiki to an external tool via its REST API rather than embedding the functionality within the wiki itself.
For organizations with genuinely unique app dependencies, XWiki's open-source nature means that custom extensions can be developed without vendor approval or Marketplace gatekeeping. The extension development framework is well-documented, and the XWiki community actively supports extension developers.
The Migration Path for App-Dependent Content
When migrating from Confluence to XWiki, content generated by Marketplace apps requires special attention during the migration process.
Macro Conversion
The XWiki Confluence Migrator Pro includes 31 bridge macros that automatically convert the most common Confluence macros to their XWiki equivalents. Standard macros — Info/Warning panels, Code blocks, Table of Contents, Expand/Collapse sections — convert seamlessly. Custom macros from Marketplace apps are preserved during migration but flagged for manual review. The migration report identifies every macro instance that needs attention, so nothing is silently lost.
Diagram Migration
draw.io diagrams created in Confluence can be exported as XML and imported directly into XWiki's draw.io extension. The diagram data is fully preserved — shapes, connections, styling, and layers all transfer intact. Gliffy diagrams require an additional step: export from Gliffy to draw.io format first, then import into XWiki.
Structured Data Migration
Content stored in structured data apps (table-based or database-style apps) typically needs to be exported as CSV or JSON and re-imported into XWiki's structured data framework. The App Within Minutes feature in XWiki can recreate the data schema, and the data itself can be imported through XWiki's REST API or scripting engine. This is one area where pre-migration planning pays dividends — understanding your data structures before migration prevents re-work.
Start Your App Audit Now
The Confluence Marketplace app cliff is not a separate problem from the Data Center end of life — it is the same problem, amplified. Every day that passes without an app inventory is a day closer to discovering critical dependencies under deadline pressure. Start your audit now, while you have time to evaluate alternatives properly, test migrations thoroughly, and plan training for your teams on replacement tools.
If you are evaluating XWiki as your post-Confluence platform, MassiveGRID's managed XWiki hosting provides a ready-to-use environment where you can test extension compatibility, run migration trials, and verify that your Marketplace app equivalents work as expected — all on EU-hosted infrastructure with full data sovereignty. Our step-by-step migration guide walks through the complete process from audit to verification.