Migrate your Fruux data
CalDAV/CardDAV sync service built on open standards, letting privacy-conscious users escape Apple or Google lock-in. Targets small teams and individuals who want cross-device calendar and contact sync without vendor dependency.
In its favor
Why people choose Fruux
The signal that keeps Fruux on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Uses open CardDAV and CalDAV standards, meaning contacts and calendars are portable to any RFC-6352 or RFC-4791 compliant client without vendor lock-in
Free tier offers unlimited contacts, calendars, and tasks with no per-record charges, making it attractive for individual users evaluating self-hosted alternatives
Built by the SabreDAV open-source team, giving technical users confidence the sync implementation is mature and well-documented
Cross-platform compatibility with macOS, Windows, Linux, Android, iOS, and BlackBerry draws users who refuse to commit to Apple or Google ecosystems
Privacy-focused positioning appeals to users leaving Google Calendar or iCloud due to data-collection concerns
Sync reliability is inconsistent, particularly with Apple's DAV servers, leading to calendar entries silently failing to propagate
No CSV import support — Fruux founder confirmed the service will only ever accept VCF and native CalDAV/CardDAV feeds, blocking spreadsheet-to-contact workflows
Internal server errors on calendar upload have been reported in third-party clients, suggesting backend instability
The service has a very small review footprint and limited community support compared to Google or iCloud alternatives
Users in privacy communities report difficulty exporting full datasets when they decide to leave, particularly for bookmarks and notes
Reasons to switch
Why people leave Fruux
The recurring reasons buyers give for replacing Fruux. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Fruux fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Fruux pricing overview
Fruux uses a per-seat model with a free individual tier and two paid tiers. Pro is priced at €4/month per user or €40/year, while Team starts at €20/month for 5 members with additional seats at €4/month each.
Basic
Tier 1 of 3
Free
What's included
Need help selecting your Project Management?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Fruux's schedule — see our quote-based pricing →
What gets migrated
Fruux object support
Object-by-object support for Fruux migrations. Per-pair details surface during scoping.
Contacts
Fully supportedContacts are exposed via CardDAV at the principal URL, returned as vCard (RFC 6350) blobs. The standard properties (name, email, phone, address) migrate cleanly. Extended Fruux properties like photo data are base64-encoded within the vCard and preserved as-is.
Calendars
Fully supportedCalendars are CalDAV collections (RFC 4791) containing iCalendar (RFC 5545) VEVENT components. Recurring events, exceptions, and time zones are preserved in the iCalendar stream. We stream each calendar home as a single .ics export and replay it to the destination CalDAV endpoint.
Tasks
Mapping requiredFruux stores VTODO components in a dedicated task CalDAV collection. The destination platform may use a different task schema (Todoist, Things, Asana), so we extract summary, due date, completion status, and description, then map them to the destination's task fields. Custom Fruux task fields are not standardized.
Bookmarks
Not in this platformFruux stores bookmarks in a proprietary non-standard format that is not documented in any public RFC. We do not attempt to migrate Bookmarks because there is no interoperable export protocol and the internal schema is not publicly specified.
Notes
Mapping requiredFruux notes are stored as proprietary objects. There is no CardDAV or CalDAV binding for notes. We export what is accessible via the web API but cannot guarantee the full content or formatting will be preserved at the destination.
Task Lists
Mapping requiredFruux allows multiple task lists. When migrating to platforms that support only one task inbox (e.g. Todoist), we merge all Fruux task lists into a single destination list and flag the merge for customer review.
Calendar Subscriptions
Fully supportediCalendar subscriptions (webcal/ics feeds) appear as read-only calendars in Fruux. We export them as .ics URLs and re-register them at the destination. If the subscription URL is private, the customer must re-authenticate at the destination.
Address Books
Fully supportedFruux supports multiple address books per user. We map each CardDAV addressbook-home-set to a separate destination address book or folder, preserving grouping semantics where the destination supports it.
| Object | Support | Notes |
|---|---|---|
| Contacts | Fully supported | Contacts are exposed via CardDAV at the principal URL, returned as vCard (RFC 6350) blobs. The standard properties (name, email, phone, address) migrate cleanly. Extended Fruux properties like photo data are base64-encoded within the vCard and preserved as-is. |
| Calendars | Fully supported | Calendars are CalDAV collections (RFC 4791) containing iCalendar (RFC 5545) VEVENT components. Recurring events, exceptions, and time zones are preserved in the iCalendar stream. We stream each calendar home as a single .ics export and replay it to the destination CalDAV endpoint. |
| Tasks | Mapping required | Fruux stores VTODO components in a dedicated task CalDAV collection. The destination platform may use a different task schema (Todoist, Things, Asana), so we extract summary, due date, completion status, and description, then map them to the destination's task fields. Custom Fruux task fields are not standardized. |
| Bookmarks | Not in this platform | Fruux stores bookmarks in a proprietary non-standard format that is not documented in any public RFC. We do not attempt to migrate Bookmarks because there is no interoperable export protocol and the internal schema is not publicly specified. |
| Notes | Mapping required | Fruux notes are stored as proprietary objects. There is no CardDAV or CalDAV binding for notes. We export what is accessible via the web API but cannot guarantee the full content or formatting will be preserved at the destination. |
| Task Lists | Mapping required | Fruux allows multiple task lists. When migrating to platforms that support only one task inbox (e.g. Todoist), we merge all Fruux task lists into a single destination list and flag the merge for customer review. |
| Calendar Subscriptions | Fully supported | iCalendar subscriptions (webcal/ics feeds) appear as read-only calendars in Fruux. We export them as .ics URLs and re-register them at the destination. If the subscription URL is private, the customer must re-authenticate at the destination. |
| Address Books | Fully supported | Fruux supports multiple address books per user. We map each CardDAV addressbook-home-set to a separate destination address book or folder, preserving grouping semantics where the destination supports it. |
Gotchas
What to watch for in Fruux migrations
Issues we've hit on past Fruux migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
No CSV import blocks bulk contact migrations
Sync failures with Apple DAV clients cause data loss
Bookmarks and Notes have no exportable standard format
No public rate-limit or quota documentation
Conflict-resolution artifacts require deduplication
| Severity | Issue |
|---|---|
| High | No CSV import blocks bulk contact migrations |
| High | Sync failures with Apple DAV clients cause data loss |
| Medium | Bookmarks and Notes have no exportable standard format |
| Low | No public rate-limit or quota documentation |
| Medium | Conflict-resolution artifacts require deduplication |
Leaving Fruux?
Where Fruux customers move next
5 destinations Fruux can migrate to.
How a Fruux migration works
Four steps, Fruux-specific
Connect
HTTPS basic auth or OAuth (DAV-specific) into Fruux. Scopes limited to read-only on the data we move.
Map
We translate Fruux-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Fruux quirks before production.
Migrate
Full migration with Fruux rate-limit handling. Rollback available throughout.
FAQ
Fruux migration FAQ
Answers to the questions buyers ask most during Fruux migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Fruux migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationOther project management tools we support
Ready when you are
Migrate Fruux.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Fruux setup and destination — written quote back within a business day.