Hi again! Some answers and I hope I’m interpreting your questions correctly. Please feel free to ask for clarification if anything I am saying doesn’t make sense.
Unfortunately I learned that lesson the hard way too, although with a much smaller tree than what you are dealing with. You should be able to keep your existing folder structure (by surname), because RootsMagic will link the media files using the filename.
Unfortunately, the way Ancestry names files when you download them is pretty terrible.
I assume you mean to create a new database by importing a GEDCom file? If it has the old names for the media files, you might first try running the “Fix Broken Links” command in RootsMagic after you create the new database. RM will search for and re-link the files based on the file name. If that works for even a percentage of your files, it could save you a lot of work.
And yes, there are features that allow you to compare databases and copy things from one database to another. I’m haven’t used those much, though, so hopefully others can fill you in on the details.
I usually use the Share => Download command to get the image of the record, then save it in the proper folder using my naming convention. I usually prefer to download JPGs rather than PDFs if they are available. That said, if I’m feeling lazy, I will occasionally just download them using TreeShare. That’s not necessarily easier in the long run, though, since it means that I end up with a file folder full of media that has illegible file names and have to be moved to the correct folder, then I have to clean those files up later.
I will have to check out your Print PDF trick.
I do use it, but it means an extra workflow to rename the media files, move them to the correct folders, and then update them in RootsMagic’s Media file. It’s funny that you find the feature confusing though, because I’m the opposite. TreeShare feels more intuitive to me and the FamilySearch sync confuses the heck out of me.
Neither are super-simple, but they do give you a lot of control over the data that you’re moving back and forth, which is good.
Hope this helps!


