A team wants to move its PostgreSQL database from 11 to 16. They open the Adobe Campaign compatibility matrix, read "PostgreSQL 11 to 17", and sign the work off in a technical committee. Six weeks later the application does not restart after the switchover, and support replies that the configuration is not supported.
Nobody lied. The matrix was telling the truth, just not about that instance. It describes the systems supported for the latest build of Campaign, not for the version in general. A platform that has not moved in two years is therefore not covered by today's matrix, even when the line it cares about is printed there in black and white.
That is the one point to take on board before opening it. The rest is a reading method, and it comes down to four moves.
The v7 matrix lives on a single page, with no public history per build: Compatibility matrix, updated 9 October 2026. The PDF filed away in a 2023 project folder is of no use to you, and the printout taped to the server room wall even less.
Adobe states a few reading rules, and each one works against a quick skim.
All minor versions of an entry are supported unless stated otherwise. That is the comfortable rule: if the matrix lists Apache 2.4, the patch number is not your problem. Its limit sits in "unless stated otherwise", which often turns up as a minimum Campaign version attached to the entry.
Anything not on the list is not compatible. The wording is blunt and that is a good thing, because it settles a recurring argument: a database or an operating system missing from the matrix is not "probably supported", it is unsupported. An absence is not silence, it is a refusal.
When a third party technology reaches its end of life, Campaign stops supporting it and removes the entry from the matrix in a later release. That rule deserves its own section below, because it is the one that pushes a quiet instance outside the supported scope without a single setting changing on your side.
First move: record the version and build actually running, on every environment and not just production. On the server side, nlserver pdump returns the full version and the build date.
nlserver pdump
7.X YY.R build XXX@SHA1
<build date>
The fragment after the at sign is a SHA1 hash, of no use for a decision but asked for by support. On the console side, the Help menu then About shows both the console version and the server version. Note both. Since each build is cumulative, applying the latest General Availability build brings everything that came before it. Source: Upgrading Adobe Campaign, updated 27 June 2026. For the wider product lifecycle, see Adobe Campaign Classic v7: versions, support and what Adobe actually says.
Second move: the relational database section. This is the one that carries the most risk, because a database engine upgrade is often decided by an infrastructure team that has never opened Campaign. The v7 matrix covers Oracle from 11g R2 to 23c, PostgreSQL from 11 to 17 including Amazon RDS, and SQL Server from 2014 to 2022. Check the exact engine version, not the family.
Third move: the client console section. It is short, and it is still the one that blocks the most workstations. Two entries only, Windows 10 and 11 on one side, the Microsoft Edge WebView2 runtime in its latest version on the other, mandatory. Plus one rule that is not open to negotiation: the server and the console must be on the same version. A console one build behind its server is not a tolerance, it is a configuration outside the matrix.
Fourth move: external databases, if you use Federated Data Access. The v7 matrix groups them by hosting model, which means the list is not the same depending on whether you are hosted, on-premise or hybrid. Snowflake, BigQuery, Teradata and SAP HANA all appear, but reading the row without reading the hosting model column remains the most common mistake in this section.
| Section of the v7 matrix | What you check there |
|---|---|
| Server operating systems | Debian 11 to 13, RHEL 8 and 9, Windows Server 2019 and 2022, for every server in scope |
| Web servers | IIS 10 or Apache 2.4 in front of the application |
| Tools | JDK 8, 9, 11 or 17, each with its own minimum Campaign version; LibreOffice 7; SpamAssassin 3.4.x |
| Relational databases | Oracle 11g R2 to 23c, PostgreSQL 11 to 17 including Amazon RDS, SQL Server 2014 to 2022 |
| CRM connectors | Salesforce API 49, Microsoft Dynamics Web API |
| FDA external databases | Snowflake, BigQuery, Teradata, SAP HANA, grouped by hosting model |
| Client console | Windows 10 and 11, Microsoft Edge WebView2 runtime in its latest version |
| Mobile SDK and browsers | What depends on your end users' devices and workstations |
💡 The one record that saves a meeting: one line per environment with version, build, operating system, database engine version, JDK and console version. Twenty minutes to produce, and every upgrade discussion then starts from a fact rather than a recollection.
This is the least understood mechanism in the matrix, and the one that produces the unpleasant surprises. Adobe does not decide on its own whether a database or a JDK is supported. When the vendor of the third party technology ends its own support, Campaign ends support behind it, and the entry disappears from the matrix in a later release.
Three consequences. Your instance can fall outside the supported scope with no change at all on your side, because a third party vendor reached a date. The removal from the matrix happens in a release that comes after that end of life, so there is a window where the entry is still listed while real support is already behind you. And watching those end of life dates is not an Adobe job, it is yours, across your operating system, database engine and JDK versions.
Adobe does not document how often the matrix is updated, which rules out any reasoning along the lines of "it will be revised next quarter". The only method that holds is to read it again, and to read it before each infrastructure project rather than after.
Four points come up on almost every instance I am asked to look at.
The minimum Campaign version per entry. Many rows do not hold for the whole of v7: they carry a minimum Campaign version. That is very visible on the JDKs, where 8, 9, 11 and 17 are all listed, each with its own floor. Reading the component version without reading that floor produces a wrong conclusion in both directions, either you plan an upgrade the build does not allow, or you rule out one that is already covered.
The WebView2 runtime. On the client console, the Microsoft Edge WebView2 runtime in its latest version is mandatory, not recommended. On a managed estate with locked down workstations, that single row is worth a request to the workstation team before the console rollout, not during it.
The 32 bit console in v8. The v8 matrix states that the 32 bit console is deprecated in 8.5, and that from 8.6 onwards only the 64 bit one remains. If your estate still has 32 bit workstations, that is a migration prerequisite, not a deployment detail.
External databases by hosting model and by version. On the v8 side, several connectors carry a floor: Redshift from 8.6.4 or 8.7.1 depending on the branch, Azure Synapse from 8.5, Databricks from 8.6.4 or 8.7. A connector listed in the matrix is not a connector available on your version.
⚠️ The sequencing you settle up front: when your build is behind and the third party component has to move, the order of operations becomes the real question. Moving the component first puts you outside the matrix for the duration of the project. Moving the build first can change what is supported, in either direction. That trade off belongs in the scoping phase, not in the evening before the switchover.
The two matrices do not live in the same place, and mixing them up is commonplace. The v7 page, updated 9 October 2026, and the v8 page, updated 5 October 2026, are separate documents. Looking for a v8 entry in the v7 matrix gives you a wrong answer, with no error message to stop you.
The underlying difference is one of scope. The v7 matrix covers server operating systems, web servers and tools, because in v7 part of the infrastructure is yours: on-premise and hybrid exist. Version 8 only exists as Managed Cloud Services, so the server is no longer your concern, and its matrix concentrates on what remains on your side, the client console and the external databases.
One clarification to avoid an unsafe transposition. In v7, every published build carries a documented status. The v8 documentation describes no equivalent. So you cannot read the v8 matrix with the question "what is my build status"; you read it with the version number and its date.
Before any upgrade of an operating system, a database, a JDK or a client workstation, three moves in this order. Record the real build with nlserver pdump on every environment. Open the matrix for the right product version, the current page and not a copy. Check not the row on its own, but the row plus the minimum Campaign version attached to it. If the build is behind, the question is no longer whether something is supported, it becomes in which order to move the build and the third party component.
I take a real reading of your Adobe Campaign environments, check every component against the current matrix and give you the order of operations.
Let us talk about your platform