The issue we are trying to address: A client has a domain name. We want to transfer the domain from say Enom to OpenSRS. We perform the transfer outside of Blesta, and now we need to update the associated registrar for the client's domain name.

If we currently use OpenSRS for the TLD, or had previously used OpenSRS for the TLD this could be a package change, except that switching packages for services only works if the module is the same. If registrar modules are standardized well enough so that service meta fields are consistent across registrars, then it may be safe to change the package even though the module is different.

So, as a domain only feature, we can add an option (bulk option maybe) to the Domains widget under the client's profile, and under Billing > Domains to change the registrar. Then, we update the package associated with the domain to a package for the TLD that uses that registrar.

If an active or inactive package does not exist for the TLD within the domain manager, it would be ideal if we could create it by cloning the existing package, maintaining the pricing, to a new package using the desired registrar. If we can't create it on the fly, we may need to add a method to edit inactive TLD pricing.

Needs some more discussion/planning.