As described in KB Article 10183, you have stored your viflow process model in SharePoint.
This is now to be used with SPM as the master process model.
The prerequisite is that all path specifications relevant for viflow are UNC path specifications.
In addition to checking in and out the client process model in viflow, the files are also checked in and out in SharePoint for the respective user. This means that in the document library, with the stored database, the option "Require document checkout" should be activated in the settings of the document library. Otherwise, several users can open the master and save different versions in parallel.
For the client users, the SharePoint functionality means a small hurdle after checking in the revised process model:
During check-in, the edited local copy of the client file is personalized and moved to the folder of the master process model. The master can then normally import the client from there.
In SharePoint, however, the master will not see this client. The client user must first check in the moved client file in SharePoint. Only then is it visible to all other SharePoint users, especially the master, and can be imported.