It seems to; it goes pretty quick though. I should note that the v18 has the latest patch but the config is blank (deleted) in my example. No luck reproducing it with your machine?
I initially misread what you did, and tried to import straight to v19. This resulted in a Slick-C stack, which will be fixed for the next beta.
I suspect the problem you have is that your vusrdefs.e is too large for our macro compiler to compile. You can transfer your keys by importing them, but you will get a Slick-C stack (although in my case the keys seemed to transfer first). In beta 3 this will work.
The code size too large problem has already been dealt with in 19.0, the vusrdefs.e file is split into two files so future users will not get this. Your vusrdefs.e was generated by version 18.0.
We are talking about another possible solution to this, but I'm not sure if we will get it in or not.