There are three ways of making changes on a website:
Make the change on the live site.
Make the changes on the staging site, when done, make the same changes on the live site.
Clone the site. Make your changes. When done, migrate orders and everything else to the new site.
Use #1 when you feel safe in being able to make a change without breaking the site. All non-coding changes and small tweaks such as adding a code snippet to change the length of blog post excerpts can be done this way.
Use #2 when you need the safety of making sure your changes are not going to break the live site, or when you want to show your changes to the client for approval before applying them to the website.
Use #3 when building a brand new site.
Cloudways staging site feature is new within the last year, so hopefully in the future they’ll make it so that we can push data back without having to worry about overwriting orders and form submissions, but right now it is currently not possible to use staging sites this way.
If you want to experiment around, you can use https://github.com/liquidweb/woocommerce-custom-orders-table to put all of the orders in a separate table, and then you would be able to use Cloudway’s staging site feature to exempt the orders table and push everything else to the main site. When doing this you’ll want to make sure that a) you don’t have any other plugins such as a contact form plugin putting data into the default database tables instead of creating their own table, and b) make sure no one else is making any other changes when you work on the staging site as those changes would get overwritten.