Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Since cPanel/WHM is licensed directly to the public IP of your Droplet, creating a snapshot and then restoring to a new Droplet is most likely going to result in licensing errors or an environment that just does not work (as you’ve indicated) unless you end up with the exact same IP (which is possible, but not guaranteed – it’s also random, so you have no control over it).
That said, when it comes to migrating the best way to handle this is:
1). Setup a new Droplet and get a temporary license, if possible**.
2). Use the built-in migration utility to migrate from one server to another.
3). Modify your DNS accordingly and then test to make sure it’s working.
4). If the DNS is a go, take a snapshot of the old Droplet and destroy it.
** In regards to #1, a temporary license is only possible if that IP has never had a temporary license or a cPanel installation on it. If it has, you’d need to purchase a second license and then cancel your first after successful migration.