Add or fix a service
Every service is one YAML file on GitHub, so adding or fixing one is a few lines and a pull request. Or just open an issue.
Report a mistake or a missing service
Something's wrong
Every service page ends with a Suggest an edit link, which opens the form with the page already filled in. Or fix an entry from here. A link to the service's own docs, or what happened when you tried it, is all the proof it needs.
Something's missing
Suggest a service with its website and anything you've found on how its export works. Fancy writing it up yourself? Read on.
Add a service yourself
- Copy a service from the same category as yours in
data/services. Notion and Aegis are the fullest, so they're the best to start from. - Name the file after the service, lowercase with dashes. It's the id and the address, so
notes/obsidian.ymlis/notes/obsidian. - Fill it in from the service's own docs, then run
npm run validate, which points at any line that's wrong. - Open a pull request titled like
feat(data): add Logseq, orfix(data): refresh Notionfor a re-check.
What goes in a service file
name: Obsidian
website: https://obsidian.md/
# 160 characters at most
description: A notes app that keeps everything as Markdown files on your own device.
deployment: local # local, cloud, hybrid or self-hosted
platforms: [windows, macos, linux, android, ios]
export:
- id: vault
name: Copy your vault folder
method: folder
formats: [markdown, markdown-frontmatter]
steps:
- Right-click a note and choose Show in system explorer.
- Go up to the top folder of your vault and copy the whole thing somewhere safe.
data:
included: [text, attachments, links, tags]
excluded: [history]
unknown: [dates]
limitations:
- Wikilinks are Obsidian's own syntax, so other apps may show them as plain text.
docs: https://help.obsidian.md/data-storage
import: [] # same shape as export
verification:
status: documented
checked_at: 2026-11-20export and import are lists, one item for each way out or in. data says what comes with it, using the ids in the category's list, and unknown is a perfectly good answer. Nobody writes the moves between apps -
they're worked out from both sides, so getting formats and data right is what gets them right.
Point an editor that speaks JSON Schema at /schema/service.json (VS Code with the YAML extension, say) and it'll suggest every field as you type. There's one for formats and one for categories too.
The contributing guide explains each field, plus formats, categories and working on the site itself.