If an org still references the Google Apps integration in Setup or in user training, plan a migration to the modern Gmail Integration and Einstein Activity Capture stack. The work is mostly cleanup.
- Audit the existing integration
Setup, Installed Packages, look for any Salesforce for Google Apps or Salesforce Sidebar package. Note the configuration: which users, which fields, which sync direction.
- Stand up the modern stack
Enable Gmail Integration and Sync, configure Einstein Activity Capture, and confirm Google Workspace allow-listing of the Salesforce add-on.
- Migrate users in cohorts
Move users to the new stack one team at a time. Disable the old package for migrated users; leave it on for users still on the legacy path.
- Reconcile activity data
Legacy emails logged as Tasks remain on the record; EAC-captured emails land in the activity store. Build a unified report using the EAC virtual report types and the standard Task report type.
- Uninstall the legacy package
Once every user is migrated, uninstall the old Salesforce for Google Apps managed package. Verify nothing breaks in production.
- Update documentation
Replace every Google Apps reference in internal docs, training material, and onboarding guides with the current Google Workspace and Gmail Integration terminology.
- The legacy Salesforce for Google Apps package is no longer installable in new orgs. Migrating sandboxes that lack the package requires building the new stack from scratch in the sandbox first.
- Legacy Google Docs attachments stored as URLs on records do not migrate automatically to Files Connect. Plan a parallel migration of file references if needed.
- Google Talk integration is dead. Any Chatter feature referencing presence under the Google Apps brand should be removed during the migration audit.
- Documentation drift is severe. Treat any Salesforce article older than 2020 referencing Google Apps as historical context, not as a configuration guide.