Can Microsoft To Do Sync With Google Tasks? What Works and How to Set It Up

Microsoft To Do and Google Tasks have no documented native two-way sync. Microsoft To Do syncs through your Microsoft account and integrates with Outlook Tasks. Google Tasks works within supported Google apps, including the Tasks view in Google Calendar. Seeing a Google task on a calendar does not put that task in Microsoft To Do. Microsoft To Do setup and sync · Google Tasks help · Create or edit a Google task

Copy one list without connecting accounts

Make a new destination list named Supplier onboarding pilot. In the source list, note each open task's title, due date, useful notes, and recurrence. Copy the tasks one at a time into the destination, then set each due date, reminder, and repeat rule where available. Open the new list beside the original and verify counts and dates. Google documents a downloadable Tasks archive if you want a record before moving. Use it for reference and manually create the destination tasks. Google Tasks archive · Google repeating tasks · Microsoft To Do dates and reminders

For example, copy “Request supplier insurance certificate,” due November 13, with the supplier's reference number in the notes. For “Check outstanding certificates” every Monday, recreate the recurrence and confirm the first occurrence. Leave old completed tasks in the source unless you need a separate history. When the new list is ready, choose one place for future edits. To undo the pilot, keep the source list and remove the test destination list after checking whether it contains any new work.

Set up one-way capture with Zapier

Use this when people add tasks in Google but review them in Microsoft To Do. Zapier documents Google Tasks → New Task and Microsoft To Do → Create Task. Both accounts need to permit the connection. Zapier documents support for personal Microsoft accounts and work or school accounts with appropriate Microsoft To Do licensing. A managed account may need organization approval to grant third-party access. Use synthetic tasks to test what data the connection can access and copy. Zapier integration and action fields · Google Tasks connection · Microsoft To Do connection

1. Create Capture pilot in Google Tasks and From Google pilot in Microsoft To Do.
2. In the Zap editor, use New Task and select the Google pilot list. Add a unique test task and load it as the trigger sample.
3. Use Create Task in Microsoft To Do and choose the destination pilot list. Map the title and, if needed, notes and the due date from the sample. Verify the result in Microsoft To Do. A date-only value deserves a separate check to make sure it lands on the intended day.
4. Keep the test run separate from the live sample. Once the test mapping is correct, publish the pilot and create a second fresh sample. Allow for the connector's polling interval and confirm it arrives once.

A create-only rule does not copy earlier items as a bulk migration or propagate later edits, completion, deletion, or repeat settings. A repeated occurrence could behave differently depending on the trigger. Keep repeating tasks out of the pilot until you have observed the behavior. Avoid enabling a reverse create rule alongside the first one, since each new copy could trigger another copy. If a run is replayed, check for duplicates before using the result. To stop, turn off the rule, remove the test copies you no longer need, and revoke the connections if they are unused.

The setup is based on official documentation checked November 10, 2026. If you are deciding which app should own the list, see the Google Tasks vs Microsoft To Do comparison.