How to use date fields and avoid timezone surprises
Use date fields for day-level milestones such as expected close date or renewal date. Use tasks when a specific time matters. Teamopipe stores dates in UTC, so if you're in a timezone west of GMT, a date you enter may display as one day earlier. This is a known issue.
Check one example first
Write down the date you entered and the date shown. Reload the record, check it in app.teamopipe.com, and look at the exported value (exports use YYYY-MM-DD). See date field is showing the wrong day for the full checks.
The workaround
Enter the date one day ahead of what you want to display. If you need May 1, enter May 2. The workaround changes the stored value, so exports and automations see the shifted day. Use it for dates people read on screen, and don't bulk-edit existing dates before checking with us.
Enter and import dates safely
- Enter and import dates as YYYY-MM-DD, for example 2026-11-15.
- Avoid ambiguous values such as 03/04/26.
- Remove times and timezone suffixes from date-only columns.
- After importing, inspect several dates in Teamopipe and in an export.
Date fields to watch
Expected close date, contract start, renewal date and onboarding date. For tasks, always double-check the due date and time after saving.
Example
Renewal date in Berlin: enter 2026-11-15 and it shows 15 Nov. In New York the same entry may show 14 Nov. Compare the entered, displayed and exported values before changing anything.
When to contact us
Contact us if dates shift by more than one day, only some records are affected, or you need help correcting many records. Send your timezone, the field name, the date entered, the date displayed, the exported value and one example record.
Related articles: Teamopipe field types explained, how to prepare a CSV file for import.
Use the chat in the bottom-right corner or the contact form — we typically respond within 4 hours on business days.