You can replace an external task manager like Todoist or Things with Obsidian, and for anyone whose tasks are tied to notes and projects it is often a better home, because the task sits next to the material that gives it meaning. The honest catch is that Obsidian does not do this out of the box: you assemble the workflow from a capture habit, one task plugin, and a way to decide what to do first. Get those three right and you have a task manager that lives inside your knowledge base, with your data as plain files you own. This walks through the complete capture-to-completion workflow, where it beats a standalone app, and where a dedicated task manager still wins.
The reason people try this is consolidation. Keeping tasks in a separate app means your to-do about a project lives away from your notes about that project, so you context-switch between two tools and two sources of truth. Pulling tasks into the vault collapses that into one place.
Why moving tasks into Obsidian is not automatic
Obsidian treats a task as what it literally is: a Markdown checkbox. The core app can render and toggle - [ ] lines, and its newer Bases feature can tabulate note properties, but it has no native concept of a due date, a priority, recurrence, or a today view. A standalone task app gives you all of that on install; Obsidian gives you the raw material and expects you to add the rest through community plugins. That is the trade at the heart of the switch: more control and ownership, in exchange for assembling the system yourself.
This is why a naive move fails. People export their Todoist tasks into a note, see a flat checklist with no dates or reminders, and conclude Obsidian is worse. It is not worse; it is unconfigured. The workflow below is what turns a pile of checkboxes into a real task manager. If you are still deciding whether the vault can hold tasks at all, does Obsidian have task management covers the native limits in full.
The three-part workflow
A working replacement has three parts, and skipping any one is where setups break down.
First, capture. Decide where new tasks land: usually your daily note for quick capture, or the relevant project note when the task belongs to a project. The point is a consistent, low-friction place to write a task the moment it appears, so nothing is lost.
Second, structure. Install the Tasks plugin, which adds due, scheduled and start dates, recurrence, and six priority levels to those checkboxes, plus a query language that gathers matching tasks from across the vault into a live list. This is what replaces the dates-and-reminders layer of a standalone app.
Third, decide. This is the part people forget, and it is the part a standalone app quietly did for you by showing a focused “Today” view. A Tasks query gives you a list sorted by a field; it does not weigh which of those tasks matters most given everything around it. A deciding layer closes that gap: ZPXE reads the tasks the plugin surfaces and ranks today’s priorities on-device, with a visible reason for each, so the focused daily view you relied on in Todoist has an equivalent in the vault. The mechanics of the wider stack are in Obsidian task management.
| Layer | Standalone app gives you | In Obsidian you use |
|---|---|---|
| Capture | a quick-add box | your daily note or project note |
| Dates and recurrence | built in | the Tasks plugin |
| A focused today view | built in | a Tasks query, then a ranking layer |
| Where data lives | the vendor’s cloud | plain files you own |
A worked capture-to-completion example
Say a task arrives: email the supplier about the delayed order, due Friday, high priority. In a standalone app you would quick-add it with a due date and a priority flag. In Obsidian, you write it in today’s daily note as a checkbox, and use the Tasks plugin’s create-or-edit command to set Friday as the due date and mark it high, which writes the correct syntax for you. It now appears in any query filtering for due-this-week tasks, grouped with the rest of your week.
On Friday morning, your today query surfaces it alongside everything else due, and the ranking layer puts it near the top because it is due today and high priority, showing exactly that as its reason. You open the linked supplier note, act, and tick the checkbox, which writes a done date and, if the task recurred, generates the next instance. Capture, structure, decide, complete, all inside the vault, with the task never having left your machine.
The one thing you will genuinely miss: reminders
It is worth being blunt about the biggest gap, because it is the thing that sends people back to a standalone app. A dedicated task manager pushes a notification at the right time; Obsidian does not, by default, interrupt you. Your today view is something you open, not something that pings you. For many people that is a feature, since a day driven by notifications is a day of interruptions, and research on knowledge work puts the cost of task switching as high as 40% of productive time. For others, especially anyone who relies on time-of-day reminders for appointments and hard deadlines, it is a real loss.
The honest workaround is to keep the two roles separate. Let a calendar own time-based reminders, the things that must happen at a specific hour, and let Obsidian own the ranked list of what to work on when you sit down. Trying to make the vault replace push notifications fights the tool; pairing it with a calendar for the genuinely time-bound items gives you both. The result is a system where deciding what to do next lives in the vault and being interrupted at 3pm lives in your calendar, which is a cleaner division than a single app pretending to do both.
Common mistakes when switching
A few predictable missteps account for most failed migrations. The first is importing everything at once, which recreates the overwhelm you were escaping; move your most-used projects first and archive the rest. The second is skipping the deciding layer and expecting a raw Tasks query to feel like Todoist’s Today view, when a sorted list is not a ranked one; the difference is covered in why productivity apps fail. The third is over-building queries before the habit exists, producing an elaborate dashboard you stop opening, the failure mode covered in don’t give up on Obsidian tasks yet. Start with one capture spot, one today query, and one ranking pass, and add complexity only when a specific need appears.
Trade-offs, honestly
Replacing a standalone app has real costs worth naming before you commit. You lose the polished mobile quick-capture and the reminder notifications that a dedicated app does better; Obsidian mobile runs the same plugins but is a notes-first interface, not a two-tap capture widget. You take on setup and a little maintenance, since you are assembling the workflow rather than installing it. And shared or collaborative task lists are not Obsidian’s strength, so a task list several people edit belongs elsewhere. What you gain in return is ownership: your tasks become plain files under the local-first principle that the primary copy of your data lives on your device, not a vendor’s server.
| You gain | You give up |
|---|---|
| Tasks next to the notes that give them meaning | polished mobile quick-capture and reminders |
| Plain-text ownership, nothing in a vendor cloud | a system that works fully on install |
| One tool instead of two | easy shared or collaborative lists |
| A private, on-device today view | vendor-run backups and notifications |
For an individual whose work is note-heavy, the trade usually favours consolidation. For someone whose tasks are mostly standalone errands captured on a phone, a dedicated app remains the better tool, and running both is a legitimate choice rather than a failure.
Key takeaways: moving your tasks into Obsidian
Replace a standalone task manager with Obsidian when your tasks belong beside your notes, and build the workflow in three parts: a consistent capture habit, the Tasks plugin for dates and recurrence, and a deciding layer like ZPXE for the focused today view a standalone app gave you for free. Expect to assemble the system rather than install it, and accept the real trade: you swap polished mobile capture and reminders for plain-text ownership and one unified tool. If your tasks are mostly quick standalone errands, keep a dedicated app; if they are entangled with your projects and notes, the vault is the better home, and the switch pays off in one place to think and act.
Quick answers
Can Obsidian replace a task manager like Todoist?
Yes, for anyone whose tasks are tied to notes and projects, because keeping them in the vault puts each task next to the material that gives it meaning. You assemble the workflow from a capture habit, the Tasks plugin for dates and recurrence, and a deciding layer for a focused today view. It is not automatic: Obsidian gives you Markdown checkboxes and you add the rest. For standalone errands captured on a phone, a dedicated app still wins.
What do I need to manage tasks in Obsidian like an app?
Three things. A consistent capture spot, usually your daily note or a project note. The Tasks plugin, which adds due dates, recurrence and six priority levels to checkboxes plus a query language for cross-vault lists. And a way to decide what to do first, since a query sorts but does not rank; a layer like ZPXE ranks the surfaced tasks on-device with reasons. Together they replace the capture, dates and today-view that a standalone app bundles.
Is it hard to switch from Todoist to Obsidian?
The setup takes effort but is not hard, and the main work is habit rather than configuration. Export your tasks, decide where new ones will land, install the Tasks plugin, and write one today query. The real adjustment is that Obsidian does not remind you the way a phone app does, so you build the habit of opening your today view. Keep the old app read-only for a couple of weeks while the new routine settles.
Will my tasks stay private if I move them to Obsidian?
Yes. Obsidian stores your notes and tasks as plain Markdown files on your device, with nothing uploaded unless you turn on sync, which is itself end-to-end encrypted. A deciding layer like ZPXE also runs on-device, so ranking your tasks does not send them anywhere. That is a genuine gain over a cloud task app, whose servers hold your list. The trade is that you, not a vendor, are responsible for your backups.
When should you not move tasks into Obsidian?
When your tasks are mostly standalone and phone-first: quick errands, shared shopping lists, reminders you fire off on the go. Obsidian has no polished mobile quick-capture or notification system, so forcing those into the vault fights the tool. It is also the wrong move if you need collaborative task lists several people edit. Obsidian shines when tasks and notes are one body of work; when they are separate, keep a dedicated app and let Obsidian be your notes.
