Moving an App to another team

general considerations precondition checks connected entities usually there are publications assigned to apps and in many cases also coupon types assigned to publications when moving an app to another team, the assigned publications and coupon types must also be moved to the same team as publications can be assigned to multiple apps and coupon types can be assigned to multiple publications, there is often a whole bunch of apps, publications and coupon types which must be moved together so when the team of an app is being changed, in a first step these connections are resolved and the complete set of apps, publications and coupon types is displayed check carefully, if you really want to move them all sometimes there is just one coupon type accidentally used in multiple publications consider removing this and receive a much smaller set entitlement server configurations if there are entitlement servers configured for any of the moved apps, they are analyzed as well if all apps which use an entitlement server are moved, the entitlement server configuration is moved as well, otherwise it is stated, that the configuration will be copied in this case, the users who are logged in at the moved app at the not moved entitlement server configuration will be logged out after the move as they are not logged in at the copied server configuration selecting the target team all teams which you have appropriate access to are selectable as the target team to move the app to be careful to select the correct one you may want to temporarily rename a team, if there are multiple teams with the same (or similar) name starting the move operation after selecting the target team, the "move" can be started before we actually start moving the entities, several other checks are performed app templates and entitlement types if any of the moved apps uses an app template or entitlement type which is not allowed in the target team, an error is displayed ask the support team to either allow the app template or entitlement type for the target team or consider selecting another app template or entitlement type then try again to move the app content cloud if any of the contents to be moved to the new team is already published to the content cloud and the target team ist not yet published in the content cloud, an error is displayed publish the target team to the content cloud and then try again to move the app custom domain for web experience if any of the moved apps has a custom domain configured for web experience, the app can't be moved without downtime to move the apps, the following steps need to be followed remove custom domain from app read and understand the documentation at docid 5qp36x0omn32fk oye2ey delete custom domain from field and save remove dns entry for domain, ie remove cname pointing to the current cloudfront domain move app setup custom domain after move as described in the documentation at docid 5qp36x0omn32fk oye2ey this requires dns changes, ie permissions to perform those changes