How to back up Microsoft To Do before the apps retire
Quick answer
Sign in with your Microsoft account in To Do Mover, confirm the time zone you normally use Microsoft To Do in, and export the lossless JSON backup (todo-backup.json). Everything runs locally in your browser with no server, and you can convert the backup to other formats offline later.
Step-by-step
- Open the export tool and sign in
Go to To Do Mover's export tool and sign in with your Microsoft account; by default it requests only read-only permissions (User.Read and Tasks.Read).
- Check your lists and export time zone
Select the lists you want to save, choose whether to include completed tasks, and set the export time zone to the zone where you normally used Microsoft To Do.
- Grant attachment access if needed
If you have task attachments to download, click “Grant permission and read attachments” to add Tasks.ReadWrite incrementally, then check “Download attachments”.
- Download and archive your backup
Keep “JSON backup” selected (plus any extra formats you want), click Export, and store todo-backup.json or the full zip archive in a safe place.
- Revoke access when finished
Once you verify that the backup opens cleanly offline, remove To Do Mover's access from your Microsoft account permission settings.
Why back up before the apps retire
Microsoft has announced that all Microsoft To Do apps will retire on June 30, 2027 across Windows, Mac, iOS, Android, and the web. Both personal accounts and work or school accounts are affected. Microsoft notes that the underlying services and APIs will shut down on separate, later dates to be announced.
The impact differs by account type:
- Personal Microsoft accounts (free accounts, Microsoft 365 Personal, and Family): Microsoft Planner is not available for personal accounts, and Microsoft offers no official replacement app. You will need to back up your tasks and choose another app.
- Work or school accounts: Microsoft is directing users to Microsoft Planner, but existing tasks will not migrate automatically. If you plan to use another tool—or simply want an independent local archive—you still need your own backup.
Creating a lossless todo-backup.json file early in the export tool lets you evaluate replacement apps at your own pace without risking last-minute API disruptions.
What the JSON backup preserves and what it cannot
todo-backup.json stores two layers: normalized task fields ready for conversion, and the raw Microsoft Graph responses with account-email annotations (@odata.context and @microsoft.graph.tips) stripped at every level. Keeping the raw responses ensures that future format updates or custom scripts still have access to the original fields.
| Data item | Backup status | Details |
|---|---|---|
| Custom lists and default Tasks list | Preserved | Keeps the API order, list names, and emoji |
| Task titles, status, and importance | Preserved | Includes completed dates, created timestamps, and last-modified timestamps |
| Checklist steps and completion states | Preserved | Keeps step titles, checked states, and step timestamps |
| Task notes | Preserved | Saves both plain text and original HTML notes when present |
| Due dates, start dates, reminders, and recurrence | Preserved | Dates are restored using your export time zone; recurrence keeps its full structure |
| Categories | Preserved | Keeps all category labels attached to each task |
| Attachment metadata and files | Optional | Requires incremental Tasks.ReadWrite; files are saved under attachments/ in the zip |
| Shared lists and Outlook flagged emails | Per API response | Supported in code per Microsoft Graph docs, but not yet verified on a live account containing them |
| My Day | Not available | A temporary daily view not exposed by the Microsoft Graph API |
| List groups (folders) | Not available | Not exposed by Microsoft Graph; all lists are exported flat |
For very large accounts, To Do Mover follows Microsoft Graph’s @odata.nextLink pagination loop (covered by unit tests), though live pagination behavior on accounts with large task volumes has not yet been verified directly. If your account holds thousands of tasks, compare list counts after exporting.
Privacy and permissions explained
To Do Mover is a static site with no backend server, and its full source code is open source under AGPL-3.0. When you sign in with Microsoft, your browser communicates directly with Microsoft’s sign-in endpoints (login.microsoftonline.com, login.live.com) and Microsoft Graph (graph.microsoft.com):
- Tasks stay in page memory: Lists and tasks are held only in browser memory while you use the page. They are never written to local storage, IndexedDB, or cookies. This site sets no cookies.
- Tokens clear when you close the tab: Sign-in tokens live in
sessionStorageand are cleared immediately on sign-out or when the tab closes. - Read-only by default: Initial sign-in requests only
User.Read(to display which account is signed in) andTasks.Read(to read lists and tasks). - Why attachments ask for an extra scope: In live testing on November 20, 2026, Microsoft rejected attachment requests under read-only permission. To Do Mover therefore requests
Tasks.ReadWriteincrementally only if you opt in to reading or downloading attachments. Even then, the code never calls any write API or alters your account.
For hosting and cookie-free analytics details, see the privacy policy. If you want to inspect the workflow without signing in, try demo mode inside the export tool first.
How to verify your backup after downloading
Take two minutes to check your files before revoking access:
- Review export notes and warnings: On the completion screen, expand “Notes from the export” to confirm no lists or attachments failed. If a list failed to load, go back to the preview screen and retry only the failed list—already loaded data stays intact.
- Spot-check due dates: Microsoft Graph stores due dates as local midnight converted to UTC. If your chosen export time zone does not match the zone where you used Microsoft To Do, due dates can shift by one day. Verify two or three due dates against your To Do app.
- Test offline loading: Open the export tool in a fresh tab, choose “JSON backup”, and drop in
todo-backup.json. Confirm that all expected lists and task counts appear without signing in. - Keep the zip structure if you included attachments: When attachments are downloaded, the output is a zip archive (
todo-export-YYYYMMDD-HHmm.zip) containingtodo-backup.jsonandattachments/<list>/<task>-<filename>. Archive the whole zip or keep theattachments/folder with the JSON file.
Where to migrate next
Once todo-backup.json is safely stored, you can drop it back into the export tool offline at any time to try different destinations:
- Task managers: Migrate to Todoist, Migrate to TickTick, or Migrate to Things 3 on Mac and iPhone
- Notes and local plain text: Export to Markdown for Obsidian, Logseq, or Notion
- CalDAV and spreadsheets: Export to ICS for Thunderbird and Nextcloud Tasks or Export to CSV for Excel, Google Sheets, or Notion
For answers about revoking access, account types, or export limits, visit the FAQ.
Common questions
Can I convert todo-backup.json to other formats after June 30, 2027?
Yes. Open To Do Mover's export tool, choose “JSON backup”, and drop in your saved todo-backup.json file. You can convert it to CSV, Markdown, ICS, Todoist CSV, or Things 3 offline without signing in.
Offline conversion continues to work even after the Microsoft To Do apps retire and after the underlying API shuts down.
Are attachment files stored inside todo-backup.json?
No. To avoid bloated JSON files, todo-backup.json stores attachment metadata (names, sizes, and paths), while the actual files are placed in the attachments folder inside the downloaded zip archive when “Download attachments” is enabled.
Keep the entire zip archive—or keep the extracted attachments folder alongside todo-backup.json—if you want to retain those files.
What does meta.incomplete inside todo-backup.json mean?
The meta.incomplete field is added only if part of the read or download failed. It lists any lists, attachment metadata, or attachment files that could not be fetched, so you can tell the difference between an empty list and a failed read.
If it appears, return to the preview screen in the export tool, retry the failed lists, and export a fresh complete backup.
Sources
Ready to export your tasks?
Everything runs locally in your browser. Start with a lossless JSON backup or try the demo first.