Adobe Campaign v8: How to Migrate from Campaign Classic v7

If your team runs Adobe Campaign Classic v7, that's where your segmentation, workflows and email, SMS and push sends live, whether in your own data center, in a hybrid setup or on an instance hosted by Adobe. Campaign v8 raises familiar questions: do we have to migrate now, what changes, and would it make more sense to move to Adobe Journey Optimizer (AJO)?

The pressure doesn't come from support: according to Adobe, core support for Campaign Classic 7 ends on December 31, 2030, and v7 still gets new builds. The reasons to plan are different: v8 exists only as a managed service in Adobe's cloud, it changes the data architecture with Snowflake, it adds a web user interface (also available in Spanish) and it connects natively with Adobe Experience Platform (AEP). And since Adobe doesn't yet offer an automated migration from v7, moving to v8 is a project, not an upgrade.

At WolfSellers we implement and operate Adobe Experience Cloud. Here we explain what changes in v8, how to plan the migration and when Campaign makes more sense than AJO or Marketo Engage. If you're still choosing a tool, start with our guide to choosing a marketing automation platform.

---

What Adobe Campaign is and which versions exist

Adobe Campaign is Adobe Experience Cloud's platform for large-scale, cross-channel campaign management: it stores and segments customer data in its own database, orchestrates workflows and sends email, SMS, push and direct mail; its Message Center module also sends real-time transactional messages. Adobe describes Campaign v8 as an orchestration engine focused on batch-based journeys, paired with a real-time messaging server for notifications such as password resets.

For v7 users, Adobe says the way you work barely changes and most features remain available. And v8 isn't AJO, which runs on AEP. For the full map of the suite, see our Adobe Experience Cloud guide.

Where Campaign runs: on-premise, hybrid or Managed Cloud Services

Campaign Classic v7 supports three hosting models:

• Hosted by Adobe: the interface, execution and database, including the unsubscribe and preference pages, run on Adobe's infrastructure.
• On-premise: everything lives in your data center; your team applies upgrades and you need a database administrator.
• Hybrid: the marketing instance sits inside your firewall and Adobe runs execution in its cloud. Only the data needed to personalize emails goes to the cloud, and it isn't stored there.

Campaign v8 exists only as a Managed Cloud Service. It can't be installed on-premise or in hybrid mode; each environment comes with a dedicated virtual private cloud (VPC), Adobe upgrades the servers, and built-in packages, schemas and reports can't be modified. If you need Campaign on-premise, v7 is the only option. And if your policy requires personal data to stay in your data center —exactly what the hybrid model solves— review it with your legal and security teams before planning v8.

What mid-sourcing is in Adobe Campaign

Mid-sourcing separates the marketing instance —data, campaigns and workflows— from execution: the instance passes only the data needed to build the messages to a server hosted by Adobe, which sends them and handles bounces.

• In Campaign Classic v7 it's a deployment option that must be in your license, driven by SOAP calls over HTTP or HTTPS. Per Adobe, it simplifies configuration, saves bandwidth and keeps the database inside the company; the trade-off is a slight delay in execution information and reporting.
• In Campaign v8, every delivery goes through mid-sourcing, with both instances in Adobe's cloud. Adobe calls this a hybrid architecture, but it isn't the v7 hybrid model. Coming from v7: internal routing isn't available, and delivery statuses aren't updated instantly. If your package includes several mid-sourcing instances, a large delivery can be split across them.

If a dashboard relied on seeing a delivery's status in real time, it needs adjusting.

Message Center: transactional messaging in Adobe Campaign

Message Center is Campaign's transactional messaging module: it turns events from your systems —a purchase, a shipment, a password change— into personalized messages sent in real time by email, SMS or push. Adobe defines them as non-promotional messages.

It works with two pieces on separate machines: a control instance, where templates are created and published, and one or more execution instances, which receive events through an API —Adobe documents the PushEvent and PushEvents SOAP methods— and send the messages. In v7, Message Center requires a specific license; in v8, Adobe configures it at your request.

Snowflake and FFDA: what changes in your data with Campaign v8

Campaign v8 has two deployment models:

FFDA is where a migration planned as if it were v7 most often goes wrong:

1. Keys. Objects use UUIDs instead of numeric keys, and Snowflake doesn't prevent duplicate keys: keeping them consistent is your team's job.
2. Batches. Bursts of unitary API calls aren't recommended, and Adobe warns that custom code writing directly to the database must be refactored.
3. Replication. A technical workflow replicates the tables needed in both databases every hour.
4. Custom tables. Every custom table is created in the cloud database.
5. Not available in FFDA: Marketing Resource Management (MRM), coupons, web tracking and surveys.

