Many sources, one controlled route to CRM.
Sentria Sync connects supported source accounts such as iCloud, Google, Exchange/Microsoft 365 and Other DAV/IMAP with Zoho CRM through a configurable integration layer. Users decide what moves, which direction it moves, how conflicts are handled and what needs review before data is written.
Contacts, calendar items, tasks or approved mail metadata enter as a reviewable sync set.
Names, emails and phones are checked before records are linked.
Only configured fields and directions are allowed to move.
Duplicates, uncertain matches and sensitive writes can wait for approval.
Approved creates and updates are written with controlled limits.
Matched, skipped, updated and blocked items stay visible.
From connection to trusted continuous sync.
The service is designed as an operating journey, not a blind connector. Each step makes the integration more useful while keeping data movement explainable.
Connect
Authorize the selected source account and Zoho CRM, with provider scope and route boundaries clear from the start.
Map
Define which fields matter, how names, phones, emails, companies and activity context should align.
Match
Link existing records before creating new ones, reduce duplicates and flag uncertain identity matches.
Control
Set write direction, conflict policy, retry behavior and review gates for sensitive updates.
Monitor
Track runs, warnings, skipped items and results so the sync can be supported over time.
Sync can start where the user already works.
Start with one supported source connection and one CRM connection. Sentria keeps the route focused, previewed and explainable before scheduled sync is trusted.
Apple-owned relationship data
Contacts, calendars, reminders and selected mail metadata can feed guarded Zoho CRM routes.
Google Workspace signals
Google Calendar, Tasks, Contacts and Gmail metadata can be connected when the required provider access is available.
Microsoft 365 sources
Exchange Online calendar, tasks, contacts and mail context can be routed through Microsoft Graph.
Standards-based providers
CalDAV, CardDAV and IMAP-style sources can be prepared where the provider supports the needed access.
Prepared CRM target
Approved records and activity context can be written to Zoho CRM with mapping, review and audit evidence.
Contacts, calendars, tasks and mail context
Each lane can keep its own scope, sync direction, conflict policy and first-run guard.
Sentria Sync pricing and limits.
Simple launch conditions for syncing supported contact and calendar sources with CRM systems. Start with a safe preview, choose one-way sync when one source should lead, or use guarded two-way sync when both systems need to stay aligned.
Preview
Connect supported source and CRM routes without write-back.Review what Sentria would synchronize, and inspect possible duplicates or conflicts before anything is written back.
- No write-back
- Read-only simulation
- Connection and mapping preview
- iCloud, Google, Exchange/Microsoft 365, Other DAV and CRM connection preview
- Duplicate and conflict preview
- Basic field mapping preview
- No changes written to either system
One-way Sync
One selected direction between a supported source connection and CRM.Synchronize in one selected direction when one system should remain the master source.
- Up to 2,500 contacts
- Up to 1,000 calendar events
- Up to 6 sync runs per day
- 1 supported source connection and 1 CRM connection
- iCloud, Google, Exchange/Microsoft 365, or Other DAV-style source
- Contacts sync
- Calendar sync
- Duplicate detection
- Basic conflict warnings
- Email support
Guarded Two-way Sync
Guarded two-way sync between a supported source connection and CRM.Keep the selected source and CRM route aligned while Sentria protects the path with preview, conflict, duplicate, and delete safeguards.
- Up to 10,000 contacts
- Up to 5,000 calendar events
- Up to 24 sync runs per day
- 1 supported source connection and 1 CRM connection
- iCloud, Google, Exchange/Microsoft 365, or Other DAV-style source
- Two-way contacts sync
- Two-way calendar sync
- Preview before first write-back
- Conflict detection
- Suspicious delete protection
- Duplicate matching
- Field-level sync rules
- Sync audit trail
- Email support
Sync Pro
Higher-volume and more frequent synchronization.Higher-volume guarded two-way sync for supported source and CRM routes with advanced mapping and priority support.
- Up to 50,000 contacts
- Up to 25,000 calendar events
- Sync up to every 15 minutes
- 1 supported source connection and 1 CRM connection
- iCloud, Google, Exchange/Microsoft 365, or Other DAV-style source
- Two-way contacts sync
- Two-way calendar sync
- Advanced field mapping
- Advanced duplicate and merge rules
- Delete approval rules
- Extended sync audit trail
- Priority support
Recommended plan
Most users should start with Guarded Two-way Sync. It keeps the selected source and CRM route aligned in both directions while protecting the user from the most common sync risks: duplicates, conflicting edits, and accidental deletes.
Volume limits
- Volume means the active records Sentria monitors and synchronizes within the selected route: contacts and calendar events connected between one supported source account and one CRM connection.
- One-way Sync includes up to 2,500 contacts and 1,000 calendar events.
- Guarded Two-way Sync includes up to 10,000 contacts and 5,000 calendar events.
- Sync Pro includes up to 50,000 contacts and 25,000 calendar events.
- If a route grows above its plan limit, Sentria may ask the user to reduce the selected scope or move to a higher plan before additional records are synchronized.
Supported first-route sources
- The first public Sync lane can cover iCloud, Google, Exchange/Microsoft 365, and standards-based Other DAV-style sources such as CalDAV and CardDAV where the provider supports the needed access.
- CRM-side availability depends on the enabled CRM connector, starting with the currently prepared CRM routes.
- A route can still stay in preview when a provider, scope, or write-back action is not production-ready yet.
More connections
- A connection means a separately authorized source or target account, such as one Google account, one Exchange mailbox, one iCloud account, one Other DAV server account, or one CRM user.
- Each public plan covers one active source-to-CRM route. Extra source accounts, CRM users, or parallel routes require an additional license or add-on unless a team or custom agreement is arranged.
- Unlicensed extra connections can be prepared for setup or preview, but scheduled sync and provider write-back should remain locked until the needed license is active.
Sync frequency
- Frequency means how often Sentria checks for changes and runs the configured route while the connection is active.
- One-way Sync can run up to 6 times per day.
- Guarded Two-way Sync can run up to 24 times per day.
- Sync Pro can run up to every 15 minutes.
- Actual timing can vary when provider rate limits, authentication issues, maintenance windows, or conflict reviews require Sentria to pause or slow a route.
Support
- Email support is included in One-way Sync and Guarded Two-way Sync, with a target first response within two business days.
- Priority support is included in Sync Pro, with a target first response by the next business day and earlier handling for sync interruptions.
- Priority support includes help with field mapping, conflict rules, duplicate handling, and guided recovery when a route needs review.
- Security, privacy, and data-protection issues are reviewed according to severity, regardless of plan.
Commercial notes
- Prices are listed per user and exclude VAT or local taxes where applicable.
- Each plan covers one supported source connection connected to one CRM connection. Additional users, accounts, provider lanes, or routes require their own plan or an agreed add-on.
- Contacts and calendar sync are included in the first public route. Advanced automation or provider-specific capabilities may be offered separately.
- Write-back remains guarded by preview, conflict rules, suspicious delete protection, and audit evidence.
Automation with a brake, a map and a record.
Two-way sync is powerful only when it is governed. Sentria Sync separates the connection from the policy: mapping, matching, conflict handling, write direction and review rules are explicit before ongoing synchronization is trusted.
When the service sees uncertainty, it can stop, flag the item and leave a visible reason. That makes the integration useful for real business data, not just clean demos.
Built for controlled data movement.
The integration model is designed to support security reviews, operational accountability and compliance work around personal and business contact data.
Move only what is needed
Field-level mapping helps keep unnecessary attributes out of the sync route.
Credential boundaries
Connections are handled by the service layer, with user and organization context separated from manual spreadsheets.
Traceable decisions
Run results, decisions, skipped items and warnings remain available for support and operational review.
Reviewable processing
Visible sync policy, data scope and evidence help teams document how the integration is operated.
Keep the sync alive, visible and supportable.
After setup, users need confidence that the service is still doing the right work. Sentria Sync keeps status, exceptions and outcomes readable.
Start with a supported source and Zoho CRM sync.
Open the Sentria Sync login screen or contact us to define the first controlled source-to-CRM route.