As far as I know you can trigger scripts from Playmaker and vice versa. So you don't need to lose your scripts and redo them in Playmaker if you don't want to. But as KellyRay said, it isn't too hard. That is how I work, I look at scripts over the internet of stuff I am not sure how to do and translate it to Playmaker.
A quick search yielded this:
and
Perhaps they could give you an insight on the process and hope they help in anyway.
That said, if you want to translate code into playmaker; each code line might end up as an action. So for example if you have a line of code that says something along the lines of (I am bad at coding so bear with me):
if keypressed "w" == true
{
object.transform.translate (x, 2, 0);
}
Then the equivalent of this in Playmaker terms would be an FSM with 2 states:
1- A state with the "Get Key Down" action and has the "W" letter as the key
2- A state with the "Translate" action with the value of 2 at "y".
An event is required to transition from state1 to state2 so you'd need to create an event called "key pressed" for example. Then hook everything up.
If you want to be more "OOP" then instead of writing the "2" in the "Translate" action, you'd then create a variable called speed for example and then give it the value of "2" and edit the translate action in state2 to point to the variable rather than the value itself.
Hope that helps.