As a valued Adobe Campaign Classic customer, we are committed to providing you the best experience and value. Over the years, we have realized the value and reliability of hosting our customers in the cloud. As part of our Yearly Upgrade Initiative, we are moving all of our customers to Adobe Managed Services (Public Cloud on AWS) to provide better and more reliable services.
This program has three main goals:
Campaign Classic v7 migration to Public Cloud impacts customers using Adobe Managed Services only.
Bring a robust, reliable solution for Adobe Campaign Classic customers
Yearly upgrades makes future upgrades easier
The migration to Adobe Managed Services (Public Cloud) will happen in 2020/2021 for affected accounts. Adobe will lead and guide your organization through this journey.
To get this effort started, accounts requiring this migration will receive an email communication from Adobe providing a timeline and access to documentation. This will be your notification that your account is scheduled to be migrated.
A migration can be initiated by opening a new Customer Care support ticket. Use the subject line “Migrate to AWS”.
This migration to the Cloud is first step to the yearly upgrade program of your Adobe Campaign instances. This migration is mandatory if you are hosted in a Data Center that is not the Public Cloud (AWS).
The Adobe Managed Services cloud is hosted on Amazon Web Services (AWS), a modern, secure, and optimized environment. Learn more about AWS.
Adobe plans to decommission the legacy Data Center, Adobe Campaign instances running there must be transferred to the new reference Data Center, AWS.
This is a critical path forward as your current location may be exposed to security and performance vulnerabilities.
In addition, this migration is now a prerequisite to any future Build upgrade of your Adobe Campaign. Build upgrade is no more possible on legacy Data Center.
Adobe is committed in securing your data and getting you on track for the future of Adobe Campaign. We need your partnership to make it a joint success!
We have organized a team of dedicated Customer Care Reps, Customer Success Managers, Product Managers, Engineers, TechOps Specialists and Product Consultants to assist and ensure the experience is smooth and seamless. We are committed to making sure you have the relevant project and contact information.
We have invested a huge effort in developing technologies that will make this migration fast, seamless and secured.
Learn more in Campaign migration to Public Cloud FAQ.
Adobe handles most of the actions. We need you for validation and sign-off.
The database will be dumped from the legacy data center and restored at Public Cloud (AWS). When restarted on the new data center, the application will resume from the exact state it was before shutdown. Users won’t see any difference, except that some scheduled tasks will have been delayed.
Email sending IPs
When the migration is complete, the Campaign instance will have entirely different sending IPs. As a matter of ensuring a smooth transition, Adobe will implement a ramp-up of the new sending IPs by progres-sively switching traffic from the old to the new IPs.
Data integration IPs
Data integration on the client side might be affected by the change of IPs for data integration. The change might affect both directions, depending if Campaign acts as a server or a client.
In general, that means that the client should check possible IP-restrictions set on their firewalls and adapt them accordingly.*
Existing Campaign servers (containers actually) will be moved to Public Cloud (AWS) in a “lift-and-shift” approach. That is, no new server installation will be needed, but the entire server will be transferred to the new data center. The operation will require no more work than low-level technical reconfiguration.
Under the sub-domain(s) used for marketing communication: will remain the same. However, depending on the implementation, actions might will be needed on the client side:
For user access and data integration, the names under neolane.net will remain unchanged.
That means the change will be transparent for users, and data integration implementations, if server names were not replaced by hard-coded IPs.
Email sending IPs
First, Adobe Deliverability will assess the platform’s deliverability status and recommend a plan for the switch to the new IPs.
Adobe will provision the same number of IPs on the new data center.
The ramp-up of new IPs can begin as soon as the new IPs are provisioned.
Data transfer between data centers is on the critical path of the downtime.
The data is stored in two ways:
Reducing the size of the database is of highest importance to speed up the data transfer.
We recommend slowing down and ideally pausing all executions just before the application is shutdown on the legacy data center: deliveries and workflows. That will ease the restart on Public Cloud (AWS) as processes will have been given time to pause “gracefully” and save any in-progress execution state.
During the migration
While the migration happens, only one service will remain functional: email links redirection. In other words, recipients will be able to reach the landing page when they click in an email. These clicks will however not be recorded, so click rates for the deliveries that were started shortly before the migration will be lower than normal.
Once migrated to the new environment, the application will be restarted progressively:
Deletion of instances on legacy Data Center
Once the application migration is complete, there is no plan for running any process again on the legacy data center. We expect that all data on the legacy data center can be erased, except for temporary backup purposes, until the scheduled backup processes have run on Public Cloud (AWS).
Normally, the domain used for sending email (part on the right of the @ sign in the error address) from Campaign has been delegated to Adobe. The delegation can be changed and implemented towards the AWS DNS servers.