There are a lot of things to consider and, as Adrian hinted, there is much to be learned by experimenting to start with.
Dealing with media is always one of the biggest considerations when setting this up. The following describes how I deal with it currently.
In my experience there are several ways you can handle media when exporting to TNG. The export plugin gives you a large number of options and TNG seems to handle them quite well as long as your workflow and import media settings mesh with the export choices.
I do maintain a detailed hierarchical folder structure in FH7. It allows me to easily find and manage my media within FH as well as through explorer when required. I do not make data changes in TNG, meaning structure is less important, so I just dump everything into the media folder. When you export from FH if you are using the export plugin, then you have the option to maintain a folder structure or not. If you do not select this option then all of your media gets dumped into the same folder as the exported GEDCOM file with no folder structure. This is what I do. The export plugin will add a suffix or a prefix to the name of each media file based on your preferences. If I remember correctly, it will also warn you if there are any file names which may end up being too long or possibly invalid. Another reason I do not use the option to maintain the folder structure is that the export plugin creates numerous additional subfolders within the existing media hierarchy. I understand the reasoning for it, but it is not the best fit for my current workflow.
Next, I need to ensure that I set the
Extra Option > Manage Keys in the export plugin to
Move to note & _TYPE. TNG uses this on import. Each of my media records in FH is assigned a keyword. I use uppercase keywords. They seem to cause fewer issues with TNG. I use keywords such is
PHOTO, CENSUS, BIRTH, BAPTISM, DEATH, MARRIAGE, OBITUARY, DOCUMENT, HEADSTONE, HISTORY, etc. You can assign more than one keyword to a media record but the uppercase keyword needs to be the first one in the list. That is the one TNG will look at. FH does not seem to like the uppercase
DOCUMENT keyword and keeps resetting it to
Document so I use the Keyword Update plug in to help maintain the keywords.
On the TNG side of things I set the
Photo, Document, History, Headstone, Multimedia paths each to simply
media This is the directory where I transfer all of the media files from the FH export location. This setup is done on the
Setup >> Configuration >> General Settings admin page. Additionally on the
Setup >> Configuration >> Import Settings page I make sure all of the
Local Path settings are blank and the setting for
If no local path match is set to
Import file name only.
The next thing, before I actually ran the first import was, I had to set up collections to correspond to each of the uppercase keywords I use. This is a one-time set up unless you want to change or add new collections. TNG already has default collections set up for PHOTO, DOCUMENT, HISTORY, HEADSTONE. I added others to match my keywords. This can be done on the
Admin >> Media page. Select the
Add Collection button. The illustration shows the options I used to create a collection for the CENSUS keyword. There is detailed help to describe each of the fields. Pay attention to the help advice on the
Same setup as: option, it tripped me up the first time I tried to use it.

- Screenshot 2023-03-09 084025.jpg (42.04 KiB) Viewed 720 times
Once the collections are set up, the import process will automatically place each media item in its proper collection based on keyword. As far as I know there is no restriction on how many collections can be created, but they are added to the dropdown media menus and too many could become unwieldy. There are options to help with that, but they are beyond the scope of this discussion. I have considered organising photo collections based on major family groups (e.g. my maternal and paternal lines and my wife's maternal and paternal lines to start) but I am not sure if it adds any value since collections would still be quite large.
Additionally there are options to set up albums. I do not use them currently because they are TNG specific and need to be rebuilt every time you do a full import. This could be done using custom SQL scripts, which you would run after import. Reading between the lines, I suspect that Adrian may be doing something like that. Maintaining a detailed directory structure for your media (which I currently do not) would also help with this method. It is on my list of things to investigate more deeply in future.
This is not the only, or the best workflow. It is what I have been using successfully for quite a while. As Mike said earlier both TNG and FH are very complicated tools with a lot of options. This makes them very flexible but can also complicate things until you understand the best workflow for you.