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 lets you update your processes once they have been published to support continuous improvement. To do so, create a new version of your process. This creates a copy of your process as a draft where you can apply changes or fix issues, test the new version and publish it when it is ready. 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 replaces the existing version of the process with this latest version. New case instances will be on the latest published version of your process. To avoid version mix ups, Bizagi lets you create a new version when there are no other versions in the draft or pilot states. When you create a new version the process owner and the collaborator list remain the same.