I provide several tools to help smooth the adoption of HeuDiConv. The Google Cloud shell lesson uses and explains them all, so it is a good way to start. Depending on how comfortable you are with programming and Python, this practice may take a while. This is mostly because you have to write the translator file (so this might be a good time for a break). Google Cloud Shell will save your files.

Stage 1: hdc1.sh runs stage 1 conversion with just a few arguments. It automatically determines the level of nesting in the Dicom directory. It copies the dicominfo file and prepares a generic translator with most of the choices you are likely to need depending on whether or not you are using sessions.

Note: Number of participants

In the tutorial, you are only processing one participant. However, once you have created a translator for your project, you DO NOT need to run hdc1.sh for every participant! Assuming that you create a translator file in stage 2 below, it should work for all your subjects, as long as they all have the same naming conventions. That said, it doesn't hurt to run hdc1.sh, it just creates separate copies of the dicom*.tsv file.

Stage 2: The heudiconv cheatsheet, especially section 2, helps you get through the process of modifying the translator for your own data. In particular, the cheat sheet provides examples of using criteria for different columns in dicominfo*.tsv, some of which are different data types (strings, numbers, booleans, and tuples).
Stage 3: hdc2.sh runs stage 3, and should create the BIDS directory. If you are like me, you may have to do this iteratively as you'll make mistakes and fail to generate some of the expected files.

Watch this ~8.5-minute video demonstrating how to work with the dicominfo*.tsv and heuristic*.py files and introducing the sections in the heuristic file.

DICOM to BIDS 5 (15)