Salesforce surveyed more than 4,000 sales professionals for its 2026 State of Sales report and found the average seller spends 40 percent of the week actually selling. Gen Z reps drop to 35 percent, losing roughly two hours a week to manual data entry alone. Calendar logging is a slice of those two hours, and it is one of the few slices you can automate in an afternoon.
For sales reps, reducing manual work around meetings can streamline daily routines, boost productivity, and protect more time for customer interactions, engagement, and closing deals.
This guide covers both ways to connect Google Calendar to Salesforce in 2026: the native calendar sync inside Einstein Activity Capture, and third-party sync tools. You will get the current setup steps, the sync direction choice most teams get wrong, the limits nobody mentions until go-live, and a straight answer on when the free option is already enough.
The goal is a seamless connection between calendar and CRM systems that supports sales productivity without creating more administrative tasks.
Native option: Einstein Activity Capture (EAC). Included with Sales Cloud Starter, Professional, Enterprise, and Unlimited, capped at 100 users and roughly 6-month retention.
Setup path: Setup, then Einstein Activity Capture, then Settings, then Add Configuration, then select Google.
Sync direction: Google to Salesforce (Salesforce's recommendation, and the fastest) or Salesforce to Google.
Sync speed: events typically land within 5 minutes, but Salesforce documents that it can take several hours.
Date that matters: Lightning Sync retires April 2027. Office 365 orgs on Exchange Web Services must migrate by August 2026.
Paid alternative: third-party sync tools such as Cirrus Insight, from $14 per user per month.
You have two real options. Salesforce's native calendar sync runs through Einstein Activity Capture. Everything else is a third-party integration tool writing to Salesforce through the API.
These third-party solutions include tools like Cirrus Insight, which can add broader rules and scheduling capabilities.
Lightning Sync used to be the third. It is not anymore. Salesforce retires Lightning Sync in April 2027, and orgs running it against Office 365 with Exchange Web Services need to migrate by August 2026, because Microsoft switches EWS off in October 2026. If you are on Google Workspace, that specific deadline does not hit you the same way. It still means Lightning Sync is a dead end, so do not start there.
|
What you need |
Einstein Activity Capture |
Third-party sync tools |
|
Cost |
Included with Sales Cloud editions (Standard tier) |
Paid per user, per month |
|
User cap |
100 users on EAC Standard |
No platform-imposed cap |
|
Data retention |
Around 6 months on Standard, 24 months with a paid license |
Native records, your org's retention rules |
|
Where events land |
Standard Salesforce Event records |
Standard Salesforce objects |
|
Custom objects |
Not supported |
Usually supported |
|
Filtering rules |
Broad capture settings |
Rule-based, per event |
|
Scheduling links |
Not included |
Usually included |
|
Who has to be involved |
Salesforce admin, usually a Google Workspace admin too |
Salesforce admin plus a per-user install |
One thing the table cannot show you is your edition. EAC Standard covers Sales Cloud Starter, Professional, Enterprise, and Unlimited Edition. If you are on Enterprise Edition and you want the full version, that is a paid add-on, not a setting.
Four things, and only the first two justify a project on their own.
Meetings log themselves. Calendar events save to Salesforce as standard Event records and appear on the activity timeline of the related contact, lead, account, opportunity, contract, or quote.
That connection helps revenue teams preserve context across meetings and email messages, while better visibility for managers can reveal useful engagement patterns.
Reps get context before the call. Open the record and see every meeting and email tied to it, including ones from a teammate who left two quarters ago.
Managers get real activity data instead of self-reported activity data. Meeting volume you can report on beats meeting volume reps remembered to log.
That reporting foundation can later support AI-driven analysis, provided the underlying activity data is complete and reliable.
CRM data stops rotting. Fewer duplicate entries, fewer gaps where somebody was too busy to type.
Here is what calendar sync will not do, and it matters more than the benefits list. It will not fix bad record matching. Einstein Activity Capture associates activity by email address. If your prospect books using a personal Gmail address and your Salesforce contact holds their work address, the meeting attaches to nothing, and no amount of sync configuration fixes it.
Clean your contact data first, or you will automate the production of orphaned calendar events.
Three things will stop you before you click anything.
From Setup, type Einstein Activity Capture into the Quick Find box and select Settings. Click Add Configuration, then choose Google as your email and calendar service.
If you are expecting an on and off toggle, that was the old flow. What you build now is a configuration: a named set of rules you assign users to. One org can run several, which is how you give the SDR team different capture settings from the AE team.
Salesforce gives you three connection methods, and this is where setups stall.
User-level authentication: every rep connects their own Google account. No Google admin needed. Easy to start, slow to finish, because you are chasing people.
Service account: Salesforce provides the service account details, then your Google Workspace admin grants it domain-wide authority and access to your users' Google data. Every user is set up at once and nobody has to connect anything.
Google Workspace Marketplace app: install the Salesforce Einstein Activity Capture app and manage your EAC users inside the Marketplace app itself.
Past roughly a dozen reps, take the service account. The Google admin conversation costs you one meeting. User-level auth costs you a follow-up thread that never quite ends.
Salesforce documents two setups for event syncing, and the difference is bigger than it looks.
Google to Salesforce is the one Salesforce recommends and the fastest way to sync calendar data. Your reps manage meetings in Google Calendar. Changes made in the Salesforce calendar do not sync back to Google.
Salesforce to Google lets reps manage meetings from either their connected Google account or from Salesforce. This is the setup to pick when you actually want to sync Salesforce calendar events with Google rather than only the other way round.
Most teams should take Google to Salesforce. Reps live in Google Calendar. If nobody on your team schedules from inside Salesforce, the second direction buys you conflict scenarios you did not previously have.
Inside the configuration, you choose what to capture (email, events, contacts), which Salesforce records the activity attaches to, and your sharing settings. Then you assign users.
Assign them properly. Since May 2026, Salesforce requires every EAC user to sit inside an active configuration. Users left unassigned lose capture, and Salesforce may auto-create a default configuration with less admin control than you would have chosen for yourself.
Book a test meeting in Google Calendar with an invitee whose email address matches a Salesforce contact. Then wait, and set expectations before you do: Salesforce's own documentation says events typically sync within 5 minutes, and can take up to several hours.
If nothing shows up after a few hours, check the invitee's email address against the contact record before you touch the configuration. Match failures and sync failures look identical from the Salesforce side, and one of them is far more common than the other.
The previous version of this article said Einstein Activity Capture logs events to a shadow database outside Salesforce. That was true when we wrote it. It is not true now, and we would rather correct it than leave it sitting here working in our favor.
Event data synced through EAC is now stored on the Salesforce platform. Meetings save as event records, appear in My Events on the Salesforce calendar, and platform tools such as standard reports can reach them. Contacts sync as standard records too. Salesforce shipped that change automatically, with no action required from admins.
The storage complaint that survives is about email, not calendar. Under legacy capture, email data lives on Salesforce-managed infrastructure outside your org, invisible to reports, flows, and triggers. The Sync Email as Salesforce Activity option, introduced in Summer 25, writes emails as native records instead. If your org set EAC up before then and never migrated, every email captured since is sitting outside your reporting.
Three limits are still stand:
If you read the old version of this page and made a decision on it, that middle paragraph is the one that changed.
Four we see over and over.
Skipping the email address audit. This is the top cause of "the sync is broken" tickets that turn out to be data problems. Run the audit before the rollout, not after the complaints.
Expecting real-time. It is not real-time. Salesforce says five minutes typically and several hours sometimes. A rep who refreshes the record 30 seconds after a call, sees nothing, and decides the tool does not work is a rep you have lost.
Turning on the Salesforce to Google direction by default. If your reps never schedule from inside Salesforce, you have added a sync direction whose only job is to create conflicts. Pick Google to Salesforce and move on.
Assuming personal events stay private. EAC captures from the connected calendar. Decide your capture and sharing settings deliberately, then tell your reps what you decided. Finding out afterwards is how calendar sync projects get killed by the team they were built for.
Disclosure: this is Cirrus Insight's blog, and Cirrus Insight sells a Salesforce sync tool that competes directly with Einstein Activity Capture. Read the next two sections with that in mind. We have tried to be straight about where the free option wins.
Keep Einstein Activity Capture if you are under 100 users, your team just needs meetings visible on the timeline, your pipeline runs on standard objects, and nobody is reporting on activity older than six months. That describes a large share of Salesforce orgs. Paying for a third-party tool to solve a problem you do not have is a bad trade, and we would rather say so.
Look at an integration tool if any of these are true:
Cirrus Insight starts at $14 per user per month for Salesforce Sync. Pro is $21 and adds the inbox sidebar and calendar scheduling. Expert is $49. There is a 14-day free trial, and custom pricing for enterprise. It supports all Salesforce editions and clouds, and works in both Gmail and Outlook.
The trade-off: Cirrus Insight is a Salesforce sync and scheduling tool, not a sales engagement platform. If what you need is multi-step cadences and multi-channel outreach, that is a different category of product, and we are not it.
Five steps, and no Google Workspace admin required to try it.
Install Cirrus Insight for Gmail. Find Cirrus Insight in the Workspace Marketplace, install it, and authorize access to Gmail and Calendar. The sidebar appears inside Gmail.
Connect your Salesforce account. Open the sidebar, sign in with your Salesforce credentials, and grant permissions for syncing events, contacts, and tasks.
Turn on calendar sync. Go to Settings, then Sync Preferences, and toggle on Calendar Sync. Choose your direction: Google to Salesforce, Salesforce to Google, or two-way, which is what most sales teams run.
Set your rules. Decide which calendar events get logged based on invitees, keywords, or event duration. Map event fields to standard or custom objects, and turn on auto-association so meetings attach to the right Salesforce records without anyone thinking about it.
Add scheduling. Share real-time availability from your calendar, let prospects pick a time, and let the booked meeting log itself to the correct contact or opportunity.
Sync runs continuously rather than on a batch schedule, and events land on standard Salesforce objects, so your existing reports and workflow automation can reach them.
Because the activity is stored natively, teams can use existing reporting and operational processes without rebuilding the entire stack.
Yes. Einstein Activity Capture is Salesforce's native calendar sync and it is included with Sales Cloud Starter, Professional, Enterprise, and Unlimited editions for up to 100 users. Setup runs through Setup, Einstein Activity Capture, Settings, Add Configuration. It covers standard objects and retains captured activity for around six months on the Standard tier.
Salesforce documents that events typically sync within five minutes, though it can take up to several hours. Einstein Activity Capture sends updates continuously but not in real time. If an event has not appeared after a few hours, check that the invitee's email address matches a Salesforce contact before you change your configuration.
Choose the Salesforce to Google setup when you create your Einstein Activity Capture configuration. That lets reps manage meetings from either their connected Google account or from Salesforce. The default recommendation, Google to Salesforce, is faster, but changes made in the Salesforce calendar do not sync back to Google.
Yes, as of 2026. Event data synced through Einstein Activity Capture is stored on the Salesforce platform as event records, and standard reports can reach it. Contacts sync as standard records too. Email is the exception: under legacy capture it lives outside your org unless you have enabled Sync Email as Salesforce Activity.
Salesforce retires Lightning Sync in April 2027, and it has not been available to new orgs since Winter 21. Orgs running it against Office 365 with Exchange Web Services must migrate to Einstein Activity Capture by August 2026, because Microsoft disables EWS in October 2026. Treat it as a migration project, not an option.
For two of the three connection methods, yes. Service account authentication needs your Google admin to grant domain-wide authority, and the Google Workspace Marketplace app is installed at the domain level. User-level authentication is the exception: each rep connects their own account and no Google admin permission is required, but the rollout is slower.
Partly, with Einstein Activity Capture. You choose what to capture and which records activity attaches to, but the filtering is broad. Third-party sync tools such as Cirrus Insight add rule-based filtering on invitees, keywords, and duration, plus mapping to custom objects. If certain meetings must stay out of the CRM, that granularity is why teams pay.
Test them before you trust them. Recurring events are where calendar management edge cases show up first, especially when someone edits a single occurrence instead of the whole series. Book a recurring series against a test contact, edit one occurrence, and check what lands in Salesforce. Whatever happens there will happen to every standing customer call your team runs.
If the limits above describe your org, the 100-user cap, the retention window, the custom objects, or the filtering, that is the point at which a third-party integration tool starts paying for itself. Cirrus Insight syncs Gmail, Google Calendar, and tasks to Salesforce, adds calendar scheduling and lead routing on top, and works across every Salesforce edition and cloud.
Start a 14-day free trial and connect your calendar in about ten minutes.