How to migrate Microsoft To Do to Todoist
Quick answer
Use To Do Mover to export your Microsoft To Do lists locally as Todoist CSV files (one CSV per list), then open each target project in Todoist on the web or desktop and upload the file through the project's three-dot menu under Import from CSV.
Step-by-step
- Load your tasks in To Do Mover
Open To Do Mover's export tool and sign in with your Microsoft account, or load a previously saved todo-backup.json file offline.
- Set your export time zone and Todoist options
Pick the lists to migrate, confirm the time zone you normally used Microsoft To Do in, select “Todoist CSV” (alongside “JSON backup”), and review the Todoist checkboxes.
- Download and unzip the CSV files
Export and extract the files. Each list becomes one .csv file, and lists exceeding 300 rows (including sub-tasks) are split into numbered parts automatically.
- Import each CSV into a Todoist project
In the Todoist web or desktop app, create or open a project, click the top-right three-dot menu (…), choose “Import & export” (or “Manage data” in some versions), and click “Import from CSV”.
- Review recurring tasks, labels, and counts
Repeat for each list file, spot-check recurring rules and labels in Todoist, and revoke To Do Mover's Microsoft account access once finished.
When to use this migration path
If you plan to move from Microsoft To Do to Todoist before the Microsoft To Do apps retire on June 30, 2027, Todoist does not offer a built-in Microsoft To Do importer. Generating Todoist-formatted CSV files locally with the To Do Mover export tool is the most direct path.
Before importing all of your lists, take two precautions:
- Export a JSON backup at the same time: Todoist CSV omits fields such as completed task history, start dates, active reminders, and attachments. Saving
todo-backup.jsongives you a permanent lossless copy—see the Microsoft To Do backup guide. - Test with one project first: Actual rendering inside Todoist has not been verified end-to-end for every edge case. Create a test project and import a single list (or try demo mode first) to confirm how dates, sub-tasks, and labels appear before importing everything.
What transfers and what is lost or changed
To Do Mover produces one UTF-8 CSV file per selected list matching Todoist’s import columns (TYPE,CONTENT,DESCRIPTION,PRIORITY,INDENT,AUTHOR,RESPONSIBLE,DATE,DATE_LANG,TIMEZONE).
| Data item | Migration result | Details |
|---|---|---|
| Lists | Preserved (one per project) | Each list becomes a separate .csv file to import into a Todoist project |
| Task title | Preserved | Line breaks inside titles are flattened to spaces so CSV rows stay intact |
| Steps (sub-tasks) | Preserved (unchecked by default) | Written as INDENT=2 sub-tasks beneath the parent task; checked steps are skipped by default |
| Notes | Plain text | Placed in the DESCRIPTION column; rich formatting becomes plain text |
| Due date | Preserved | Restored in your export time zone as YYYY-MM-DD in DATE (for non-recurring tasks) |
| Start date | Lost | Todoist’s CSV template does not have a start date column |
| Reminders | Saved as text | Active reminders are not created; enabled reminder times are appended as text in DESCRIPTION |
| Recurrence | Partially preserved | Common rules become Todoist English recurrence text; unsupported rules and end conditions are written to DESCRIPTION |
| Importance | Mapped to p1 and p4 | High importance maps to 1 (p1); normal and low map to 4 (p4) |
| Categories | Optional labels | Appended as @Category (spaces replaced by _) in the title by default so Todoist parses them as labels |
| Completed tasks | Skipped by default | Todoist CSV cannot import tasks as completed; optional toggle imports them as open |
| Linked resources | Saved in description | Links such as Outlook flagged-email URLs (fields not yet verified on a live account) are added to DESCRIPTION |
| Attachments | Not included | CSV cannot carry files; download them alongside your JSON backup |
| My Day and list groups | Not available | Not exposed by the Microsoft Graph API; all lists export flat |
Choosing the right Todoist export options
When you select Todoist CSV on the preview screen, three options appear:
- Include completed tasks (imported as open): Off by default. Leave this off unless you specifically want completed items re-opened in Todoist; use the JSON backup for completed history.
- Include checked steps: Off by default. Turn this on only if you want already-checked steps inside active tasks to appear as unchecked sub-tasks so you retain their text.
- Turn categories into Todoist labels: On by default. To Do Mover appends
@Categoryto the task title and replaces spaces with underscores (_) so multi-word categories stay intact as a single label. Turn it off if you prefer a fresh label setup.
Also double-check the Export time zone at the top of the preview screen: pick the time zone you normally used Microsoft To Do in so due dates do not shift by a day.
Handling the 300-task limit and recurring tasks
Todoist enforces a limit of 300 active task rows per project (including sub-tasks). Attempting to import a CSV with more than 300 rows causes the entire upload to fail. When a list exceeds 300 rows, To Do Mover splits it into multiple files named <List name> (part 1 of 2).csv, keeping every parent task together with its sub-tasks, and adds a note under “Notes from the export”. Keep Todoist’s plan limits on total project count in mind if you have many split files.
For recurring tasks, keep two details in mind:
- Start date and original due date: When
DATEholds a recurrence rule (such asevery week on monday, wednesday), Todoist evaluates it starting from the import day. To Do Mover writes the original due date intoDESCRIPTIONso you can adjust the next occurrence if needed. - Recurrence end dates or counts: Todoist CSV cannot express “until a date” or “after N occurrences”. Those tasks import as open-ended repeats, and To Do Mover writes the full rule into
DESCRIPTIONplus warns you in the export summary so you can stop them manually later.
Post-import checklist and troubleshooting
After uploading your CSV files, verify a few common areas:
- Cannot find “Import from CSV”: Project CSV import is available in the Todoist web and desktop apps, not typically on mobile. Depending on your Todoist version, the submenu under the project’s top-right
…icon may be labeled Import & export or Manage data—open it and choose Import from CSV. - Fewer tasks than in Microsoft To Do: Check whether completed tasks and checked steps were excluded by default. If active tasks are missing, check for failed lists on the preview screen or inspect
meta.incompletein your JSON backup. - Labels did not attach: Verify that “Turn categories into Todoist labels” was checked and watch for special punctuation in original category names.
- All tasks show p4: Only starred (“Important”) tasks in Microsoft To Do map to p1 in Todoist; normal and low importance both map to p4.
Still comparing task apps? Check out the guides for migrating to TickTick, migrating to Things 3, or browse the FAQ.
Common questions
Why was one Microsoft To Do list split into multiple CSV files?
According to Todoist's help documentation, a single Todoist project can hold at most 300 task rows (including sub-tasks). If a CSV exceeds 300 rows, the entire import fails.
When a list plus its checklist steps exceeds 300 rows, To Do Mover automatically splits it into multiple files (such as part 1 of 2) without separating a parent task from its sub-tasks. Import each split file into its own project, or trim the list first.
Why are completed tasks and checked steps missing by default?
Todoist's CSV import format does not support a “completed” state—any imported row comes in as an open task. To Do Mover therefore skips completed tasks and checked steps by default.
If you want them imported anyway, enable “Include completed tasks (imported as open)” and “Include checked steps” before exporting. For archiving completed history, keep a JSON backup instead.
Why do recurring tasks lose their end dates or start from today?
Todoist CSV recurrence syntax cannot reliably express an end date (“until”) or a fixed number of occurrences, and imported recurring rules start from the day you import them.
To Do Mover preserves the original due date and any recurrence end condition inside each task's description and flags them in the export notes so you know when to stop them manually.
Sources
Ready to export your tasks?
Everything runs locally in your browser. Start with a lossless JSON backup or try the demo first.