Simple Memo and Logseq:
capture, storage and migration
Start by checking which Logseq version you use. OG works with files; the DB version uses SQLite, with different storage and migration steps. Simple Memo serves a separate capture role for text sent to an inbox or configured destination.
First identify OG or the DB version
The official repositories separate file graphs into Logseq OG. Version 2.0.1, released July 13, 2026, is a DB beta. Older guidance about files, Org and plugins should not be applied to DB graphs unchanged.
| Check | Logseq OG | Logseq DB |
|---|---|---|
| Source of truth | Markdown and Org file graphs | SQLite DB graphs, with assets for attachments |
| Text portability | Read files in another editor; check app-specific syntax | Standard Markdown export omits some data |
| Existing features | Check the installed version and plugins | Changes include no Org support; check DB-compatible plugins |
| Before testing | Keep an independent copy of the graph and attachments | Use a noncritical test graph and export the DB plus assets |
Start with journals and Quick add
Logseq uses outliner blocks and references to organize thinking. Start with a short journal entry and add links when they serve a purpose.
The DB guide documents a built-in Quick add command for the current journal. Quick capture therefore does not always require a plugin. Try opening, entering, saving and finding a note on the device you plan to use.
Prepare sync and backup separately
The official README describes DB as beta and the new mobile app and RTC as alpha, and recommends backups because data loss is possible. Enabling sync alone does not protect against every loss or deletion. Start with a small graph that does not contain essential data.
Follow the sync guidance for your version rather than combining file-graph and DB instructions. Verify both that a note reaches the other device and that an independent copy can be read back.
Choose a backup or a Markdown export
In Export graph, choose Export both SQLite DB and assets when you need the database and attachments. Standard Markdown is useful for readable text but does not preserve every property or timestamp; it should not be the only backup.
Keep the original and test Import → SQLite + assets (.zip) in a separate new graph. When converting a file graph, check the lack of Org support, mapped task statuses and limits on multiple queries or embeds.
Inspect six things before migrating
| Check | What to inspect |
|---|---|
| Text and hierarchy | Can you read paragraphs, bullets and child blocks? |
| References and links | Do page and block references open the intended content? |
| Properties and tasks | How were values, dates and statuses converted? |
| Attachments | Can you open the actual PDF, image and audio files? |
| Search and plugins | Do the searches and DB-compatible plugins you need work? |
| Read-back | Can an import into a separate graph reopen the records you need? |
Use this checklist to inspect a migration; it is not a guarantee that every graph converts identically. Keep originals until the checks are complete.
Five steps before changing your workflow
- Record your Logseq version and storage type, then make an independent backup.
- Prepare a small noncritical test graph with text, a task, an attachment and a link.
- Run the six checks above and open an exported copy in a separate graph.
- If combining tools, create one short note and find it in the final Logseq destination.
- Record mismatches and missing features before deciding how to handle your main data.
If you also use Simple Memo
If you regularly review email, capture short text there and copy only useful notes into a Logseq journal. Check the text and its context when copying. Email arrival and saving into Logseq are separate actions; this workflow does not assume automatic appending.
To try a capture entry point, configure a destination in Simple Memo and verify one message. It is not a graph replacement or migration tool.
See the first-email guide and our earlier file-version comparison.
Frequently asked questions
Does every Logseq version store Markdown files?
No. File graphs have moved to Logseq OG; the DB version uses SQLite. Its standard Markdown export does not preserve every property or timestamp.
What should I do before trying the DB version?
Keep an independent copy of the original graph and use a small, noncritical test graph. If attachments matter, export both the SQLite DB and assets, then check importing that copy into a separate graph.
Will my existing plugins work with DB graphs?
Check each plugin. Look for Supports DB? in the official marketplace or the DB compatibility indicator in the app before relying on it.
Does quick capture require a plugin?
The DB documentation describes a built-in Quick add command that sends short notes to the current journal. Check the entry point for your version and device before installing a plugin.
Does official sync eliminate data-loss risk?
Sync does not replace a backup. The official README describes the DB version as beta and the new mobile app and RTC as alpha, with possible data loss and a recommendation to keep independent backups. Check your version and sync route.
Does Simple Memo append to Logseq automatically?
The workflow here means reviewing text received in your email inbox and copying what you need into Logseq. It does not demonstrate automatic writes to a Logseq database or migration of a complete graph.
What was checked
Checked the official repositories, DB documentation and changes, and the 2.0.1 release on September 9, 2026. These steps are not a report of a physical migration completed in this update. The author develops Simple Memo.
On desktop? Scan with your phone