This used to be much easier before Parallels release version 3.0. You might simply try to backup to a Windows or NFS share (see the JumpBox backup and restore instructions) and restore to a fresh Drupal JumpBox on the Fusion server. If you don't want to do that, you can try the following procedure.

With 3.0 you may recall that when you first started your JumpBox it asked you if you wanted to convert your disks to the new parallels 3.0 format. This conversion complicates the task at hand but doesn't make it impossible (I don't think. I am pretty sure I tried this back when 3.0 first came out, but I am working from memory at the moment. So, I can't guarantee that it will work.).

1. First off, if you can, stop the JumpBox and make a complete copy of the Drupal directory.
2. Now with that copy, if you have made any snapshots you must delete them so you only have the current state.
3. Now you can move that copy to the Xserve.
4. Edit the JumpBox.vmx file to point to the correct disk data files ...
   • On the Xserve you will have to dig around and find the new paths to the root, var, and swap data disks. Parallels has moved the root, var, and swap disks. What they do is take the disk data file, say root.hdd, and make a directory with that name, put a config file (ending in .xml) and the old data file (1GB file that looks something like root.hdd-0-LOTSOFJUNK.hds) in it.
   • Edit the root, var, and swap.vmdk files in the disk directory to point to the files you found above. You just replace the "root.hdd", "var.hdd", and "swap.hdd" on the line that looks like 'RW 2097152 FLAT "root.hdd" 0'. Make sure you have the correct relative path to the file, like root.hdd/root.hdd-0-JUNK.hds
5. You should now be able to boot in Fusion