Symlinking does not look like a good idea to me. hawthorne wrote that his installation was moved to a different server, propably with a newer OS version, different library versions, different (g)cc version, and so on. Even perl itself may have been compiled differently. So, while the pure Perl part of the modules should survive that quite easily, the XS libraries may not be binary compatible and will probably cause segfaults and other unexpected behaviour.

The best bet here is to install all required modules from CPAN, using Perl's cpan utility.

With access to the old server, creating an autobundle on the old server and installing it on the new server should be the easiest way.

Without access to the old server, you need to find the required modules manually. I would start by grepping all existing code for lines containing "use" or "require", followed by extracting the loaded modules, and finally creating a distinct, ordered list of modules. find, grep, sort, and uniq could help, or a little Perl script with File::Find, grep, sort, and a hash of module names. With that list, I start the cpan utility and make it install each and every module on the list, either manually using the cpan utility or by using the CPAN API.

After that, every single application has to be tested, and watched for errors. (Hint: Read the web server's error log.) All modules that are still missing have to be installed, as above.

Alexander