Considerations for Migrating between Environments
The Click solution includes an embedded Account Key which is specific to the environment for which the solution was provisioned. So each environment that should have a working Click integration will need to have its own unique Click solution installed. However, this can present challenges when migrating customizations between Dynamics 365 organizations.
As a general rule, you can follow normal deployment methods for moving customizations (such as entity forms, views and fields) between environments. And as a final step, import the correct Click solution to overwrite the Account Key if it was brought over from another environment along with the customizations.
Keep in mind that many items created with the Click application—Email Templates, Campaign Automations, Forms, Surveys, Landing Pages, etc.—are not able to be transferred from one environment to another using a Dynamics solutions.
We do not recommend migrating Click entities as part of your own unmanaged customizations. You should always import the managed Click solution you received from Click into the environment for which it was provisioned.