NoteThe following discussion is not exhaustive, but is offered to help you determine the need for an encoding converter in the context of importing SFM lexical data into FieldWorks Language Explorer (FLEx).
If your data uses only ASCII character (a-z, A-Z, 0-9, and basic punctuation), then you do not need an encoding converter. You can use Already in Unicode or Windows1252<>Unicode.
If your data uses any diacritics, then you may or may not need an encoding converter.
If you are using a standard Windows® font, such as Times New Roman in Shoebox, then you should use the supplied Windows1252<>Unicode converter because Shoebox does not support Unicode.
If you are using Toolbox, use Project & Language Encodings, click each language and select Modify. Go to the Options tab and click Advanced. If the Unicode (UTF-8) check box has a check mark, then it probably means that your data is in Unicode, so you would choose Already in Unicode as the converter.
If you are using a custom (hacked) non-Unicode font supplied by your branch or someone else, then you will definitely need a custom converter to convert your data into Unicode.
See: SIL Encoding Converters on the Internet at https://software.sil.org/fieldworks/support/technical-documents/.
If you choose the wrong encoding converter, some of your data will look incorrect once in FLEx. In this case, you will usually need to choose a different converter.
NoteThe Bulk Edit Entries features (Lexicon) use processors.
Import Standard Format lexical data
https://scripts.sil.org/cms/scripts/page.php?cat_id=ConversionUtilities