Overview
Please note, bi-directional syncing is only available on certain plans. See the Apollo Pricing Guide for more information.
Bi-directional syncing allows two datasets in two different systems to act as one. This kind of synchronization allows you to keep consistent data across multiple platforms. It also helps you prevent stale data and resolves conflicts between Apollo and your CRM.
Apollo uses bi-directional syncing to streamline your experience. Refer to the following sections to discover how Apollo protects and integrates your existing contact data from your CRM with the Apollo contact database.
How Does Apollo Use Bi-Directional Syncing?
Apollo allows you to sync contact data between your saved contacts and HubSpot or Salesforce.
Use bi-directional syncing to keep your contact data consistent between your CRM and your saved contacts in the ever-evolving Apollo database.
Since the sync is bi-directional, you can both sync your CRM to your saved contacts in Apollo and sync your saved contacts in Apollo to your CRM. Do this regularly to keep your contact data up-to-date on both platforms.
When you sync your CRM with Apollo, Apollo cross-references your data with your saved contacts in the Apollo database and enriches any missing or inaccurate data.
Please note, you can only connect 1 CRM to Apollo at a time. For example, if you connect a Salesforce account to Apollo, you can't also connect a HubSpot account.
How Does Apollo Protect Its Database?
With bi-directional syncing, it is possible to import or export corrupt data. To protect your data and the Apollo database from data pollution, you work within your own instance of Apollo.
This protects your data and shields the Apollo database from accidental corruption. Each user has the base instance of Apollo and can sync with HubSpot or Salesforce.