Unix-style line endings on Windows servers

I started a new job and we use Windows servers for everything (local, dev, stage, live), but the new project was committed with Git for Windows with the default setting "use Unix-style line endings for commits" (paraphrasing) selected by the team members, and now any file I open with Notepad shows files with no newlines.

I can use other file editors to read the files (though it's more steps for quick views), but I'm worried that the Unix-style line endings will cause issues with Windows servers. I haven't seen a problem yet with the new or old code (the latter of which had mixed files), and committing with CRLF shows up in the git diff, so it could look bad unless all files are converted at the same time with an obvious message.

Is it going to be worth converting to CRLF? I doubt the system will move to Unix (they're entrenched pretty heavily and use IBM System i infrastructure as their data backbone), but I'm not sure Unix-style line endings will cause a problem.