I don't know of any documents that explicitly describe rexster migrations to gremlin server. Here's a rough guide:
1. If you were using Rexster REST APIs then you'd have to convert to Gremlin scripts for Gremlin Server. From what I've seen/heard in production environments very few folks use those routes when they start to build a "real application", so hopefully, there aren't too many of those folks out there.
2. If you were doing Rexster Extensions, you would pull that logic out into a "utility class", build a jar from it, place it on Gremlin Server's path, add the imports to Gremlin Server's yaml, and then call it from gremlin scripts sent to the server. Alternatively you could turn it into a "plugin" and write it in such a way that the imports happen automatically as a result of enabling the plugin in Gremlin Server's yaml. You could see the TinkerGraphGremlinPlugin for an example.
3. If you were using a Rexster init script to build custom functions and such, then nothing much changes - you can do the same with Gremlin Server's init script.
4. If you were deploying a jar of custom functions/classes to Rexster, then nothing much changes, you can do the same with Gremlin Server, though I would consider making it a plugin for convenience and better reusability.