Skip to main content

Reinstate Direct Google Contacts One-Way Sync

Feature Request

While CardDAV works for syncing accounts in both ways, CardDAV is inherently client-dependent and introduces additional overhead (local account configuration, local client-side syncing etc.).

The discontinued one-way sync via direct Google Contacts integration offered cleaner cloud-based approach. It reduced reliance on local clients and provided a seamless way to treat Dex as the single source of truth for contacts.

Reinstating the direct Google Contacts one-way sync as an option alongside CardDAV would give users flexibility:

  • Those preferring cloud-based sync could rely on Google Contacts integration as a one-way sync

  • Those requiring two-way sync could continue to use CardDAV

Posted by Jason Haak ·
Status: Open4 comments

Log in to comment and vote

Comments4

  • Dex Operations

    Team•

    Sep 22

    Requested again by a customer who used the earlier direct Dex to Google Contacts one-way sync and would like it reinstated. They valued treating Dex as the source of truth and having contact changes flow out to Google Contacts automatically in the cloud, rather than relying on a device-side CardDAV client. They would like this cloud-based export path available again alongside CardDAV.

  • Dex Operations

    Team•

    Sep 2

    Requested again by a customer who expected contacts to flow from Dex into Google Contacts as a one-way push, with a Dex-specific label created on the Google side. They had a Google account connected and were looking for the contacts to appear there. The use case is treating Dex as the source of truth and having that address book available anywhere Google Contacts already syncs, without configuring a CardDAV client on each device.

  • Ruben Uzan

    •

    Oct 17, 2025

    Why remive a feature in the first place? Why force everyone to moive to caldav whgen Google Contacts is widely used?

    • Jason Haak

      •

      Oct 20, 2025

      Ruben Uzan just what I was thinking! Changing this also changed a lot in the workflow of all.

      Isn't there the possibility to keep both solutions?