SyncGuarded contact sync
Connect an address book or CRM contact library from eight supported providers. Choose any supported pair and direction, preview the first changes, and keep uncertain matches, conflicts, and removals under review.
Useful from day one
Replace repeated exports and fragile manual reconciliation with a route that keeps its direction, scope, safety rules, schedule, and history together.
Keep an iCloud, Google, Microsoft, or CardDAV address book aligned with the CRM your team uses. New and updated contacts move in the direction you choose while uncertain matches stay visible for review.
Prepare a guarded route between supported CRM contact libraries when teams are migrating gradually or need two systems available for a controlled period.
Use a focused contacts route across Apple, Google, Microsoft, or CardDAV accounts when people need the same essential names, email addresses, phone numbers, organizations, and postal details.
Preview identity matches, field differences, and suspicious removals before provider write-back. Exact email identity is treated as stronger evidence than a name-only match.
Connection library
A saved connection is maintained once and can participate in multiple prepared or active routes. The route—not the credential—owns direction, rules, schedule, and review state.
Keep the address book used on iPhone, iPad, and Mac connected through Apple CardDAV.
Connect a Google address book through Google OAuth and the People API.
Connect the contacts in a Microsoft account through Microsoft Graph authorization.
Connect a standards-based CardDAV address book using its server and account credentials.
Keep selected CRM contact records aligned without relying on repeated CSV imports.
Connect HubSpot contacts to an address book or to another supported CRM endpoint.
Keep Pipedrive people aligned while leaving deals and other CRM objects outside the Sync route.
Route Salesforce contacts without turning the Contacts service into a full CRM migration.
Sentria's Google OAuth application is verified for read-only and read/write Contacts access. Each user remains in control of consent, and the other supported connections operate independently of Google.
From connection to first sync
Every route keeps the two endpoints, direction, contact scope, mapping, safety behavior, license, and runtime evidence in one place.
Connect the provider accounts you want to reuse. Credentials belong to connection cards, not to individual routes.
Choose any two different supported endpoints and select A → B, B → A, or guarded A ↔ B.
Check scope, mappings, duplicates, conflicts, and proposed creates or updates before enabling writes.
Assign route capacity, start the route, and use the Sync monitor to review health, exceptions, and approvals.
Designed for controlled change
Sentria treats provider write-back as an operation that needs identity evidence, a defined scope, and a reviewable result. Routes can pause when authorization, mappings, limits, or provider behavior make a change unsafe.
Read the security commitmentsCompare the selected sources and inspect proposed changes before the first provider write.
Conflict, volume, capability, and identity checks can block unsafe operations before they reach a provider.
Likely duplicates and name-only matches stay available for human review instead of being merged silently.
Monitor failures, paused routes, pending approvals, usage, and authorization issues from one workspace.
Simple route-based pricing
Prepare and preview routes for free. Paid tiers are based on active route capacity, distinct active contacts, and sync frequency—not whether data moves left, right, or both ways.
One active contact route in either direction, including guarded two-way sync.
Up to three active contact routes, with any direction and the full guarded-sync safety layer.
Up to six active routes across all supported Contacts providers, faster sync, advanced controls, and priority support.
Prices are per Sync workspace and exclude VAT or local taxes where applicable. Full plan conditions are shown before Checkout.
Questions before you connect
Sentria Sync supports iCloud Contacts, Google Contacts, Microsoft Contacts, CardDAV, Zoho CRM, HubSpot CRM, Pipedrive, and Salesforce. Any two different saved endpoints can form a route, including two accounts on the same provider.
Yes. A route can run A to B, B to A, or as guarded two-way sync. Direction does not change the price or consume a second route slot.
Yes. The free Preview level lets you save connections, prepare inactive routes, inspect mappings, and run read-only checks. A paid Starter, Standard, or Pro plan is needed to activate scheduled sync and provider write-back.
Sentria previews likely matches and conflicts before write-back. Exact email identity is stronger evidence than a name-only match. Delete proposals always require explicit review and verified provider evidence.
The limit is based on distinct active contacts monitored within active routes. Rechecking the same contact does not turn it into a new contact for plan usage.
Sentria Sync is deliberately focused on contact identity and continuity. Its route model adds preview, field comparison, duplicate review, guarded write-back, suspicious-delete protection, and sync evidence instead of treating every field update as an unrelated automation.
Yes. Sentria's Google OAuth application is verified for read-only and read/write Google Contacts access. Each user still chooses whether to grant access, and every other supported provider route operates independently of Google.
Start without provider write-back
Create a Sync workspace, save your connections, and see how contacts compare before choosing a paid activation.