Kristen, I'm working on a set of tools to due just that for our organization and will share once I finish my python addin and figure out how to clearly document it for others to use. My issue is, not only are we moving from mapped drives to UNC references, I'm also working on changing all the users profile connections to a common location, and the trickier part is getting shapes to gdb, coverages to gdb, etc. it'll be a week before I'm back at it, but getting closer. Anyway, I'll be happy to share once I get at least most scenarios covered. In any case, probably can't do 100%, but with thousands of mxds, and starting with about 4000 unique broken links, if I can simplify 80% for my agency, that is a great saving.
bottom line, do planning....and keep a list of original path, new path....and old type and new type if moving shapes etc into fgdb. Oh, and I suggest keeping the old structure and creating the new structure.....force a broken-link by renaming the old folder....point to the new.....all before you delete the old structure. Lots of things can be in play when you take this on.....but with technology and best practices changing over the years, what worked great years ago can be improved just be reorganizing into a more logical structure, especially for those that may not have the history to understand why it was done like that in the past. My opinion.
oh, and I think Frank Garofalo is the owner of this group. He maybe can move it to a better location, if Kristen doesn't.
