This would be hugely appreciated.

Since this tool was written to help replace essentials, this shouldn't be too bad, but the reason @lithium3141 hasn't written a converter yet is there are many different warp plugins, and writing converters for all of them would be impractical.

The other issue is that essentials didn't have the concept of public/private warps, so when conversion happens, what does a warp become? Are they all public now?

@Lolmen: like @fernferret said, this is unlikely in the short term for a number of reasons. However, I may write up a script to do this in the future; if you can post a snippet of your Essentials warp config file so I can see the format you're converting from, as well as address the public/private issue, I can expedite this process.

All warps are writen in plugins/Essentials/warps/NAME_OF_WARP.yml Content:

yaw: -1.4794006
name: mine
pitch: 7.94986
z: -41
world: world
y: 64
x: -513

Is there one YAML file per user, or just one YAML file with all the warps?

If the YAML files are one-per-user it would make sense to import them as private warps for that user.

No, actually all these warps show up in a list, the list gets displayed to the user, and I think all these warps should be public (since there's not really an owner to the warps.)

Oh, so the filename is the name of the warp? So warp "home" is in plugins/Essentials/warps/home.yml?

The problem now is (which may not be a problem) is that now all warps belong to one user (since in OW warps must belong to a user) so you'd have to input that on the import, then maybe have users go to their warps, then delete them from openwarp at a later time.

Just some thoughs.

I actually have a class which sort of does that (in java, for another plugin). Just use onCommand (something like /warp convert), OP permissions, and let him be owner.