Lynn's solution is going to be your most reliable mechanism, albeit potentially slowest, for doing so.
The problem, in the generic, is a difficult one. Not all statements (MAKE, some SETs) are supported in a CAB like they are in a PStep, nor are Event Actions supported. You have to care about dialog flows, PStep USEs, packaging alterations, etc. You're likely going to have to refactor those to support some of the functionality you need. Depending on your scenario, you could look at doing a PStep USE. Not available under all circumstances, but may help.
Under the right, stringent circumstances, there's one possibility - each PStep is backed by an AB already, which contains the views/statements. You could consider an automated mechanism for severing the link between the PSAD and the PStep, but it would ultimately leave the PStep orphaned and you would have to repackage the AB (as it won't be implicitly packaged in a LM via the PStep that consumes it). It's not a straightforward process by any means.