Todoist adds views to one task model instead of replacing it

What the company's documentation describes today

Todoist's company page, as retrieved on 16 September 2026, describes Doist as a remote-first organisation since 2011, before the pandemic normalised it, run by founder and chief executive Amir S. with a team spread across dozens of countries. The core product remains a task list: items organised into projects and sections, which the company has extended over time with additional ways to look at the same data rather than replacing the underlying model. Todoist's help documentation describes a board layout that turns a project's sections into columns and its tasks into draggable cards, syncing the same underlying tasks across a calendar view, a list view and the board, so a change made in one layout appears in the others rather than living in a separate system.

What stability looks like in the documentation

Keeping one task model while adding views is a specific design choice, visible in how the documentation treats data portability. A task exported or imported as CSV, according to Todoist's export documentation, keeps its section, description, dates, comments and attachments as an exact duplicate of the original project, provided it stays under a stated limit of 300 tasks per project. The same documentation notes that a recurring task loses its original start date on export, so a task recurring every year from a specific date becomes simply every year, a small but real gap between what a user set up and what a plain file can represent.

The friction: what backups and exports do not cover

Todoist's backup documentation states that a full backup is created automatically on days a user makes changes, stored as a ZIP of per-project CSV files, with up to 21 backups retained before the oldest is deleted. Both the backup and CSV export explicitly exclude completed tasks and, for backups, archived projects, and full backup access is restricted to Pro and Business subscribers using the web or desktop apps. That means a free-tier user's safety net is thinner than a paying one's, and even a paying user's export is a snapshot of active work, not a complete historical record of everything the tool has tracked. A tool that keeps one model for years is easier to trust with daily use, but the documentation shows that trust should not extend past what the export options actually promise.

Questions to ask before you adopt it

• Does your workflow depend on a complete history of completed tasks that the stated export options do not retain?
• Is your project size within the documented 300-task CSV limit, and what happens to larger projects if you need to migrate?
• Is backup access available on your specific plan, and have you checked recently that a downloaded backup actually restores?

A stable task model is a real advantage for a habit meant to last years, but stability in the interface says nothing about the completeness of an export. The documentation is specific enough here to check before relying on it, which is a more useful signal than the company's own claim to longevity.