Migrating Adobe Campaign Classic V7 to V8: complete guide

Adobe Campaign Classic V8 has been available for several years, yet many companies are still running V7 in production. Migration is inevitable, Adobe has announced end of support for V7, but it requires careful preparation. Here's what I've learned in the field.

Why V8 changes everything

The fundamental difference between V7 and V8 isn't visible in the interface, it lies in the data storage architecture. V8 introduces two data management modes:

• FDA (Federated Data Access), data stays in an external database (Snowflake, Redshift, Azure Synapse…). Campaign accesses it without duplication.
• FFDA (Full Federated Data Access), all Campaign tables are migrated to Snowflake. This is V8's native mode for high-volume environments.

This architecture change has direct consequences on your workflows, SQL queries and JavaScript scripts. This is not a simple version upgrade, it's a partial rework of the data layer.

5 things to audit before migrating

1. Custom data schemas

All your custom schemas must be reviewed for compatibility with the FDA/FFDA engine. Data types, indexes and primary keys are particularly sensitive. An incompatibility missed during preparation can block the migration in production.

2. Technical workflows

Workflows using JavaScript activities, complex queries or mass data loading are the most exposed. In V8, query execution on Snowflake has different latency compared to a local Oracle or PostgreSQL database. Workflows optimised for V7 can become very slow in V8 without adjustments.

3. Personalisation scripts

JavaScript scripts embedded in delivery content (personalisation tags, dynamic conditions) run on Campaign's JST engine. Compatibility is generally good between V7 and V8, but some native functions have been deprecated. A thorough inventory is required.

4. External integrations

If your Campaign communicates with third-party systems via REST API, SOAP or SFTP files, verify that endpoints and exchange formats are still supported. Native connectors (CRM, CDP, DMP) may require updates.

5. Typologies and pressure rules

Typology rules are often poorly documented and underestimated in migration projects. Take time to map all your rules and verify their behaviour in the new environment.

Typical V7→V8 migration timeline

Total duration ranges from 3 to 5 months depending on platform complexity. Projects that overrun almost always do so during the workflow adaptation phase, systematically underestimated at scoping.

Most common mistakes

• Underestimating the audit phase, a migration without prior inventory is a high-risk migration.
• Not setting up a mirror UAT environment, testing directly in production is out of the question.
• Ignoring "orphan" workflows, disabled workflows never deleted may contain hidden dependencies.
• Forgetting the rollback plan, prepare a Plan B before Go-live, not during.
• Not involving business teams early enough, functional acceptance testing takes time and must be prepared upstream.

Conclusion

A well-prepared V7→V8 migration is a successful migration. Prior audit, a proper UAT environment and early business team involvement are the three pillars of a project with no unpleasant surprises. If you're assessing or planning this migration, I'm available to discuss it.