How to export Microsoft To Do to Obsidian (Markdown)

Obsidian

Quick answer

Export your Microsoft To Do lists to Markdown in To Do Mover using either the Obsidian Tasks emoji format or plain text, then copy the .md files into your Obsidian vault and install the community “Tasks” plugin if you want dates, priorities, and recurrence parsed.

Step-by-step

  1. Load your tasks in To Do Mover

    Open To Do Mover's export tool, sign in with your Microsoft account or load a saved todo-backup.json file offline, and verify your export time zone.

  2. Pick Markdown style and file layout

    Select “Markdown” (and keep “JSON backup” checked too). Choose “Obsidian Tasks (emoji markers)” for Obsidian's Tasks plugin or “Plain text” for Logseq and Notion, and decide between one file per list or a single todo.md.

  3. Download and extract the .md files

    Click Export and extract the zip archive if multiple files were generated; by default each list becomes its own .md file.

  4. Copy the files into Obsidian (or import to Logseq / Notion)

    Move the .md files into your Obsidian vault folder. For Logseq, place them in your graph's pages folder; for Notion, use Settings → Import → Text & Markdown.

  5. Enable the Obsidian Tasks plugin if needed

    In Obsidian, open Settings → Community plugins, turn off Restricted Mode if enabled, browse for “Tasks”, and install and enable it to activate date, priority, and recurrence markers.

When Markdown is the right destination

If you want your tasks stored as open, local plain-text files that outlive any single cloud service, Markdown is a strong choice ahead of the Microsoft To Do app retirement on June 30, 2027. Exporting UTF-8 .md files in the To Do Mover export tool lets you drop your lists straight into an Obsidian vault or bring them into Logseq, Notion, or any plain-text editor.

Keep JSON backup checked alongside Markdown (see the Microsoft To Do backup guide) so you retain reminder times, attachment metadata, and raw Graph responses in case you need them later.

Obsidian Tasks style vs. Plain text style

To Do Mover lets you export one <list>.md file per list (the default) or combine all lists into a single todo.md file, in either of two styles:

  • Obsidian Tasks (emoji markers, default): Appends emoji signifiers in the Tasks plugin’s serialization order—priority (⏫ high, 🔽 low), recurrence (🔁), start date (🛫), due date (📅), and completion date (✅)—and turns categories into #tags with spaces replaced by -. Example task lines:
- [ ] Submit quarterly expenses #finance ⏫ 🛫 2026-11-20 📅 2026-11-30
  - [ ] Gather PDF receipts
  - [x] Verify totals
  > Task notes are preserved as indented blockquotes
- [x] Pay utility bill 📅 2026-11-15 ✅ 2026-11-14
  • Plain text: Replaces emoji signifiers with readable parentheses such as (important) (starts 2026-11-20) (due 2026-11-30), which is cleaner for Obsidian without the Tasks plugin, Logseq, Notion, or plain reading.

What is preserved and what is lost

Data item Markdown export result Details
Lists Preserved One <list>.md per list by default, or one combined todo.md
Task title & completion Preserved Standard - [ ] / - [x] checkboxes; multi-line titles flatten to one line
Steps (sub-tasks) Preserved Two-space indented - [ ] / - [x] checklist items
Notes Plain text Two-space indented > blockquotes; rich formatting becomes plain text
Due, start, and completed dates Preserved Restored in your export time zone using 📅/🛫/✅ or parenthetical text
Importance Preserved ⏫ (high) and 🔽 (low) in Obsidian style; parentheses in plain text
Categories Preserved Converted to #tag (spaces become -, # and , removed)
Recurrence Partially preserved Obsidian style writes 🔁 rules; end dates/counts are not supported by Tasks and are added in a blockquote; plain text writes readable rules
Linked resources Preserved Indented [title](url) links; Outlook flagged-email fields have not yet been verified on a live account
Reminder times Lost Neither Markdown nor Obsidian Tasks carries clock-time reminders
Step completion timestamps Lost Checked state is kept, but not the timestamp when a step was checked
Attachments Not included .md files cannot carry binaries; archive them with a JSON backup
My Day and list groups Not available Not exposed by the Microsoft Graph API; all lists export flat

Setting up Obsidian and the Tasks plugin

Once you copy the .md files into your Obsidian vault folder, they appear immediately in your file explorer. If you exported in Obsidian Tasks style:

  1. Open Settings → Community plugins in Obsidian.
  2. Turn off Restricted Mode if you have not enabled community plugins before.
  3. Click Browse, search for Tasks, and click Install followed by Enable.
  4. You can now query tasks across all imported list files using Obsidian Tasks query blocks.

Note that live rendering and query behavior inside Obsidian have not yet been tested end-to-end across every edge case. Try exporting demo data or copying a single list file into your vault first to confirm the formatting matches your setup.

Importing into Logseq or Notion

  • Logseq: Export in Plain text style and copy the .md files into your local graph’s pages folder, then refresh or re-index inside Logseq. Because Logseq is an outliner organized around bullet blocks, checkbox tasks and indented sub-tasks map naturally, though top-level list headers and blockquotes may look slightly different from flat Markdown—test with one or two files first.
  • Notion: Export in Plain text style. Open Settings → Import in the Notion sidebar (or click ••• → More → Import on any page) and pick Text & Markdown to upload multiple .md files at once; each file becomes a Notion page with checkboxes. If you want a filterable Notion database instead of pages, follow the CSV export guide for Excel and Notion.

Post-import checks and troubleshooting

  • Recurring tasks with end dates: Expand “Notes from the export” after downloading to see how many repeating tasks had an end date or occurrence count; Obsidian Tasks will keep generating future occurrences until you remove the 🔁 marker manually.
  • Dates shifted by one day: Re-export after confirming the Export time zone matches the time zone where you normally used Microsoft To Do.
  • Tags split unexpectedly: Spaces in Microsoft To Do categories are automatically converted to -, but punctuation unusual for Markdown tags may need a quick find-and-replace in your vault.
  • Missing tasks or lists: Check whether “Include completed tasks” was enabled and confirm no lists failed to load. For general questions about attachments, shared lists, or revoking access, see the FAQ.

Common questions

Should I choose “Obsidian Tasks” style or “Plain text” style?

Choose “Obsidian Tasks (emoji markers)” if you plan to use Obsidian with the community Tasks plugin for due-date filtering, priority sorting, and recurring tasks.

Choose “Plain text” if you do not use the Tasks plugin or if you are importing into Logseq, Notion, or a standard Markdown editor where readable parentheses look cleaner than emoji markers.

Why do some recurring tasks have a blockquote note telling me to stop them manually?

According to the official Obsidian Tasks documentation, the plugin does not support recurrence rules that end on a specific date (until) or after a fixed number of occurrences.

To Do Mover keeps the base recurrence emoji rule, writes the original end condition into an indented blockquote beneath that task, and lists a warning in the export summary so you know when to stop it manually.

How do I bring the exported Markdown files into Logseq or Notion?

For Logseq, export using the Plain text style, copy the .md files into your local graph's pages folder, and click Refresh or re-index your graph in Logseq.

For Notion, open Settings → Import (or click ••• → More → Import on any page) and choose Text & Markdown to upload one or more .md files as Notion pages. If you want a Notion database instead of pages, export CSV rather than Markdown.

Sources

Ready to export your tasks?

Everything runs locally in your browser. Start with a lossless JSON backup or try the demo first.