Asana dates wrong in Google Sheets: causes and fixes

Asana dates wrong in Google Sheets? A date one day off or a swapped month and day comes from UTC due times, the sheet's locale or text dates. Each has a fix.

October 21, 2026 7 min read

Key takeaways

A date off by exactly one day means the task had a due time: Asana stores timed due dates in UTC, and cutting off the time can cross midnight.
To shift a UTC time back to New York in October, use =INT(A2-4/24), since New York is 4 hours behind UTC then and 5 in winter.
Day and month swap when the sheet's locale reads day first and the file is month first. Set File, Settings, Locale before you import.
Dates that won't sort or sit on the left of the cell are text. Convert them with DATEVALUE, or with DATE, LEFT, MID and RIGHT.
Asana's CSV import expects US month/day/year dates.

The task is due Thursday in Asana. In the spreadsheet it says Friday. 2 rows down, a deadline of 4 March shows up as 3 April, and the overdue count on the report is off by 6.

Asana dates wrong in Google Sheets™ trace back to 3 causes. A due time stored in UTC that crosses midnight. A spreadsheet that reads month and day in the opposite order. Or dates that arrived as text and never became dates at all.

The fix for any of them takes under a minute once you know which you're looking at. The menu paths below come from Google's and Asana's help pages, read on 21 October 2026.

The short answer

If a date is off by exactly one day, the task had a due time, and the time got converted to or from UTC. Shift it back with a formula.

If day and month trade places, the spreadsheet's locale disagrees with the file. Go to File, Settings, and set the Locale to match the file before you import.

If dates won't sort or add up, they're text. Convert them with DATEVALUE or DATE.

Asana keeps 2 kinds of due date

Asana stores a due date in one of 2 ways, and the difference explains most of this post.

A plain due date has no time. Asana's developer docs call it "the localized date on which this task is due". It means Thursday wherever you are.

A due date with a time is different. Asana's docs describe it as "the UTC date and time on which this task is due". UTC is the world's reference clock, the time in London in winter. A task due at 9pm in New York gets stored as 1am the next morning in UTC.

Start dates follow the same split. So do date custom fields, which can hold a plain date or a date with a time. If your team adds times to deadlines, every one of those dates carries this risk. If nobody does, the off-by-one problem can't happen and you can skip to the locale section.

Screenshot of an Asana project in List view with a Due date column holding single due dates such as 10 Nov and date ranges such as 14 to 28 Oct, beside Priority, Effort (pts) and Budget columns

Off by one day: the UTC shift

Take a real case. A task in New York is due Thursday 22 October 2026 at 9pm. New York is 4 hours behind UTC in October, so Asana stores Friday 23 October, 01:00 UTC.

Any tool that writes the UTC value and keeps only the date shows Friday. Your Thursday deadline moved a day without anyone touching it.

It runs the other way east of London. A task due 9am Monday in Sydney is 10pm Sunday in UTC, because Sydney is 11 hours ahead in late October. Strip the time and the deadline lands a day early.

Asana doesn't document how its CSV export writes dates with times. Open the raw file in a text editor and find a task you know has a due time. If the hour doesn't match what Asana shows you, the file is in UTC.

To shift a UTC date and time back to New York in October, subtract 4 hours. In Sheets, that's =A2-4/24. Wrap it to keep only the date with =INT(A2-4/24) and format the cell as a date.

The catch is daylight saving. New York is 4 hours behind UTC in summer and 5 in winter, so a fixed offset is right for part of the year. For a report that spans the clock change, add a column with the offset per row, or ask the team to drop due times they don't need.

Month and day swapped: the locale

Asana's CSV import expects US dates, month first. Its help says to "use the standard US date format of month/day/year". Asana doesn't document the export format, but month first is the safe guess. Check your file to be sure.

Google Sheets reads dates by the spreadsheet's locale. Google's help says the locale changes the spreadsheet's date, number and currency formatting. A sheet set to the United Kingdom reads 03/04/2026 as 3 April. A sheet set to the United States reads the same text as 4 March.

