@Ragulhm, using this feature, the converted 2GP will have the same namespace as the source 1GP, it will not change.

Can we rename and publish as new packages? Lots of unwanted global classes and objects needs to be removed? Happy to ask customer to uninstall and and upgrade to new 2gp versions. Is it possible?

@@ragulhm If you have a managed package that: 1. Is either not installed in any customer production orgs, or you don't mind having each customer uninstall it and install a new package instead, and 2. The original package either hasn't passed Security Review yet, or you don't mind putting the new replacement package through Security Review, then yes, you can effectively "abandon" the existing package, and create a new 2GP that is entirely separate. To do that, you do not need the Package Migrations feature from the video. That has been doable for many years. Depending on what is in your package, the uninstall & install could be a significant project per customer if there is lots of data to migrate, integrations to configure, customer-created dependencies on packaged metadata, etc.

Thanks a lot for your response, if we change a name space do we need to pay again for security review ?

@@ragulhm think of it this way- you can't change the namespace of an existing package. To "change namespaces" you would need to create a new package that has a different namespace. So yes, this new package would need to go through Security Review in order to be distributed to customers and the Security Review fee would apply.

@AlexRawen thanks for the callout! We've updated the Name and Description of the video to make this clearer at a glance. Apologies for this being unclear originally.