In this article
Scenario
Your organization is upgrading from the legacy Salesforce integration to the Modern Salesforce Integration to ensure a more robust, stable, and future-proof connection for syncing data between Coconut and Salesforce. This upgrade is required to enable advanced staffing features, such as syncing Unassigned Events and enabling Walk-In Syncing.
Solution
The migration process is typically guided by your Customer Success team and must be initiated by an Admin user at your organization.
Migration Steps
Banner Trigger: Once the necessary feature flag (Opt-In Salesforce Upgrade) is enabled by a Coconut Administrator, a clear migration banner will appear on the Salesforce Settings page ([coconut_url]/settings/salesforce).
Initiation: The client administrator must Click the button within the banner to begin the migration process and authorize the new Salesforce integration.
Salesforce Activation: Your Salesforce Administrator must log in to Salesforce and manually Enable the new Coconut integration.
Review Data Carryover: Confirm that all existing Field Mappings and links to synced staff and events have been automatically carried over to the new integration settings. No manual re-entry of mappings is required.
Confirm Entity Syncing: Review the CRM settings page ([coconut_url]/settings/crm) to verify the following:
Entity Type: Confirm that events are syncing to the correct entity type (Leads, Contacts, or Person Accounts).
Matching Algorithm: Confirm the preferred matching algorithm is selected for customer identification.
Finalize Integration: Once you confirm the modern integration is stable and working correctly, a Coconut Administrator must turn off the Opt-In Salesforce Upgrade flag in the Coconut Tools Test Lab.
NOTE:
If your organization uses Salesforce Person Accounts, this requires additional, non-standard configuration steps by a Coconut Administrator and is not part of the self-serve migration flow.
Syncing Logic After Migration
The modern architecture ensures a seamless transition of synchronization state. All event and staff links from the legacy system are preserved.
Pre-Migration Status | Post-Migration Status | Recommended Client Action |
Events were syncing | Events are syncing (No action needed) | Review the Entity Type and Matching Algorithm on /settings/crm. |
Staff was synced | Staff remains synced | Review staff links in the new integration's settings page. |
Person Accounts intended | Syncing to default (Leads/Contacts) | Contact Coconut Administrator for the separate configuration steps required for Person Accounts. |