How do I migrate workflows, templates, etc., from one environment to another (e.g., from development environment to production environment)?

[jae_lee]

Hi,

How do I migrate (or duplicate) workflows, templates, db, etc., from one environment to another in Adobe Campaign? For example, templates developed inside the development environment and migrate (or duplicate) them to our production environment?

Thank you.

[Vipul_Raghav · Accepted solution]

Hi Jae,

You need to create packages of each entity, export them from a lower environment where you usually develop and then import them on to production.

For more information on packages import and export, please refer to official documentation https://docs.campaign.adobe.com/doc/AC6.1/en/PTF_Administration_Elements_Data_packages.html

Regards,

Vipul

[assiba_johnson]

Hi Vipul,

I am not able to access the following link:

- https://docs.campaign.adobe.com/doc/AC6.1/en/PTF_Administration_Elements_Data_packages.html

Thanks

[jae_lee]

Hi,

Thank you as always Vipul. Is there a way to migrate packages from a higher environment (from production) to a lower one (say, staging, testing, or development) environment?

Jae

[Vipul_Raghav]

Hi Jae,

The same procedure applies there as well.

You can export package from one environment and import it to the other.

Regards,

Vipul

[jae_lee]

Thank you so much Vipul!

Jae

[jae_lee]

Hi,

I received this reply from Adobe tech support, when I broached migrating workflows, campaigns, etc.:

"The process that is followed, internally when requests such as this are raised, is to refresh the NON-PROD database with the PRODUCTION database.  This is done by restoring the latest backup into the NON-PROD environment.

Please see the following documentation for more information: https://docs.campaign.adobe.com/doc/AC6.1/en/PRO_Data_processing_Duplicating_environments.html

We do not normally create packages from PROD and move them into the non-PROD environments."

So is the best way to migrate existing workflows (campaigns, etc.), from one environment to another? Create and exporting/importing data packages or refresh?

[florentlb]

Hi,

Following support recommendation is the best thing to do :)

Exporting and importing package is more designed for advanced users who have experience with the solution.

Florent.

[Vipul_Raghav]

Jae Lee wrote...

Hi,

I received this reply from Adobe tech support, when I broached migrating workflows, campaigns, etc.:

"The process that is followed, internally when requests such as this are raised, is to refresh the NON-PROD database with the PRODUCTION database.  This is done by restoring the latest backup into the NON-PROD environment.

Please see the following documentation for more information: https://docs.campaign.adobe.com/doc/AC6.1/en/PRO_Data_processing_Duplicating_environments.html

We do not normally create packages from PROD and move them into the non-PROD environments."

So is the best way to migrate existing workflows (campaigns, etc.), from one environment to another? Create and exporting/importing data packages or refresh?

Hi Jae,

There seems to be a misunderstanding here. Recommended approach is to create data/entity in one system and export it as a package. 

Then move it to another environment by importing it. 

This is something that the business practitioner or the implementation expert will do. Adobe support will not work on the migration, as you'd requested assistance for on the support portal.

Yes, the database refresh aspect is there but it is for once in a while kind of a scenario. Also, there is a cost associated (need to check with CSM), this needs to be planned carefully. Also, such a refresh will actually wipe off the current development work on the system that is being refreshed.

Hope this helps.

Regards,

Vipul

[alexanderb67059]

Hi Vipul,

Just following up on this. When we export packages, should we export them as XML then update them as XML in the target environment/

Is there another easy way that I am missing?

Thanks

[bertc50331664]

Great idea in theory.  Link generates html 404 error.