To move your journal to a new app safely, export everything from the old app while your subscription is still active, open the export to check it, save a copy in a folder you control, import into the new app and spot-check old entries and photos, and only then cancel. Choose plain text, Markdown or JSON exports over PDF. Expect dates, tags, locations and photos to be the parts most likely to break, and expect AI memory not to transfer at all. The whole process takes an evening.
What is the right order to move a journal?
Almost every migration horror story is an ordering problem rather than a technical one. Subscriptions lapse, accounts lock, and the export button stops being reachable at exactly the moment you need it.
- Export from the old app first, while the subscription is still active. Export is often a paid feature, and access usually ends the day the plan does.
- Open the export and read three entries from three different years. An archive you have not opened is a guess, not a backup.
- Store one copy somewhere that is not the new app and not the old one. A folder you back up is the only thing here that is really yours.
- Import into the new app and spot-check the oldest entry, the longest entry, and one with a photo.
- Only then cancel anything. Give yourself a month of overlap; it costs one subscription payment and removes all of the risk.
What usually breaks when you move a journal?
Exports tend to preserve the words and lose the context around them. Knowing which parts are fragile lets you check the right things instead of scrolling hopefully.
| What you had | Usually survives | Often lost |
|---|---|---|
| Entry text | Yes | Rarely an issue |
| Dates and times | Usually | Time zones shift; entries can land on the wrong day |
| Photos and audio | Sometimes | Links break, or media exports as separate unlinked files |
| Tags and folders | Rarely | Flattened into plain text or dropped entirely |
| Location and weather | Rarely | Almost always dropped |
| AI history and memory | Almost never | Nothing standard exists to carry it |
| Formatting | Partially | Headings and lists degrade unpredictably |
Which export format should you ask for?
If you are given a choice, take plain text or Markdown, one file per entry, with the date in the filename. That combination is readable by everything, searchable by your own operating system, and still openable in thirty years by anything that reads text.
JSON is the next best option. It is less pleasant to read, but it preserves structure and any developer, or any competent assistant, can convert it into something else later.
PDF looks reassuring and is the worst of the common choices. It is a picture of your journal. You cannot import it anywhere, search across it reliably, or restructure it. Take it only in addition to something else.
If the only export is PDF or there is no export at all, treat that as the answer to whether you should be storing years of your life there.
What happens to AI memory when you switch apps?
This is the genuinely unsolved part, and it is worth being straight about it. When an app has built up a model of you, the people you mention, the things you are working through, what it has previously asked about, none of that is portable. There is no standard for it and no app that imports another's.
So the memory resets when you move. You can shorten the gap by writing one deliberate entry in the new app that reintroduces the essentials: who is close to you, what you are in the middle of, what you are trying to change. It feels artificial for about five minutes and saves the new tool weeks of catching up.
It is also the reason to be slower about switching for novelty. Moving costs you accumulated context, which is exactly the asset that took the longest to build.
How do you move from Day One, Apple Journal or a notes app?
Day One exports to JSON with media folders, PDF and other formats from its settings, and JSON is the version to keep, because it preserves dates and structure. Apple Journal is not built around exporting large archives, so check the options in your current version before moving years of entries, and copy important entries out manually if needed. Notes apps such as Apple Notes and Google Keep can be exported through their account data tools, such as Google Takeout for Keep, which produces files per note.
Whatever the source, test with ten entries first, including the oldest one and one with photos, before importing everything.
How do you help a new AI journal catch up?
Reflectize is an AI journal that remembers the people, plans and moments you write about, and follows up with questions when the time is right. It is built for iPhone and Android and is launching soon, with a waitlist open now. Like other AI journals, Reflectize builds its memory from what you write in it, so a reintroduction entry helps it start with context: the people who matter, what you are in the middle of, and what you want to change. From there it can follow up on real situations instead of starting cold.
How do you keep an archive that outlives every app?
The habit that makes all of this permanently easy: once or twice a year, export everything and drop it in a dated folder alongside your other important files. Nothing else. No system, no tidying.
This takes about fifteen minutes annually and it changes your relationship with the whole category. You stop being locked in, because leaving costs you nothing. You stop worrying about a company being acquired. And you gain the ability to actually read your own history in one place, which almost nobody with a decade of digital journaling can do.
Treat the app as the place you write and the archive as the place it lives. Apps are temporary in a way a fifteen-year record should not be.
Can I import old entries so they appear on the right dates?
Sometimes, and it is worth checking before you commit, because the alternative is a decade of your life landing in the app under today's date.
Apps that support dated import usually want a specific structure, one file per entry with the date in the filename, or a JSON file with a date field per record. If your export is a single long document, you will get one enormous entry unless you split it first, which is a genuinely tedious job done by hand and a five-minute job for anyone comfortable with a script.
If the new app has no dated import at all, you have a decision to make: keep the archive separate as a readable record and start the new app fresh, or do the conversion work. Starting fresh is a more reasonable choice than it sounds, provided the archive is somewhere you can actually open it.
This piece is part of how to start journaling. Everything you need to begin: what to write about on day one, how long an entry should be, how to pick between paper and an app, and how to keep going after the first week.