This document details the prerequisites to a migration, the steps for a migration to Adobe Campaign Classic v7. Steps and optional settings depend on your configuration.
The migration process must be carried out with caution, its impacts must be fully considered beforehand and the procedure must be carried out rigorously. It must only be performed by an expert user. We strongly recommend getting in touch with Adobe Customer Care before starting any migration procedure.
The migration must be tested on the test/stage environment beforehand to make sure it runs smoothly and without any errors. Migrating the production environment must only be performed once the migrated test environment is fully validated.
New features and improvements coming with Adobe Campaign v7 are detailed in the Release Notes.
More prerequisites are available in this page.
Performing a migration can be a chance to update your environment (database engines, operating systems). Adobe Campaign strongly recommends upgrading your production environments to the most recent versions.
For further information about the versions supported by Adobe Campaign v7, refer to the Compatibility matrix.
The general procedure for migrating to Adobe Campaign v7 is detailed in this page.
The changes brought about by Adobe Campaign v7 may also mean that you have to adapt certain specific configurations developed in the earlier versions. Therefore, it may be necessary to perform an audit on all your configurations before the migration: contact Adobe Campaign for any assistance.
For example, particular attention should be paid to specific settings for Web applications, schema extensions with SQLdata or out-of-the-box schema cloning. For more information, refer to this page.
Similarly, in order to respond to the heightened security within Adobe Campaign, some internal mechanisms have been modified: you must adapt these configurations accordingly.