Have you looked at the Copy Tree function in EPDM? It will gather up all the file references of assemblies and let you copy the files to an external folder if desired.
But isn't Copy Tree run on assemblies, just like Pack and Go? If I could define a handful of top level assemblies that contained everything, that would be great, but that's difficult to weed out and I've already determined that there are many parts, drawings and assemblies that don't report to anything else yet, so those would be left behind.
The files are all in one folder and seem to be self contained within that folder - they shouldn't be referencing anything external. That being the case, I was thinking I could just copy the folder as-is. There are about 1600 files in the folder.
One simple approach to do this could be to set up a fresh Vault View on the new Server then after logging in use the 'Get Latest Version' command on the Folders you want to 'migrate'. If you then 'Delete File Vault View' and select the option to keep files in the Cache then you will be left with a folder structure as per the vault View and all the files you cached (as the latest version), with all references defined correctly.
If you do just copy the Folder and you have any old versions of any of the files cached there is a chance that you may get an out of date file in your copied dataset.
Hope that helps
Customer Support Manager
I saw that option and was leaning in that direction - except that the Copy To location is just a shared folder; it's not another PDM location (again, not my choice).
That's why I'm thinking that as long as I've done a Get Latest, I should be able to just copy everything from the PDM folder to the shared folder and be done with it. Just wanted to make sure I wasn't missing something.