This isn't prohibited in any way, as long as you don't exceed the rate limits.
However it might be simpler to simply create a new account on the new machine and issue a certificate for the single domain there. It's fine to have simultaneous validity and use of different certificates that refer to the same names.
You can eventually reissue the certificate on the old machine so that it no longer covers the migrated name. @JuergenAuer's reference to --allow-subset-of-names is a possible approach but a more correct option is to renew by running with certbot --cert-name specifying the certificate name and a list of -d options covering all of the names that you still want to be included in the new certificate (and leaving out those that you don't want to be included).