Cloning your process creates a copy of your process as a draft. It can be copied regardless of the state it's at. Cloning your processes creates a whole new process identical to the process you just copied. This will reuse your process and it's helpful when you need to automatize a process that is similar to one you've already modeled.
We recommend giving the new process a different name to avoid confusions. The cloned process will start in draft state, the owner will be the user who cloned the process and the collaborator's list will be empty.
Bizagi allows you to update your processes once they've already been published to achieve continuous improvement. To do so, you just need to create a new version of your process. This will create a copy of your process as a draft where you can apply the changes it needs, test it and publish it again. Unlike cloning processes, Bizagi recognizes the new version of your process as the same process, even if you change its name. Once you publish the new version, Bizagi will replace your process for its latest version. The new case instances will be on the latest published version of your process. To avoid version mix ups, Bizagi allows you to create a new version once there are no others on draft or pilot states. When you create a new version the process owner and the collaborator's list will remain the same.