Transform

Merge separate date and time columns into unified ISO 8601 timestamps

Join isolated date and time fields into single standard timestamp columns.

🛡️ Your rows never leave your browser.
Why Onfyt: Converts 12-hour AM/PM times to 24-hour time during fusion so output timestamps conform strictly to ISO 8601.

Interactive Sample Data

idevent_dateevent_timevenue
12026-10-0514:30:00Main Hall
22026-10-0609:15:00Room B
32026-10-0718:00:00Auditorium

How this tool works

Legacy ERP systems, medical equipment logs, and airline schedule exports frequently store dates and times in separate columns—such as a 'flight_date' column holding '2026-10-05' and a 'departure_time' column holding '14:30:00'. However, modern SQL databases (PostgreSQL TIMESTAMP, BigQuery DATETIME) and analytics APIs expect a single composite timestamp (ISO 8601 '2026-10-05T14:30:00Z'). Merging these fields by simple text concatenation often fails because of formatting inconsistencies. Time columns might use 12-hour AM/PM notation ('2:30 PM') or omit leading zeros ('9:15:00'), while date columns might use slashes ('10/05/2026'). Concatenating them blindly produces malformed strings that database ingestion scripts reject. DataFix parses both the date component and the time component, normalizes 12-hour AM/PM values into 24-hour military time, formats dates into standard YYYY-MM-DD, and fuses them into your preferred timestamp syntax: standard ISO 8601 with 'T' separator, SQL standard space separator, or full UTC 'Z' representation. Merging separate date and time fields into standardized ISO-8601 timestamps ensures accurate temporal sequencing in database event logs.

Things that usually go wrong

  • Times without AM/PM (e.g. '2:30') are interpreted as 24-hour time.
  • If the date column uses a non-ISO format, standardise it first.

Edge cases we tested

🧪 12-hour AM/PM time ('12:30 AM' vs '12:30 PM')

Accurately converted to 00:30 and 12:30 respectively.

🧪 Missing time value (date exists but time is blank)

Defaults to midnight (00:00:00) or outputs null based on user setting.

🧪 Times with milliseconds ('14:30:00.521')

Preserved cleanly in final timestamp string.

Frequently Asked Questions

What format is the output timestamp?

ISO 8601: 2024-10-05T14:30:00. This is universally recognised by databases, APIs, and BI tools.

Can I include a timezone?

Add 'Z' for UTC or use the Convert Time Zones tool after combining.

What if the time column uses 12-hour format (AM/PM)?

12-hour format is detected automatically. '2:30 PM' is correctly combined as '14:30:00' in the ISO output.

Can I add a timezone to the combined timestamp?

Yes — select 'Append timezone' and choose the timezone. The output becomes: 2024-10-05T14:30:00+03:00.

What if dates and times are in the same column separated by a space?

Use the Split Date and Time tool first to separate them, then if needed recombine in a different format.

Related tools

Transform

Column to Comma-Separated List

Extract a CSV column and convert it to a comma-separated list for SQL IN clauses or code arrays.

Open Tool →
Transform

Comma-Separated List to Column

Convert a comma-separated, line-separated, or SQL IN list into a single-column CSV.

Open Tool →
Transform

Lines to CSV

Convert plain-text newline-delimited records into structured CSV tables.

Open Tool →