@WastonAdobe- this is a common problem, but doesn't have any really nice fixes if you are using the built-in functionality to import the incoming files.
Most of the fixes would require upstream fixes: e.g.
Change your string delimiter to not include use the problem character (using uncommon characters like pipe "|" can help)
Parse your source data to change the delimiter character before or during export (i.e. single quote to double quote or visa-versa)
Pre-parse the file before import using sed/awk/perl/JS to apply some regex functions to the string (e.g. if the delimiter character does not have a comma before or after it then swap it out with a different quote character - not perfect but might help)
Remove the string delimiter altogether (provided your strings don't contain the column delimiter)
The best method is usually 1 and/or 2 as whoever/whatever is creating the data file should have the responsibility to provide you with correctly formed data.