The question comes back with every budget cycle: how long is v7 supported? There is exactly one official date, and it sits in a table almost nobody opens. Adobe's end of life matrix gives Campaign Classic 7 a general availability date of 31 March 2017 and a core support end date of 31 December 2030, with no extended support. The page carries an update dated 15 May 2026. Source: Adobe end of life matrix.
The product documentation gives no date at all. The v7 FAQ states that Campaign Classic v7 will reach End of Support "in the coming years", wording still in place on 9 October 2026 and repeated word for word in the key concepts FAQ. So you have two Adobe pages about the same product: one with a 2030 deadline, one with none. No Adobe page reconciles the two. Sources: Campaign Classic v7 FAQ and key concepts FAQ.
For a steering committee, the only usable date remains 31 December 2030. The Campaign Web FAQ also points to the end of life matrix when asked about timelines, in its 5 October 2026 version. What has to be decided now, though, does not depend on that date. It depends on your deployment model.
The end of life matrix is a generic table shared across all Adobe products. It tells you nothing about Campaign as such, it fills in columns.
| Matrix entry | Value | How to read it |
|---|---|---|
| Campaign Classic 7, general availability | 31 March 2017 | Start of the lifecycle |
| Campaign Classic 7, core support ends | 31 December 2030 | The only official date in existence |
| Campaign Classic 7, extended support | none | Nothing is planned past the first deadline |
| Campaign 6.1, core support ended | 29 March 2020 | Historical reference from the same matrix |
| Campaign 6.1, extended support ended | 29 March 2022 | 6.1 was given two further years |
| Split by deployment model | none | A single row, hosted and on-premise alike |
The product documentation does the opposite: it covers Campaign in detail and says nothing about the date. Both sources carry recent updates, May 2026 for the matrix, October 2026 for the FAQ. I have found no Adobe page that explains the gap, justifies it, or ranks one source above the other. The gap can be observed, it cannot be explained, and any reading beyond that observation is guesswork.
One thing not to over-read either: the matrix holds a single row for Campaign Classic 7. There is no separate date depending on whether you are hosted, on-premise or hybrid. If someone quotes you a deadline specific to your hosting model, ask them for the source.
The matrix uses two terms, core support and extended support, without defining them on the page. The official definitions are not published there, so nobody can tell you exactly what each level covers without stepping outside the document. What can be read is the structure: some products have two rows, Campaign Classic 7 has one.
The most telling reference point is the previous version. Campaign 6.1 had core support until 29 March 2020, then extended support until 29 March 2022, two further years beyond the first deadline. Campaign Classic 7 has no second row. On 31 December 2030, the matrix plans nothing behind it.
⚠️ The planning trap: 2030 looks far away, but a change of hosting model followed by a major version migration is not decided in the year of the deadline. If you are on-premise, your route is two projects in sequence, not one.
Beyond the dates, the nature of what Adobe ships says something. The v7 builds released in 2025 and 2026 contain almost nothing but fixes and security fixes. One exception across two years, build 9400, which brings the move to the Adobe Analytics 2.0 API. Sources: latest release, updated 15 October 2026, and 2025 releases.
That does not mean maintenance has stopped. Ten builds were published between March and October 2026, and on 15 October 2026 two builds held General Availability status, 7.4.5 build 9420 and 7.4.4 build 9403. The platform is maintained, it no longer evolves functionally. For the detail of build statuses and how to read your own, see Adobe Campaign builds, versions and release notes.
Taking the reading on each environment is a thirty second job:
nlserver pdump
7.X YY.R build XXX@SHA1
<build date>
Staying on v7 until 2030 does not mean standing still. Adobe commits to a version upgrade at least once a year, and who performs it depends on the deployment model. On a hosted environment Adobe applies the upgrade, and critical security patches go out without prior notice. On Managed Services and hybrid, the request goes through Customer Care. On-premise, you download the latest General Availability build and apply it yourself. Production upgrade windows run Monday to Thursday, with Friday reserved for non-production.
One last signal, the only dated removal in the whole of the v7 documentation: the Netsize SMPP connector, targeted for January 2027. It is the sole operational deadline set down in writing before 2030, and it only affects part of the installed base. Source: deprecated features, 5 October 2026 version.
Three options get raised in meetings: move to v8, move to Campaign Web, move to Journey Optimizer. Only one of them is documented as a migration.
Version 8 exists on Managed Cloud Services only. On-premise and hybrid do not exist in v8. An on-premise or hybrid customer therefore has to move to Managed Cloud Services first, and only then consider v8. The documentation adds one sentence that reshapes every plan: "Automated migration from an existing Campaign Classic v7 environment is not yet available", as of 5 October 2026. Source: moving from v7 to v8.
Campaign Web is the web interface of v8, available from 8.6, with Adobe IMS sign-in. It is not an alternative product to v7, it is an interface sitting on top of a v8. Its capability matrix, updated 12 October 2026, lists what remains console only: creating typology rules, designing offers, web applications, workflow ETL activities, external accounts and schemas, cube reports, monitoring. Source: Campaign Web capability matrix.
Journey Optimizer, finally, is documented as an integration with Campaign v8, not as a way out of v7. Nothing in the documentation presents it as the target of a migration from Classic.
| Starting point or option | What the documentation says | What it forces |
|---|---|---|
| Hosted, Managed Cloud Services | The only model v8 exists on | One project, but a change of data model |
| Hybrid | Does not exist in v8 | Move to Managed Cloud Services first |
| On-premise | Does not exist in v8 | Move to Managed Cloud Services first |
| Migration tooling | No automated migration available as of 5 October 2026 | Rebuild and data carry-over to scope, no tooled switchover |
| Campaign Web | Web interface of v8 from 8.6 onwards | Assumes a v8, does not replace the console |
| Journey Optimizer | Documented as an integration with Campaign v8 | Not a migration target from v7 |
The decision is not the same depending on where your server runs.
If you are on-premise or hybrid, your first item is not v8, it is the change of hosting model. Two projects follow one another and the second cannot start before the first is delivered. The inventory work, on the other hand, starts straight away: record the build on every environment, the third party systems and the external databases, then check that list against the compatibility matrix, which describes the systems supported for the latest build and not for the version in general. Source: v7 compatibility matrix, updated 9 October 2026.
If you are already on Managed Cloud Services, the question shifts to the data model. The v8 Enterprise deployment rests on a local PostgreSQL database for the interface, the configuration and real time processing, and on a Snowflake cloud database for customer data, logs and batch execution, with one way replication running hourly. Keys become non sequential UUIDs, and Snowflake does not guarantee their uniqueness: consistency falls to the customer and duplicates are handled by hand. Direct database access disappears, writes go through workflows or through the xtk.session.ingest and xtk.session.ingestExt APIs, in batches rather than unit calls.
Three further points weigh on the scoping. Authentication goes through Adobe ID only, since login with a username and password and the LDAP integration have both been removed. Opt-ins, opt-outs and mobile registrations become asynchronous, processed once an hour, so delivery statuses are no longer immediate and internal routing is not possible. The Enterprise deployment offers neither Marketing Resource Management, nor coupons, nor web tracking, nor surveys. The full route is covered in the v7 to v8 migration guide.
One last scoping element concerns cadence. Version 8 does not carry over the v7 build statuses. It moves on a major, minor, patch scheme every two to three months, the latest documented version being 8.9.4, dated 15 October 2026. Source: Campaign v8 upgrades, updated 1 September 2026. The maintenance calendar your teams work to today does not transpose as it stands.
💡 An interface trap: some features removed in v8 remain visible in the interface. A quick demo is not enough to validate a scope, every requirement has to be checked against the Enterprise deployment documentation.
When someone asks how long v7 will live, answer 31 December 2030, cite the end of life matrix, and add that the product documentation carries no date. Then ask the question that actually commits a budget: which hosting model is the platform running on? If the answer is on-premise or hybrid, the deadline that matters is not 2030, it is the date you start the move to Managed Cloud Services.
I take a real reading of your platform, hosting model, builds and third party systems, and tell you which path to v8 is realistic and in what order.
Let us talk about your path