Table of Contents
Please note, Bi-directional Sync is only available for Basic, Professional, and Custom plans. See the Apollo Pricing Guide for more information.
Bi-directional Sync allows two datasets in two different systems to act as one. This kind of synchronization allows you to keep consistent data across multiple platforms. In a practical sense, it helps you prevent stale data and resolves conflicts between two platforms.
Apollo uses Bi-directional Sync to streamline your experience. Refer to the sections below to find out how Apollo protects and integrates your existing contact data from your CRM with the Apollo contact database.
How Apollo Uses Bi-Directional Sync
Apollo allows you to sync contact data between your saved contacts and Hubspot or Salesforce.
Use Bi-directional Sync to keep your contact data consistent between your CRM and your saved contacts from 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 your saved contacts in Apollo, Apollo cross-references your data with 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 connect a Hubspot account as well.
How Apollo Protects the Contact Database
With Bi-directional Sync, 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 means that if you import Salesforce data into your saved contacts in Apollo, users from other companies will not have access to that data.
This protects your proprietary contact information and shields the Apollo database from accidental corruption. Each user has the base instance of Apollo and can sync with Hubspot or Salesforce.