If your data already lives in AEP or a data warehouse, decide during the redesign what lives in Campaign. Our guide to data governance in Adobe Experience Platform can help.

Campaign Classic v7 vs. Campaign v8: what changes and what's gone

What's gone in v8. Adobe lists as no longer supported: Social Marketing with Facebook, the ACS Connector (Prime offering) to Campaign Standard, LDAP integration, username/password sign-in, and the hybrid and on-premise models. Some of these may still appear in the interface. For Facebook, Adobe suggests the X integration or a custom channel; if you use LDAP today, access moves to Adobe IMS, which supports Federated ID accounts authenticated by an external identity provider, such as your company's.

Which channels Adobe Campaign v8 supports

These are Campaign v8's channels per its documentation; which ones you have depends on your contract:

For a channel that isn't on the list, check your contract with Adobe or consider a custom channel.

Integration with Adobe Experience Platform and Journey Optimizer

With AEP, Campaign v8 uses two Adobe Campaign Managed Cloud Services connectors, requested through Adobe. The destination connector sends AEP audiences to Campaign and syncs profile attributes —opt-in and opt-out values, for example— in update-only mode, for profiles that already exist in Campaign. The source connector brings Campaign delivery and tracking logs into AEP.

With AJO, the journey is designed in AJO and the send can go out through the Campaign v7 or v8 Message Center, by email, push or SMS. Adobe sets up the connection at provisioning; these actions can be combined with AJO's native channels in the same journey, but not with the Read Audience or Audience Qualification activities. That lets you move real-time journeys to AJO without immediately rebuilding your transactional templates. More in our guides to Adobe Journey Optimizer and Real-Time CDP.

How to plan the migration from Campaign Classic v7 to v8

Adobe doesn't yet offer an automated migration from Campaign Classic v7, so the path depends on where your instance runs:

For on-premise or hybrid migrations, Adobe lists due diligence, an environment audit, data cleanup, stage migration and production cutover. This is how we put it into practice in every case:

1. Inventory. Schemas, workflows, templates, typologies, forms, JavaScript code, external accounts, APIs, connectors, Message Center, reports and users. What isn't used doesn't get migrated.
2. Scope. Which features without a v8 equivalent you use today, whether the target is FDA or FFDA, and which use cases belong in AJO instead of being rebuilt in Campaign.
3. Identity. Operators move to Adobe IMS, and technical operators to Adobe Developer Console technical accounts, a mandatory step if you use the Campaign APIs.
4. Data model. UUIDs, key consistency, custom tables in the cloud database and batch loads; data changes go through workflows, not direct database access.
5. Integrations. Rewrite code that wrote directly to the database and adapt integrations to batch processing.
6. Deliverability and channels. If your sending IPs change —Adobe's deliverability guide notes you can't bring established IPs with you when switching platforms— they need warming, starting with small volumes and your most engaged contacts, and you should at least split marketing and transactional email into separate IP pools. For push, Adobe recommends the AEP Mobile SDK with the Campaign extension instead of the deprecated Campaign SDK.
7. Testing. Everything goes through the stage environment first, with realistic volumes.
8. Coexistence and cutover. While v7 and v8 run side by side, opt-outs and suppression lists stay in sync between them. Cutover happens flow by flow —transactional, recurring, campaigns— and v7 is shut down last.

We don't quote generic timelines: they depend on your data, workflows and custom code, and we estimate them after the inventory.

Consent and opt-outs in Mexico: what to watch when migrating

A migration moves lists, preferences and opt-outs, and in Mexico that's governed by the Federal Law on the Protection of Personal Data Held by Private Parties (LFPDPPP) and the Federal Consumer Protection Law (LFPC). This isn't legal advice: validate it with Mexican counsel, especially if you send to customers in Mexico from the US or Canada.

• Consent (LFPDPPP, Art. 7). As a general rule, implied (tacit) consent is valid: the individual had the privacy notice available and didn't express otherwise. Financial or asset-related data requires express consent, and sensitive data requires express, written consent (Art. 8). Consent can be revoked at any time, and the privacy notice must explain how. The right to object is in Article 26; ARCO rights (access, rectification, cancellation and objection) are covered in our Mexican data protection guide.
• Advertising (LFPC, Arts. 17, 18 and 18 Bis). It must show the name, address and phone number —or, failing that, the electronic address— of the merchant, of whoever sends it on the merchant's behalf, and of Profeco, Mexico's federal consumer protection agency. Sending it to people who asked not to receive it, or who are listed in Profeco's public registry of consumers who don't want their information used for marketing, is prohibited, and if you send through third parties you share responsibility for how that information is handled.

In Campaign, that translates to:

