- Campaign v7 documentation
- Latest updates
- Release Notes
- Get started
- Start with Adobe Campaign
- Privacy
- Profile management
- Import and export data
- Filter data
- Create queries
- Permissions
- Data packages and enumerations
- Connectors
- Create and send messages
- Get started with messages
- Key steps when creating a delivery
- Send emails
- Send SMS
- Send LINE messages
- Send push notifications
- Send direct mail
- Use delivery templates
- Personalize deliveries
- Use seed addresses
- A/B testing
- Services and subscriptions
- Monitor deliveries
- Track messages
- Deliverability management
- Content management module
- Orchestrate marketing campaigns
- Marketing Resource Management
- Distributed marketing
- Response manager
- Design and share reports
- Design web content
- Create online surveys
- Integrate with Adobe Experience Cloud
- Automate with workflows
- Get started with workflows
- Execute a workflow
- Targeting activities
- Flow control activities
- Action activities
- About action activities
- Delivery
- Delivery control
- Continuous delivery
- Recurring delivery
- Cross-channel deliveries
- Local approval
- Data loading (RDBMS)
- Loading (SOAP)
- Data loading (file)
- Content Management
- Data extraction (file)
- SQL code and JavaScript code
- SQL Data Management
- Nlserver module
- Update aggregate
- Event activities
- Use cases
- Monitor workflows
- Advanced management
- Manage Offers
- Transactional Messaging
- Integrate with social media
- Installation and configuration guide
- Architecture principles
- Deployment types
- Security and privacy settings
- Install Campaign (on-premise)
- Deploy Campaign (on-premise)
- Configure Campaign
- Connect to Campaign
- Connect Campaign to external systems
- Appendices
- Monitoring guide
- Developers guide
- Migration guide
- Technotes
- Campaign Control Panel
Prerequisites
This page lists specific steps to perform before starting the migration process. You must also refer to this page for more guidance.
In this document, commands are given as samples. They can vary depending on your configuration.
- Check your Adobe Campaign version: before migrating, install the latest build of the current version that you are using.
- Back up your data.
- Check your environment: you cannot change your database engine system (DBMS). For instance, you cannot switch from a PostgreSQL engine to an Oracle engine. However, you can switch to the latest versiuon of your database engine. Note that it is not possible to go from a non-Unicode database to a Unicode database.
Migration steps
The migration procedure must be carried out on all servers and in a particular order.
-
In the case of a standalone platform (single machine mode), the application is migrated in its entirety.
-
In the case of a standard platform (enterprise), the migration steps are as follows:
- Migrate the marketing server.
- Migrate the mail server (mta).
- Migrate the redirection and tracking servers (Apache / IIS).
-
In the case of a Cloud Messaging platform, the execution servers are hosted at Adobe Campaign. Please contact Adobe Campaign to coordinate migration between different servers.
-
In the case of a Power Booster or Power Cluster platform, the migration steps are as follows:
- Migrate the redirection and tracking servers (Apache / IIS).
- Migrate the Power Booster/Cluster servers.
- Migrate the marketing server.
User passwords
In v7, internal and admin operator connection must be secured by a password. We strongly recommend assigning passwords to these accounts and all operator accounts, before migration. If you have not specified a password for internal, you will not be able to connect. To assign a password to internal, enter the following command:
nlserver config -internalpassword
The internal password must be identical for all the tracking servers. For more information, refer to the Internal identifier and Permissions sections.
Business.Adobe.com resources
Resources
Adobe Account
