Practical guide
Import Plain-Text Journal Entries into Day One on Mac
Day One’s Mac plain-text importer needs dated entries and clear boundaries. Use the format of the actual computer and the vendor’s sample, then inspect two complete entries; photos, location metadata and weather metadata require a different decision.
Confirm what this route can carry
Documentation checked 11 November 2026: this guide uses the English Day One help documents linked below. Match the platform and controls to your app. Examples are fictional; the application import, sharing or recovery has not been tested here.
Plain-text import is documented for the macOS app. Each entry needs a date stamp. The official guide states that media cannot be imported this way, and location/weather metadata will not be carried over as metadata. A sentence mentioning a place is text; that does not make it a structured location field.
| Material | Plain-text decision | Check before proceeding |
|---|---|---|
| Two written reflections | Potentially suitable | Known date stamps and separate entry boundaries |
| Attached photograph | Not imported through this route | Keep the original media and choose a documented alternative |
| Location/weather metadata | Not carried over as metadata | Decide whether you need the structured fields |
| Unknown date | Not ready to convert by guesswork | Resolve source date meaning first |
On a narrow screen, scroll inside the table. Keyboard users can focus the table region and use the arrow keys.
Read the date format of the actual Mac
Day One says the date format must match the computer’s format. Its example shows Date: June 24, 2016 at 10:59:06 AM MDT; it also gives dd/MM/yyyy HH:mm as a possible computer format. Neither is a universal format to paste into every journal.
Before reformatting many entries, note the date/time format shown by your own computer and compare it with the current vendor example. Keep the source dates and their meaning separately. Changing 03/04 from one convention to another without knowing the original convention can change the event date even if the imported text looks neat.
Sources: [1].
Inspect the boundary on both sides of the text
Entry 1 date
Known date stamp in the computer’s format, then the documented two carriage returns.
Entry 1 text
The complete first reflection, then two carriage returns before the next date.
Entry 2 date and text
Another date stamp, two carriage returns, then the complete second reflection.
Original explanatory diagram.
The guide explicitly asks for two carriage returns between a date and its entry, and between the end of an entry and the next date. Match the current downloadable vendor sample instead of treating this explanatory diagram as an import file. Line-ending conventions and editor display can differ; a visual blank line alone should not replace checking the actual sample and your trial result.
Open the official plain-text guide and its example download. The worksheet below is our inspection record, not a replacement export format.
Run a bounded trial through the documented Mac menu
- Keep the original notes, media and dates unchanged; make a separate two-entry working copy.
- Check both date stamps and both kinds of entry boundary against the official sample.
- Use Day One → File → Import on macOS and select the documented plain-text option available in your version.
- After the trial, locate both entries and compare their full text and displayed dates with the original. Inspect the last sentence of entry 1 and the first sentence of entry 2.
Sources: [2].
No application trial has been performed here. If the two entries are joined or one is missing, stop the larger import and inspect date recognition and boundaries first; a larger file does not resolve a malformed boundary.
Work through a joined-entry problem
Case 1
In a fictional two-entry trial, the imported first entry includes the second date and both reflections. The reader wants to copy-paste the whole journal again. What should happen first?
Show answer and explanation for case 1
Stop and inspect the small working copy’s second date and preceding boundary.
Check whether the second date matches the Mac’s expected format and whether the documented two carriage returns precede it. Keep the imported result and original available for comparison. Repeating the entire source before understanding the mismatch makes it harder to distinguish first-attempt entries from later attempts.
Record what the format leaves behind
Download the blank boundary and field-check record. Record the two original dates, expected entry count, observed dates and text endings. List each attachment or structured field that still needs another route. An import that produces two text entries has not therefore preserved a two-photo journal.
Case 2
A fictional reader imports a reflection that originally had a photo and weather metadata. The text arrives, including the words “rain at the park,” but the photo and weather fields do not. Is this a complete migration?
Show answer and explanation for case 2
Only the selected text may have migrated. The media and structured weather fields were outside this route’s documented scope.
Preserve the originals and choose a supported route based on the source export and target platform. Do not invent placeholder photos or convert the written word “rain” into a verified weather record. Decide what information actually matters before choosing the next migration step.
Sources and further reading
- Day One Help: Importing Data from Plain TextEnglish official documentation checked 11 November 2026. Mac plain-text dates, computer date format, two-carriage-return entry boundaries, and unsupported media/location/weather metadata.
- Day One Help: Importing Data to Day OneEnglish official documentation checked 11 November 2026. Documented platform-specific import options and Mac/iOS menu routes; no automatic conversion or repeat-import guarantee.