1. Migrate opt-outs along with profiles: service unsubscriptions, per-channel exclusions (the profile's No longer contact section) and quarantine. An SMS reply of "STOP" or a spam complaint puts the address in quarantine as Denylisted.
2. Mind FFDA latency: there, subscriptions and unsubscriptions are processed hourly, so design the sync so an opt-out takes effect before the next send.
3. Handle access and deletion requests: since version 8.3, Campaign processes the ones that come in through Adobe Privacy Service.
4. Separate the law from deliverability: the law accepts implied consent, but Adobe recommends double opt-in to protect sender reputation. We recommend applying the stricter standard to anything you'll send from new IPs.

Campaign, Journey Optimizer or Marketo Engage: when each one fits

If you're building on AEP, compare before rebuilding everything in Campaign v8: beyond journeys, AJO now includes batch orchestrated campaigns with the Journey Optimizer – Campaigns & Journeys or Journey Optimizer – Campaigns packages. For B2B, see our Marketo Engage guide.

Combining them is fine: AJO can send through Campaign's Message Center, and Campaign receives AEP audiences. What doesn't pay off is licensing more platform than your team can operate; we cover how to size it in How Much Adobe Do You Need?. Adobe quotes each product's license based on your volume; we estimate the total cost of implementing and operating it in an assessment.

How we do it at WolfSellers

We start with an assessment of your instance: hosting model, version, data model, workflows, integrations, deliverability and actual use of each feature. That answers two questions before we touch anything: whether to migrate to v8 now or later, and which part of your operation makes more sense in AJO.

Then we run the migration in phases —data model, workflows, integrations, the move to Adobe IMS, IP warming with Adobe, testing in stage and coexistence through cutover— and, if you'd like, we keep operating the platform with you. We cover it in our Adobe Campaign, Adobe Journey Optimizer, Marketo Engage, Adobe Experience Platform, Data Engineering & Integrations, consulting and support and maintenance services.

We're an Adobe Solution Partner headquartered in Mexico City, and we don't sell Adobe licenses: you license directly from Adobe. If you'd like a review of your Campaign instance, contact us or see how we work as a partner.

---

Frequently asked questions about Adobe Campaign v8 and migrating from v7

What is Adobe Campaign?

It's Adobe Experience Cloud's platform for large-scale, cross-channel campaigns: it stores and segments customer data, orchestrates workflows and sends email, SMS, push and direct mail, plus transactional messages through Message Center. Three current products share the name: Campaign Classic v7, Campaign v8 and Campaign Standard.

How long is Adobe Campaign Classic v7 supported?

According to Adobe's technical support periods matrix, core support for Campaign Classic 7 ends on December 31, 2030, with no extended support period. Adobe still ships v7 builds: 7.4.4 came out in September 2026.

Can Adobe Campaign v8 be installed on-premise or in a hybrid setup?

No. Campaign v8 is available only as a Managed Cloud Service, in a cloud managed by Adobe. If you need Campaign in your own data center or in a hybrid setup, Campaign Classic v7 is the only option.

What is mid-sourcing in Adobe Campaign?

It's a setup where the marketing instance delegates sending to a server hosted by Adobe and passes it only the data needed to build the messages. In Campaign Classic v7 it's a deployment option that must be in your license; in Campaign v8, every delivery goes through mid-sourcing.

Is there an automated migration from Campaign Classic v7 to v8?

Not yet: Adobe states that automated migration from v7 isn't available yet. If your v7 is hosted by Adobe on Managed Cloud Services Advanced or Enterprise, Adobe schedules the upgrade; if it's on-premise or hybrid, you first license Managed Cloud Services and migrate to the cloud with help from Adobe or a partner.

What is Message Center in Adobe Campaign?

It's Campaign's transactional messaging module: it receives events from your systems, such as a purchase or a password change, and sends personalized messages in real time by email, SMS or push. A control instance publishes the templates, and one or more execution instances receive the events and send.

What happens if I'm on Adobe Campaign Standard today?

Adobe states that Campaign Standard users are eligible to transition to Campaign v8 on Managed Cloud Services. To ease the move, v8 added Standard capabilities such as Dynamic Reporting, centralized branding, landing pages, visual fragments and REST APIs for migrated users.

Should we migrate to Campaign v8 or move to Adobe Journey Optimizer?

It depends on your use cases. For batch campaigns with complex segmentation on your own data, migrating to v8 preserves your investment; if you're building on Adobe Experience Platform and need to react to real-time events, Journey Optimizer is the better fit. They can also be combined: Journey Optimizer can send through Campaign's Message Center.

Related services

If this topic is relevant to your business, these services from WolfSellers can help you implement it:

• Adobe Campaign
• Adobe Journey Optimizer
• Data Engineering & Integrations