BCP woes: Unexpected EOF encountered in BCP data-file

So it turns out that the -n and the -N are not what I wanted; I had assumed it used the db metadata to implicitly convert the incoming data, but it looks like it's expecting binary data with that.

I changed it to -c and it worked without issue.