Importing from other apps
Notes from another notes app come into Lines from Settings → Export and Import, where each app has a group of its own saying what to export from it and how. Each is a plugin, on to begin with; turned off, its group leaves Settings, and what it brought stays. Markdown, LaTeX, CSV and Excel files of your own are imported with Import Files… in the same place, as is Lines' own export, its .zip bringing its notes back with their pictures and files; the Library's bookmarks and Readwise in Settings → Library (Library).
How an import goes
- Choose what the app exported: a folder (an Obsidian vault, a Logseq graph, Bear's Markdown), or files (Bear's backup, Notion's export, Evernote's notebooks, a ZIP; a ZIP of nothing but ZIPs, as Notion splits a large export, is unpacked in turn: below). Nothing is written yet, and nothing in it is run: its notes are read as text.
- What it would do comes first: how many notes, attachments and folders, and on lines of their own, what won't come across as it was, each kind with how many and a few examples (
^37066d (Plan)): what's kept as text because Lines has nothing like it, and what's left out. Notes imported from it before are left out too, and said so, with which (below). - Import (focused, so Enter imports) copies the pictures and files the notes show into Lines' attachments, then makes the notes a few hundred at a time, with a bar showing how far it's got; Stop stops either, keeping what's made (stopped while copying, no note is made, and it says so). Ten thousand notes take a few seconds. Closing Settings doesn't stop it, and opening it again shows how it's going, or how it went.
- What it did, with what didn't come across said again, and Undo Import, which moves every note it made to the Trash (but one you've changed since, which is yours now). Nothing an import made is ever deleted outright: empty the Trash for that. Choosing something else to import keeps the last import's Undo, under what the next would do; an import with nothing to bring can't be started, so it never takes that Undo's place.
What carries over, from any app:
- Titles. A note's title is its first line (Linedown), so a note whose text doesn't start with its title as a heading gets one:
# Plan. - Text, in Linedown: what the app writes that Lines has too is translated into Lines' way of writing it; what Lines has nothing for stays as readable text, and is counted.
- Folders. Lines has tags rather than folders, so with Tag notes with their folders on (as it is to begin with), a note in
Projects › 2026is tagged#projects/2026, a tag in a tag in the sidebar. The tag goes on the note's last line, with its other tags. - Tags, nested ones too, as
#tagsin the note's text. - Pins, and the trash. A note pinned or bookmarked there is pinned here; one in the app's trash is in Lines' Trash.
- Dates. When each note was made and last changed, from what the app keeps (a note's properties, or its file's date).
- Attachments. Pictures and files the notes show are kept as Lines keeps any (Linedown), by their content: a file shown by several notes, or imported before, is kept once. A file no note shows is left out, and said so.
- Links between notes become wiki links (
[[Plan]],[[Plan#Goals|the goals]]), which Lines draws as mentions. A link to a note that isn't there stays one, which Lines offers to create.
ZIPs, and how big an export can be
A ZIP in a folder chosen is one of its files, like any other, never unpacked: only a ZIP chosen as a file is (Bear's backups and TextPacks are ZIPs too), or a folder of nothing but ZIPs (an export in parts, unpacked once; TextPacks, each its TextBundle), and a ZIP of ZIPs. A ZIP is read into memory, so it can be up to 2 GB, and what's in it can unpack to 2 GB all told; for a bigger one, unpack it and choose its folder, whose files are read one at a time, with no limit. A file in a ZIP that would unpack to more than 256 MB, or that's packed more than 100 times over (as no real file is, only one made to fill memory), is left out, and said so, as is a ZIP in parts that can't be read. ZIPs of more than 65,535 files (ZIP64) are read whole.
Importing again
Importing the same export again adds only the notes that aren't here yet, and says which are (a few by name): Lines keeps, with each note it imports, where it came from (the app, the note's id there and its name there), in the note's own record rather than its text. It's written in the header Lines keeps above a synced note's text (Sync) as source: {"app":"obsidian","collection":{"id":"9c2e…","name":"Vault"},"id":"Projects/Plan.md","name":"Plan"}, so it goes to your other devices too, and isn't in an export. A note you've changed since isn't changed again, nor brought back as a second copy. One in the Trash counts as not here (an import undone, say), unless it was in the other app's trash too. A conflicted copy sync makes of an imported note doesn't say where it came from: only the note does. A locked note keeps only a hash of its id there, and not its name there (Sync): importing again still knows it, but links brought with it don't find it by its old name once it's renamed.
Some apps' notes have ids of their own everywhere (Bear's). An Obsidian vault's are only its notes' paths, which another vault can have too, and a vault has no id Lines can read. So each vault gets an id of Lines' own when it's first imported (collection above), and when one is chosen that may be a vault imported before (the same name, or notes with the same paths, as when it's been renamed or moved) Lines asks: The same as "Vault", imported before is on to begin with, and says how many of its notes have the same paths. On, what's here already is left out; off, it's another vault, and all of it is imported.
Links, once a note's renamed
A mention finds a note by its title (Linedown), and renaming a note doesn't change the mentions of it. Links brought from another app still find a note renamed in Lines by the name it had there: in a note imported with it (from the same vault), [[Plan]] finds the note imported as Plan after it's retitled "Q3 plan", as long as no note is titled Plan; of two once called Plan, the one edited last. In a note of Lines' own, [[Plan]] finds only a note titled Plan, or offers to create one.
Obsidian
What to choose: a vault is a folder of Markdown files, so there's nothing to export: choose the vault's folder with Choose Vault Folder…. To find it, open Obsidian's vault switcher (the vault's name, at the bottom of the left sidebar) → Manage Vaults, or right-click a note → Reveal in Finder (Show in system explorer on Windows and Linux).
What comes across:
| In Obsidian | In Lines |
|---|---|
A note, Projects/Plan.md | A note titled Plan, tagged #projects |
| Properties (front matter) | Properties, as they were, but tags:, which become #tags in the text. aliases: and the rest stay properties; Lines reads them the same way |
[[Plan]], [[Projects/Plan]], [[Plan#Goals]], [[Plan|the plan]] | [[Plan]], [[Plan#Goals]], [[Plan|the plan]], to the note Obsidian would open: by its path in the vault, from the note's folder, or the shortest path ending in it |
Markdown links to notes, [the plan](Projects/Plan.md) | [[Plan|the plan]] |
![[photo.png]], ![[photo.png|300]],  | , : the picture, kept in Lines, at its width |
![[Report.pdf]], ![[talk.mp3]], [[Report.pdf]] | [Report.pdf](../attachments/….pdf): a file's card, or a player for audio and video |
| Pictures and files wherever the vault keeps them (its attachment folder setting, a folder of each note's) | Found as Obsidian finds them, by their name |
> [!tip] Title callouts | Lines' callouts (:::info icon=lightbulb), the title in bold on their first line; note, info, tip, success, example and the like as info, with Obsidian's icon; question; warning; danger, bug and failure as error. Nested ones nest. One of a kind Lines doesn't know is a card of its name. Folding ones are open |
==highlight==, #tag, #nested/tag, $math$, ```mermaid, tables, tasks | The same: Lines writes them alike |
%%comment%% | <!--comment-->, Markdown's own: faint in Lines, and not shown by other Markdown apps. One within text ends in its paragraph (or heading, or table cell), or its %% stays text, and is said so; one that starts a paragraph runs on to the next %%, past blank lines too. One that runs past a code block, or holds what would end an HTML comment (-->), is kept as written, and said so |
A bar in a table: [[Plan|the plan]], ![[photo.png|300]], escaped | Every bar the import writes in a table escaped, |: a link's, a Markdown link made a wiki link ([[Plan|the plan]]), a picture's width (), so the table keeps its columns |
| Bookmarked notes (and starred, in older vaults) | Pinned |
Daily notes, named as Daily notes' settings say (2026-11-14) in their folder, or any note named like a day | date: 2026-11-14, so it's on the Calendar on that day |
Notes in the vault's .trash | In the Trash |
created: and updated: properties (or date created, modified…) | When the note was made and changed; otherwise its file's date |
Code is left as it is, read as Lines reads Markdown: fenced and indented code blocks, in lists and quotes too, inline code, math and HTML. A link, an embed or a %% in them stays as written; so does a %% in a link ([50%% off](Sale.md), [[Sale|50%%]]).
Links never lead into the vault's trash (.trash), as in Obsidian: only its notes are imported, into the Trash; its pictures and files aren't.
Kept as text, and said so: block ids (^37066d; Lines doesn't link to a line), links to a heading in their own note ([[#Goals]]), tasks with a status Lines doesn't have (- [/], - [-]), Dataview queries (kept as their code), cssclasses (kept as a property, which Lines doesn't use), properties Lines can't read (a key in quotes, say: kept as a YAML code block at the note's top), and links to files that aren't in the vault (kept as written).
Made something else, and said so: a note shown in another (![[Recipe]]) is a link to it, as Lines doesn't show one note in another.
Left out, and said so: files no note shows (a canvas, a picture nothing uses), and Obsidian's settings, workspace and plugins (.obsidian).
Notes with the same name in different folders are both imported, and said so: Obsidian tells them apart by their paths, but Lines finds a note by its title, so a link to that name finds the one with a type, then the one edited last (Linedown).
Where it's read: in a browser (and the apps), with the folder's files read only as text, never run, and nothing sent anywhere. The code is in src/plugins/obsidian/: vault.ts reads the vault, markdown.ts its notes.
Bear
What to choose: in Bear (on the Mac), File → Backup Notes… saves a .bear2bk file: choose it with Choose Backup…. A backup has everything, and keeps which notes are pinned, archived or in Bear's trash, and when each was made and changed. Or export notes with File → Export Notes… as Markdown or TextBundle, with Export attachments on, into a folder, and choose that folder with Choose Export Folder…: notes exported that way are dated by their files, and have no pins. TextPacks (.textpack) and ZIPs of either can be chosen as a backup.
What comes across:
| In Bear | In Lines |
|---|---|
| A note, its first line its title | A note, titled the same |
#tag, #nested/tag | The same |
#tag of several words#, #work/next steps# | #tag-of-several-words, #work/next-steps: Lines' tags have no spaces (said so) |
#tag# | #tag |
==highlight==, ~~strikethrough~~, tasks, tables, code, $math$ | The same; a table right under a line of text gets a blank line before it, which Markdown needs |
~underline~ | <u>underline</u> |
[[Note]], [[Note/Heading]], [[Note|text]] | [[Note]], [[Note#Heading]], [[Note|text]] |
A link to a note, bear://x-callback-url/open-note?id=… | [[Note|text]], by Bear's id of the note |
Pictures and files (assets/, or a folder beside an exported note), with a size: <!-- {"width":320} --> | Kept in Lines, , the size its width |
| Pinned | Pinned |
| Archived | Tagged #archived, as Lines has no archive (said so) |
| In Bear's trash | In the Trash |
| When it was made and changed | The same |
Left out, and said so: locked notes, which can't be read without Bear (unlock them there, and back up again), and files no note shows.
Kept as they are, and said so: links Bear shows as previews (<!-- {"preview":"true"} -->) are links, and links to pictures or files that aren't in the backup are kept as written.
Bear's older markup (Bear 1's "Polar Bear" ::highlight::, *bold*, /italic/) isn't translated: Bear 2 writes Markdown. The code is in src/plugins/bear/: backup.ts reads the backup or export, markdown.ts its notes.
Logseq
What to choose: a graph is a folder of Markdown files, so there's nothing to export: choose the graph's folder (the one with pages, journals and assets in it) with Choose Graph Folder…. Logseq shows where it is in its left sidebar's graph menu → All graphs.
What comes across:
| In Logseq | In Lines |
|---|---|
A page, pages/Plan.md | A note titled Plan (or as its title:: says) |
A namespace's page, Projects/Acme (Projects___Acme.md, or Projects%2FAcme.md as older versions wrote it) | A note titled Projects/Acme, as links name it, tagged #projects |
A day's journal, journals/2026_11_14.md | A note titled as Logseq titles it ("Nov 14th, 2026", or as :journal/page-title-format says), with date: 2026-11-14, so it's on the Calendar, tagged #journals |
Page properties, type:: book | Properties, type: book; tags:: become #tags in the text, title:: is the title |
| The outline | A list, nested as it was: an outline stays one. A page that's clearly prose (below) is paragraphs |
- # Heading blocks | Headings, what's under them after them |
TODO, LATER; DONE | - [ ]; - [x] |
DOING, NOW, WAITING | - [ ] DOING …: open, the state kept as a word (said so) |
CANCELED | - [x] ~~…~~ (said so) |
[[Page]], [text]([[Page]]), #[[two words]] | [[Page]], [[Page|text]], #two-words (said so) |
((block reference)), {{embed ((…))}} | The block's text, and a link to its page if it's another's (said so): Lines doesn't link to a block |
{{embed [[Page]]}} | [[Page]] (said so) |
{{video …}}, {{youtube …}}, {{tweet …}} | The link |
^^highlight^^ | ==highlight== |
{:width 320} | Kept in Lines, at its width |
Favorites (:favorites in config.edn) | Pinned |
Prose or a list: Logseq writes every line as a block, so a page of paragraphs reads as a list of them. A run of blocks at a page's top (between headings) becomes paragraphs only when it's clearly prose: each block a sentence or more (40 characters or longer, ending as a sentence does), with nothing under it, no task, no properties Lines would keep; or a page of one such block alone. Anything else, a block with blocks under it, a short item, a task, stays the list it was, so nothing that was an outline is flattened.
Kept as text, and said so: a block's own properties (owner:: Ada, as Lines' properties are a note's; but its id::, which references used, and collapsed::, which is Logseq's), task priorities ([#A]), SCHEDULED: and DEADLINE: dates, and queries and other macros ({{query …}}).
Left out, and said so: empty pages (Logseq makes some itself, as Contents, and a journal for each day opened), pages written in Org mode, and files no page shows (an unused asset, a drawing, a whiteboard). Logseq's own folder (logseq/: its settings, backups and versions) isn't read but for config.edn.
The code is in src/plugins/logseq/: graph.ts reads the graph, outline.ts its pages' outlines, dates.ts its journals' names.
Notion
What to choose: in Notion, Settings → Export all workspace content (or a page's ••• menu → Export), with Markdown & CSV as its format, Include subpages and Create folders for subpages on. Choose the ZIP it downloads with Choose Export ZIP…, as it is: a large export is a ZIP of other ZIPs, which Lines unpacks too. Or unpack it and choose the folder with Choose Unpacked Folder…: a large export's folder of ZIPs, unpacked once, is unpacked the rest of the way.
What comes across:
| In Notion | In Lines |
|---|---|
A page, Plan 1a2b….md | A note titled Plan, without the id Notion adds to names |
| A sub-page, in its page's folder | A note of its own, linked from its page as in Notion, tagged with the pages it's in (#home), as sub-pages are folders here |
A link to a page, [Plan](Plan%201a2b….md) | [[Plan]], to the note, whatever the page is renamed to (Notion's ids are its own everywhere, so importing again knows each page) |
A database, Reading List 3c4d….csv and its folder of rows | A note titled Reading List, with a table of its rows (@type.reading_list(Author, Status, …), Linedown) |
| A database's row | A note of the type named after the database (type: Reading List), its columns its properties: relations as links to their pages, dates as Lines writes them (November 14, 2024 9:30 PM → 2024-11-14 21:30), the rest as written; its Created and Last edited columns its dates. A property's name and a type's have only letters, digits, spaces, _ and -, so the rest is left out of them, and said so: Price ($) is Price, 📚 Reading List the type Reading List; two that come out the same are told apart (Done, Done 2), and a column called Type is Type 2. A database whose name has nothing left is no type: its note lists its rows, and says so |
| Pictures and files, in a page's folder | Kept in Lines |
Callouts (<aside> 💡 …, on one line or several) | Lines' callouts, info, or warning, error and question by their icon (⚠️, ❗, ❓), the icon kept as text |
Toggles (<details>) | Their title in bold, what's in them under it, open (said so) |
| To-dos, headings, lists, tables, code, equations | The same |
Said so: links to pages that aren't in the export (kept as written), toggles, files no page shows (left out), and pages with the same name (Lines finds notes by title, so a link to that name finds one of them).
Notion's Markdown export doesn't say when a page was made, so pages are dated when they were exported, but rows, by their Created and Last edited columns where the database has them. The code is in src/plugins/notion/: export.ts reads the export and its databases, markdown.ts its pages.
Evernote
What to choose: in Evernote, right-click a notebook → Export Notebook… (or select notes → Export Notes…) and choose ENEX (.enex) as the format. Choose the files with Choose .enex Files…: several notebooks' at once, if you like.
What comes across:
| In Evernote | In Lines |
|---|---|
| A note | A note, titled as it was ("Untitled" for one without a title), dated when it was made and changed |
| Its notebook (the .enex file's name) | A tag of its name, with folder tags on |
| Tags | Tags (big ideas as #big-ideas) |
| Its text (ENML, Evernote's HTML) | Linedown, read as Lines reads a feed's HTML (Library), where nothing in it runs or loads: paragraphs, headings, bold, italics, links (to the web and mail), lists, quotes, tables, pictures from the web. Scripts, forms and the like are left out, and its words are only words (a # in them isn't a tag) |
Its files (<en-media>, found by their MD5) | Kept in Lines, pictures at their width; a file its text doesn't show, under it |
Checklists, old (<en-todo>) and new | Tasks, ticked where they were: each box a task wherever it is in a line, checklists nested as they were, in bullet lists too |
| Code blocks | Code blocks |
| Highlights | ==highlights== |
| Author, source URL | author: and url: properties |
| A reminder not done | due:, so it's on the Calendar |
An encrypted part (<en-crypt>) | Text saying so, with its hint, and the encrypted text as Evernote wrote it, in code (said so): Lines can't decrypt it, and nothing is lost |
Evernote's .enex has no id for a note, so importing again knows a note by its notebook, title and when it was made, whichever notebooks are chosen with it.
Read safely: an .enex that declares entities (outside its notes' text) isn't read at all, so nothing is fetched from elsewhere or multiplied ("billion laughs"); Evernote's own declare none, and one that does is said not to be readable. Its files, in base64, are held to the same limits as a ZIP's (above): 256 MB each, 2 GB all told, any past that left out and said so. An .enex over 2 GB, or one that can't be read, is left out and said so, when other notebooks are chosen with it. In a table, a picture's width keeps the table's columns (). The code is in src/plugins/evernote/: enex.ts reads a notebook, md5.ts names its files as Evernote does.