I tried changing the preference in Fibery but it didn’t help. My date format in the CSV is DD-MM-YYYY, but it imports as MM-DD-YYYY. It imports correctly when there is also DD’s that are over 31, then it know which is the right way. Is there a way to indicate the date format I want it to import as? …

Now you can select date format during the import [image] February 19, 2026 / Filter by to-many relation count, many small improvements Changelog Many quality of life improvements today, hope you will find something to enjoy. Filters: Filter by to-many relatio…

I might be completely wrong about specific description, or misunderstand. But afaik if you import as actual dateform or datatype that could have to do, i.e. be controlled by your user display settings: settings ► preferences ► date format? might also be related to a formatting bug or remainder in…

I have the exact same problem… please advice – this is a kind of a critical issue. As Ron already tried I also have the date format in the user settings set to DD.MM.YYYY (exactly as it’s formatted in the CSV) but it still imports it as MM.DD.YYYY.

Just as a temporary solution: add a line with a date that is over 12 on the DD section of the date, (16.03.2024) then Fibery should understand which format is the right one format to import in. Then delete that entity after import. Lmk if it works for you.

I have many lines with dates that are over 12 on the DD part, or do you mean if the first line has such a date then all the rest is imported correctly? Sorry I cannot try it immediately as I’ve already imported 20K+ entities and it would be a pain to redo everything (can’t bulk delete / import 20K+ …

[image] Eren_Turgut: I have many lines with dates that are over 12 on the DD part Do you mean that some entities (those with over 12 in DD) were imported as you would like and others (those with 12 and under in DD) were imported wrongly?

I believe that was the case, but some entities had empty date fields so I could be wrong and it could be that ALL those with DD 12 and above were left empty and the others imported incorrectly.

[image] RonMakesSystems: Just as a temporary solution: add a line with a date that is over 12 on the DD section of the date, (16.03.2024) then Fibery should understand which format is the right one format to import in. Then delete that entity after import. Lmk if it works for you. Can confirm…

Just in case, it might help someone. I did not manage to import the dates correctly. At the end, I imported them as Text and pasted the values in the date column in the Fibery database.

CSV import wrong date

Get Help

mdubakov February 19, 2026, 1:16pm 10

Now you can select date format during the import

Topic		Replies	Views
.csv Import End Date is 1 Day Early Bugs & Issues	3	44	February 22, 2025
Internationalization on the roadmap? Ideas & Features	8	1951	September 19, 2023
[FIXED] CSV Export Character Conversion Error Bugs & Issues	2	87	December 24, 2025
Allow setting Created Date during import (for historical data migration) Ideas & Features	1	15	April 22, 2026
toText(date) format Get Help	4	286	July 7, 2023

CSV import wrong date

Related topics