Different systems store dates with different internal data formats (FileMaker stores a date as the number of days since 12/31/0000) and thus, there might be an incompatibility that is keeping the data from importing correctly.
I ended up doing something a little but round the houses, but it works.
In fmp I have a date field. I then create a calc field that turns that date into text, like this,
Day(dateCreated) & "." & Month(dateCreated) & "." & Year(dateCreated)
In SQL Server I have a text field that this calc field is imported into. So I now have a date in SQL Server, but as a varchar.
Finally I create a view that points at the varchar and converts it back to a date like this,SELECT *,CONVERT(DateTime, dateCreated, 104) AS dateCreated FROM Orders(note, the 104 works with the fmp calc format that I've shown above).Maybe this will help somebody else trying to do a similar thing.
If you research the way dates are stored in SQL Server, it may be possible to setup a less convoluted way to get this to work by using a calc field in FileMaker that computes a number that can correctly import into a date field in SQL Server.