I recently moved away from Day One and am now using Obsidian to keep my daily journal. To make that possible, I needed to migrate over a decade’s worth of journal entries into an Obsidian-friendly format.
When I first started using Day One, I wrote about it on this blog and said one of the requirements needed to be
…and stores my data in an open format that I’m confident is future proof and exportable to another system if the need ever arises.
I’m happy to say that worked out well. I don’t know what I’d do if my 20,000+ entries were locked-up in a proprietary format.
This Swift script takes Day One’s JSON export file (and media attachments) and converts each entry into a YAML + Markdown file that is friendly to Markdown editors like Obsidian.
Entries are sorted into folders based on their date with support for multiple entries per day. Media attachments are saved alongside the Markdown files as inline attachments.
Running the script
d1obsidian <path-to-export.json> <some-output-folder>
will create a directory structure like this:
/export-folder/
/2023/
/2024/
/2025/
/2024-01 - January/
/2024-02 - Februrary/
/2024-02-01/
2024-02-01 - 001.md
2024-02-01 - 002.md
some-image.jpeg
another-image.jpeg

Based on the availabe metadata, each entry’s Markdown file will look similar to:
---
uuid: AA7A6A77946547449ED0BBC99349537C
creationDate: 2013-02-13T20:38:54Z
timeZone: America/Chicago
location:
latitude: 37.546
longitude: -77.439
localityName: Richmond
administrativeArea: Virginia
country: United States
weather:
conditionsDescription: Cloudy
weatherCode: cloudy
temperatureCelsius: 3.5
---
Today I went for a run and ate a sandwhich.

It’s worth noting that this script does not exhaustively migrate all fields that Day One supports — mostly because I couldn’t find a complete listing of all the available fields. It also strips out dayone-moment:/workout
and dayone-moment:/location
in-line references from your entires.
And in keeping with open source tradition, there are plenty of other export scripts floating around GitHub and the Obsidian forums, but it was easier to hack this together quickly than try and modify someone else’s to match the output I wanted.