I'm with Kevin on unracking and disconnecting. Racks that I've worked with that are built to ship loaded typically have additional bracing and must be attached to a fixed base (like a pallet) during shipping. Usually the servers have some kind of locking mechanism, too. If you're not moving something that isn't built to be moved loaded don't.
I would add this to Kevin's answer:
Part of documenting is knowing why the various connections and cables are there. You can make all the notes, take all the pictures, etc, that you want to, but at the end of the day if you don't understand why something is there you're running a risk of not knowing what to test to establish, after the move, that you "got everything".
This is a golden opportunity to, as you're documenting the "what's plugged into what" of the move, ask yourself "why is this plugged into this"?
I've had too many cases of the "I'll just patch this here and temporarily change a VLAN assignment" that turns into a semi-permanent configuration that no one documented come back to bite me when moving equipment years later.
Before any equiment goes into a personal vehicle, find out how the company's insurance is handling claims in the event of damage during transport.
Back everything up before you begin moving. Assume that all the equipment will be destroyed during the move because (if you're driving on public roads, at least) it could be. It goes w/o saying that the backup media should not move with the infrastructure gear!