This open-source bridge syncs Google Tasks and Microsoft To Do—with limits
Tasks–To Do Sync runs in your own Google Apps Script project. Its account requirements, scheduled updates and deletion behavior deserve a look before you connect real task lists.
In this article
Tasks–To Do Sync is an open-source project that connects Google Tasks and Microsoft To Do through a user's own Google Apps Script installation. Its maker, writing as simonchai-tw, described the project in a 16 October DEV Community post. The practical appeal is a shared task workflow across two services without a separate synchronization company hosting the task database.
The repository says it supports creating and editing tasks in either direction, completing and reopening them, notes, eligible lists, and other parts of the task lifecycle. This is a documentation-based overview checked on 16 October; Auratro has not installed it, connected accounts or independently tested synchronization.
Scheduled sync, with account and scale limits
The documented trigger runs every ten minutes. The project says ordinary changes normally arrive within that interval, while guarded operations can take another cycle. That is a stated operating expectation, not a real-time delivery guarantee.
The guided Microsoft sign-in flow is for personal accounts. According to the README, work and school accounts need the more involved self-managed Azure or Entra setup. The project recommends roughly 300 synchronized task pairs as a conservative operating range and describes 600 as an observed stress boundary, not a support promise.
Time and deletion do not map perfectly
The project documents a notes-marker convention to carry time-of-day information into the Google Tasks side, alongside an optional dedicated-calendar projection. Its current defaults enable that calendar projection, so connecting the tool can create calendar events as well as synchronize tasks.
Deletion and list moves are also enabled by default in the documented configuration. The maker describes confirmation rounds, live checks and recovery records intended to reduce accidental or duplicate changes. Those safeguards are the project's design claims; a test count in its README does not establish that every account or failure case is safe.
Self-hosted still means granting account access
The project says it runs inside a private Apps Script project and talks to Google Tasks and Microsoft Graph APIs rather than operating its own hosted sync service. Google and Microsoft still process the requests, and the installation needs permissions for the resources it uses.
The README identifies Google Tasks, a dedicated secondary calendar and alert email among those resources. On the Microsoft side it identifies To Do access and a mailbox-settings permission for the account's time zone. Its detect command can also temporarily read other Apps Script projects visible to the account to identify existing installations.
The repository uses the MIT licence. That makes the source available to inspect and adapt, but does not remove account authorization or maintenance responsibilities. Before trying any two-way synchronization tool, read its current permission list, defaults, rollback guidance and supported-account requirements, and preserve important task data. This article is not a tested setup guide or a recommendation to bypass a consent or security warning.
Image: the unmodified project-supplied diagram illustrates the direct Google Tasks–Microsoft To Do bridge. Its surrounding app connections describe native integrations; Auratro has not tested those workflows. Copyright (c) 2026 Simon Chai, reproduced under the MIT licence; original asset and full licence linked below.
Sources & further reading
Maker's 16 October announcement
Tasks–To Do Sync README: capabilities, defaults and operating limits
Project security model and incident guidance
Our articles help you explore AI and build practical skills. For a correction or a question, contact us. Contact
