The SUSE migration services pre-checks should make sure that "non-activated" services are actually not activated. I've seen where the customer has switched from SUSE Manager back to directly communicating with SCC and updates.suse.com and from SUSEConnect perspective the products were not "activated". However the customer had the related module packages still installed on the host. During the dist migration it was failing due to refreshing of the "non-activated" services.
The SUSE migration services pre-checks should make sure that "non-activated" services are actually not activated. I've seen where the customer has switched from SUSE Manager back to directly communicating with SCC and
updates.suse.comand from SUSEConnect perspective the products were not "activated". However the customer had the related module packages still installed on the host. During the dist migration it was failing due to refreshing of the "non-activated" services.