Migrate Adobe Campaign V7 On-Prem Instance to V8 Adobe Cloud | Community
Skip to main content
Parvesh_Parmar
Community Advisor
Parvesh_ParmarCommunity Advisor
Community Advisor
September 18, 2023
Solved

Migrate Adobe Campaign V7 On-Prem Instance to V8 Adobe Cloud

  • September 18, 2023
  • 1 reply
  • 3645 views

Hello,

 

I have a question related to Adobe Campaign V8 migration.

We have a client that is currently on on-prem V7 and looking forward to migrating to Adobe Cloud V8. They have a hybrid architect.

 

According to our analysis we are looking for the following path:
1. Move the V7 marketing server from on-prem server to Adobe Managed cloud service.
2. Migrate V7 to V8 on Adobe Managed cloud server. 

 

We do not get the clear answer from Adobe how they migrate the current data of on-prem marketing server to manage cloud.

 

As per my assumption, we might need to do the following step:

Steps:1. First we need to configure Adobe Campaign env. on Adobe cloud. For e.g. we need to export all the custom schema, forms, JS, webapp, reports, workflows, campaign, delivery etc. via package from on-prem to Adobe cloud.

 

Step 2. We need to import all the technical and functional data via files. For e.g. data of recipient, broad logs, tracking logs, and other functional data.

 

Can you please let me know if you have any experience in this type of exercise and if yes what is the steps to migrate and how much time it will take?

 

Feel free to share this message to someone who have this experience.

 

Kr,

Parvesh

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by costa_n11

Hi @parvesh_parmar 

To make it short, the reason you don't get a clear answer on moving the data is because Adobe does not take the responsibility to move the data from on-prem instance to hosted instance and you have a significant migration project in hand to do so. In a nutshell, the migration project will involve

  1. Revisit your data ingestion processes: if you have follow ACC architecture principles, you would load data via flat files and you would have to do a initial load of your main customer data
  2. When it comes to communication history (delivery, delivery logs, tracking, exclusion, bounces), you will design a solution where you would keep in sync these entities in your 2 on-prem and hosted instances (extension of the schema by adding a 2nd ID and building files to export/ import the history between the 2 instances and keep your typology rules effective (depending on your approach, you would have to revisit these rules but there are way to do it that do not introduce any impact)
  3. Doing the above will ensure you that you can migrate your campaigns over a long period of time
  4. The tricky part is the sender domain, in ideal circumstances, you would define new sender domains for the hosted instance (that you would ramp-up of course). Doing so will avoid overcomplexity in the tracking server configuration

You would have to review all your endpoints for the ACC landing pages and APIs (if you use them)

 

We had customers having done it successfully in the past although if the on-prem deployment doesn't follow some architecture principles, the road to migration can be more or less complex and you need to plan it carefully of course....

 

You should definitively engage Adobe Consulting Services who would help you in shaping the migration activities avoiding pitfalls along the way. 

 

Hope this helps,

Thanks

Denis

 

 

1 reply

C
Adobe Employee
costa_n11Adobe EmployeeAccepted solution
Adobe Employee
September 18, 2023

Hi @parvesh_parmar 

To make it short, the reason you don't get a clear answer on moving the data is because Adobe does not take the responsibility to move the data from on-prem instance to hosted instance and you have a significant migration project in hand to do so. In a nutshell, the migration project will involve

  1. Revisit your data ingestion processes: if you have follow ACC architecture principles, you would load data via flat files and you would have to do a initial load of your main customer data
  2. When it comes to communication history (delivery, delivery logs, tracking, exclusion, bounces), you will design a solution where you would keep in sync these entities in your 2 on-prem and hosted instances (extension of the schema by adding a 2nd ID and building files to export/ import the history between the 2 instances and keep your typology rules effective (depending on your approach, you would have to revisit these rules but there are way to do it that do not introduce any impact)
  3. Doing the above will ensure you that you can migrate your campaigns over a long period of time
  4. The tricky part is the sender domain, in ideal circumstances, you would define new sender domains for the hosted instance (that you would ramp-up of course). Doing so will avoid overcomplexity in the tracking server configuration

You would have to review all your endpoints for the ACC landing pages and APIs (if you use them)

 

We had customers having done it successfully in the past although if the on-prem deployment doesn't follow some architecture principles, the road to migration can be more or less complex and you need to plan it carefully of course....

 

You should definitively engage Adobe Consulting Services who would help you in shaping the migration activities avoiding pitfalls along the way. 

 

Hope this helps,

Thanks

Denis

 

 

    Parvesh_Parmar
    Community Advisor
    Parvesh_ParmarCommunity AdvisorAuthor
    Community Advisor
    September 18, 2023

    Hello @costa_n11, 

     

    Thanks for your reply.

     

    For the point 4, we do not have any issue. Our IP and domains are hosted on Adobe mid server and we are not going to change it.  

    We just need to migrate Marketing server or you can say Application server.

     

    I would like to discuss point 1 and 2 little more , to understand it better. 

     

    1. For the point 1, As I understood, we need to load the customer data via flat files. 

     My question, Do we need to ingest it as a fresh data? I mean adobe campaign will create new recipient primary key for each customer Or we can  use the existing recipient id.  

    For e.g. Communication data is currently based on current recipient id. If we ingest the customer data as fresh records and create a new recipient id, then it would not link with the current communication data. 

    Can you little bit explain how it was done for the client which migrated the data? 

     

    2. For the point 2, I do not understand the solution you mentioned. Are you referring to import current on-prem communication data in same table, where old id will be store in different filed and campaign will create a new PK?  Can you please little explain it in more details with example to understand it better with? 

     

    Thanks in advance!

    Kr,

    Parvesh

    Parvesh Parmar – Adobe Community Advisor https://www.linkedin.com/in/parvesh-parmar/
    C
    Adobe Employee
    costa_n11Adobe Employee
    Adobe Employee
    September 19, 2023

    Hello @marcel_szimonisz, 

     

    Yes, our first approach will be to see if we can import all of the existing data (e.g., recipient, broad logs, tracking logs, etc.) in the same form with the same key.

     

    However, I see,  we need to take care of the sequence of the primary key when importing the primary key from the old data.

    But i think this approach going to helpful if we go to big bang approach, I mean we switch off on-prem and turn on the hosted server.

     

    Thanks your suggestion.

     

     

    Best regards,
    Parvesh

     


    Hi @parvesh_parmar and @marcel_szimonisz 

    I will be extremely careful on the following "you can use  2 different mail servers for the same domain name".

    On ACC V7, although technically possible, in fully hosted instances, this is not a standard configuration and you will request a configuration that goes against Adobe's internal processes, will most likley break certain tools  (Adobe Campaign Control Panel for instance) and will require an exception in all cases. The lengthy process this will take to get it done and the issues it will bring will not overcome creating new sender domain and executing a ramp-up...From experience, such configuration is very tricky to get done...

    As for the data, you could of course load the logs as is in the hosted schemas saying that I suggest you keep the 2 set of IDs distinct, much more safer if anything goes wrong, replay, etc.... 

     

    Of course in a big bang approach you might not bother but if you choose parallel run (aka the 2 instances sending emails along for couple of weeks / months), then it'd be safer to keep the IDs separate....

     

    Just thoughts from experience on these topics,

    Thanks

    Denis

     

      Terms & ConditionsAccessibility statement

      Loading footer...