Synchronize with a SyncML server via HTTP#

This is the simplest usage, explained as part of the “getting started” documentation. Limited to one address book, calendar, task list and set of memos because that is what SyncML servers typically support.

Synchronize with a SyncML-capable device via Bluetooth#

When you don’t want to store your confidential data on some third-party’s server, then direct synchronization via Bluetooth can be used.

Run your own SyncML server#

If you have access to a server on the Internet, then you can run SyncEvolution as your own, private SyncML server. Useful if you have devices which support SyncML over HTTP natively or via third-party apps and you want to synchronize anywhere, anytime without relying on third-party services. The instructions use plain files on the server and thus do not depend on Evolution.

Synchronize Evolution data between different computers and phones via WiFi/LAN#

In contrast to the usage on a server in the previous scenario, this HOWTO assumes that synchronization happens on the home network. It explains how data stored in Evolution can be synchronized between different computers running SyncEvolution or other devices (like a phone) with SyncML over HTTP. SyncEvolution can synchronize an arbitrary number of databases, which is explained in the HOWTO.

Synchronize with a CalDAV/CardDAV server like Google Calendar#

This is a new feature in SyncEvolution 1.2. It uses “local sync” to move data between a local storage (for example, accessed via SyncEvolution’s Evolution backend) and a remote CalDAV/CardDAV server (accessed with the new CalDAV/CardDAV backend). A basic setup with Google Calendar is explained as part of the command line usage.

Manipulate a PIM storage via the command line#

It is possible to export/add/update/delete items in local storages (EDS, Akonadi) and some remote storages (WebDAV). See the item operations HOWTO for details.