How to merge timelines from multiple platforms

A conversation that matters rarely stays in one place. It starts as a text, continues over email, moves to WhatsApp when someone's traveling, picks up in Slack when it's work-related, and circles back to Instagram DMs for the parts that feel too personal for email. Each platform holds a slice. None holds the full picture.

When you need to understand what happened - for documentation, for legal purposes, for your own clarity - merging those slices into a single chronological view is where the real story becomes visible.

Why merging matters

Individual platform records show you isolated threads. A merged timeline shows you the conversation as it actually happened: across channels, across days, across shifts in tone and topic.

Patterns that are invisible on a single platform become obvious in a merged view. You might notice that formal commitments happen in email but get contradicted in text messages. You might see that the tone of a conversation changes depending on whether it's in a group channel or a private DM. You might realize that what felt like three separate disagreements were actually one continuous escalation spread across two weeks and four platforms.

A merged timeline also prevents gaps. If you only review your text messages, you miss what was said by email. If you only look at Slack, you miss the side conversations that happened in DMs. The full picture requires all the pieces in order.

Step one: gather your exports

Start by collecting message data from every relevant platform. The export process varies:

• iMessage: Third-party tools like iMazing export to CSV or PDF.
• WhatsApp: In-app export (Settings > Chats > Export Chat) produces a text file.
• Gmail: Google Takeout exports email in MBOX format. For specific threads, save as EML or PDF.
• Slack: Admin export for public channels (JSON format), or manual copy for specific messages.
• Instagram DMs: Data download through Settings produces HTML or JSON.
• Facebook Messenger: Download Your Information tool produces HTML or JSON.
• Signal: No export feature. Manual screenshots or transcription required.
• SMS/Android Messages: SMS Backup and Restore app exports to XML.

For each platform, note what format you received and what timestamp format it uses. This matters in the next step.

Step two: normalize timestamps

This is the step that makes or breaks a merged timeline. Different platforms record time differently:

• Some use Unix timestamps (seconds since January 1, 1970).
• Some use ISO 8601 format (2026-03-10T14:30:00Z).
• Some use local time without timezone information.
• Some use 12-hour format, some use 24-hour.

Pick one format and convert everything to it. ISO 8601 with timezone is the most unambiguous: 2026-03-10T14:30:00+11:00 tells you exactly when and where. If you're working in a spreadsheet, a column with this format sorts correctly and avoids confusion.

Timezone differences are the most common source of error. If you're in Sydney and someone is in London, a WhatsApp message sent at 9am their time appears at 8pm your time. The platform may show it in either timezone depending on your settings. When merging, convert all timestamps to one timezone - either UTC or your local timezone, but be consistent.

Step three: build the unified view

Spreadsheet approach. Create a spreadsheet with these columns:

Populate it from your exports. Sort by the Date/Time column. The conversation reassembles itself chronologically regardless of which platform each message came from.

For message content, quote directly when the exact words matter. Summarize when they don't. A message that says "ok" doesn't need to be transcribed verbatim. A message that says "I never agreed to that" does.

The Notes column is for context that isn't in the message itself: "This was in a group chat with [names]," or "This email was BCC'd to [name]," or "Vanish mode was on - this is from a screenshot, not an export."

Document approach. If a spreadsheet feels too clinical, a chronological document works too. Format each entry as:

[Date, Time] - [Platform] - [Sender] Message content here.

This reads more naturally and works better when you need to present the timeline to someone else in narrative form.

Tool-based approach. Receipts automates this merging process - connect messaging platforms or upload exports, and it builds the unified chronological view automatically, then analyzes the combined record for communication patterns. If you're working with a large volume of messages across many platforms, automation saves significant time and reduces the risk of accidentally omitting messages.

Step four: handle what's missing

Every merged timeline has gaps. Acknowledge them rather than ignoring them.

Phone calls and in-person conversations leave no text record. If you know a phone call happened between two messages, note it: "Phone call occurred between [time] and [time] - no transcript available." If you remember the substance, note that too, with a clear indication that it's your recollection rather than a direct record.

Deleted messages may show up as gaps in the timeline or as "this message was deleted" placeholders. Note these. The absence of a message can be as informative as its presence.

Platform switches are worth flagging. If a conversation was in email and then abruptly moved to Signal, the switch itself is information. Note when and why the platform changed, if you know.

What becomes visible when you see everything together

People who build merged timelines for the first time often describe the same realization: the full picture looks different than any individual thread suggested.

You see escalation patterns that were invisible when the heated texts were separated from the calm emails by an app boundary. You see how quickly someone responds on one platform versus another. You see contradictions between what was said in a group channel and what was said in a private DM.

You also see your own patterns - how you communicate differently across platforms, what you address in real time versus what you save for a considered email, where your own responses changed over time.

A merged timeline doesn't interpret any of this. It just shows you the sequence. What you do with that clarity is up to you.