To change it:

Open the spreadsheet.
Click File, then Settings.
Under General, open the Locale menu and pick the locale that matches the file, such as United States.
Click Save settings.

Do this before you import. Once Sheets has read a cell as a real date, the date stays put, and changing the locale afterwards only changes how Sheets shows it. So import with the US locale, then switch back to your own if you want to see day first.

The time zone menu sits in the same window. Set it to the time zone your team works in. It costs nothing and removes one suspect the next time a date looks off.

Text dates won't sort or add up

The quiet version of the locale problem leaves some dates as text. Under a UK locale, 03/04/2026 becomes the wrong date. But 03/14/2026 can't be the 3rd day of month 14, so Sheets keeps it as text.

On screen these look fine. They just won't sort with the others, and any formula that subtracts them returns an error. A quick tell is alignment. Sheets puts numbers and dates on the right of a cell by default and text on the left.

2 fixes, depending on the mess.

If the locale is now right, =DATEVALUE(A2) turns the text into a date.
If you can't change the locale, build the date by hand. For month-first text like 03/14/2026, use =DATE(RIGHT(A2,4), LEFT(A2,2), MID(A2,4,2)).

The second formula assumes 2-digit months and days. If the file writes 3/4/2026 without leading zeros, SPLIT on the slash first and feed the 3 parts into DATE.

The 3 causes side by side

What you see	Cause	Fix
Due date one day late or early	A due time stored in UTC, then cut to a date	Subtract or add the hours, `=INT(A2-4/24)` for New York in October
4 March shows as 3 April	Spreadsheet locale reads day first, file is month first	File, Settings, Locale, then re-import
Some dates left-aligned, won't sort	Days past 12 kept as text under the wrong locale	`DATEVALUE` after fixing the locale, or `DATE` with `LEFT`, `MID` and `RIGHT`
Total of hours shows as a clock time	Asana exports 1h 30min as 1:30	Format as a duration, or multiply by 24 for decimal hours

Excel has the same 3 problems. It reads a CSV using your computer's date settings. Export Asana to Excel covers the import route that lets you pick the locale per column.

Stopping it at the source

A CSV makes you fix dates every time you export, since every export is a fresh file. That's the strongest argument against a weekly CSV routine, and the Asana CSV export post covers the others.

A sync tool makes the date decision once, for every run. Before you trust one, test it with 2 tasks. Give one a plain due date and the other a due date at 9pm. Sync both and check that the sheet shows the day Asana shows. If the 9pm task moves, ask the vendor which time zone the tool writes in.

Date custom fields deserve the same test, since they can carry a time too. Asana custom fields in Google Sheets covers how each field type lands in a cell.

Frequently asked questions

Why is my Asana due date one day off in Google Sheets?

The task almost certainly has a due time. Asana stores due dates with a time in UTC, so an evening deadline in the Americas or a morning one in Asia and Australia crosses midnight. Shift the hours back with a formula.

Why are the month and day swapped in my Asana export?

Asana's CSV import works in US month/day/year order, and the export likely does too. A spreadsheet with a day-first locale reads those dates the other way round. Set the locale before importing.

How do I change the locale in Google Sheets?

Click File, then Settings. Under General, pick a new Locale and click Save settings. The time zone menu is in the same place.

Does Asana export dates in UTC?

Asana stores due dates that have a time in UTC. Plain due dates have no time and no zone. How the CSV writes the timed ones isn't documented, so check your own file.

What date format does Asana's CSV import need?

US month/day/year. Asana's help says to use the standard US date format for due dates when importing.

Your next step

Make the 2-task test above in a scratch project and check what happens to the 9pm task. If it moves and you can't tell why, send the details through the support page.

Asana is a trademark of Asana, Inc. Google Sheets and Google Workspace are trademarks of Google LLC. Asana to Sheets has no affiliation with either, and neither endorses it.