[Front](https://frontapp.com/blog/2019/04/16/sync-contacts-integrate-front-piesync/ "Front app blog") is the first shared inbox for teams that unifies your email, customer communication channels, and apps in one platform, helping teammates work better together.

frontapp_logo_new

Front

#### What does the 'Avoid Duplicates' option do?

When 'Avoid Duplicates' is enabled in the configuration set-up, PieSync only syncs contacts that have an email address. We use the email address as the main identifier for a contact in order for us to prevent creating duplicates and to match and enrich contacts where possible in both applications.

![](//images.ctfassets.net/f2ysq090txql/6Y233jtNhZQphmahNGNAJX/74ce2980b5ad34fc4206915cb966a126/screenshot-2019-09-03-at-14-19-48.png)

#### What happens when the 'Avoid Duplicates' option is switched off

If the 'Avoid Duplicates' option is switched off we won't be able to double check if contacts that don't have an email address already exist in the receiving app, as such we might be creating duplicates.

That's why we would always recommended to keep this option switched on. If you do want to switch this option off then it is always recommend to first:

*   clean up your database
*   create a backup

#### How do I disable the 'Avoid Duplicates' option?

As a precaution we don’t allow users to disable this setting themselves because PieSync may not be able to reverse a sync and KWCommand does not have a way of restoring contacts either.

**If you read the above and you want to disable the 'Avoid Duplicates' option anyway then just send an email to support@piesync.com and we will disable this checkbox for you.**

What does the 'Avoid Duplicates' option do?  When 'Avoid Duplicates' is enabled in the configuration set-up, PieSync only syncs contacts that have an email address. We use the email address as the main identifier for a contact in order for us to p...

Keller Williams

How do I disable the Avoid Duplicates option for my KW Command connection?

> Do you need to setup a sync from Salesforce data to another app and the data you need sits on the Account instead of the Contact?

The fields you can choose to sync to your other app with are only those from **the contact level.** Data you store on the account is not to be found in the PieSync rules or mappings. (We're working on improving this)

![](//images.ctfassets.net/f2ysq090txql/6cZkxLGnW8QF1BuCDx53NF/44ed5f500a4365045b0e8f1c4aa0c83d/ky-us-6-xh-te-p.gif)

There's a workaround to this if you need this today. This is valid to sync data **from Salesforce to your other app** (continuously). You cannot expect this workaround to update fields on the other object in Salesforce. Possible scenarios?

*   you only want to sync contacts whereby the **Account is from a certain Type**
*   you want to sync contacts but they don't have a **billing address** stored, instead it is stored on the Account
*   if no phone number on the contact is available, then and only then **copy over a phone number from the account**

Here's what you'll need to do.

## Step 1: Create fields on the contact that will take in the account data

The overall principle of this workaround is that we will set up formula fields on the Contact object that replicate the Account fields that we need. Go to the [Salesforce object manager](https://help.salesforce.com/apex/HTViewHelpDoc?id=extend_click_find_objectmgmt_parent.htm) and update the contacts object. Hit 'New'.

![](//images.ctfassets.net/f2ysq090txql/M9SHXs8SDfhlss12LI1Px/76a4ec17ecec24e25275e8ece6d51829/image.png)

You need to make this a formula field. It's a formula since we will rely on Salesforce formula's to take in information from another related object and copy it on the contact record.

![](//images.ctfassets.net/f2ysq090txql/6EUEQUImJBipWkc7qO3ZfL/aca47f62da9f6e0193f1536a8c22734b/image.png)

Choose the format the field will take on the contact level. When in doubt? Choose text. From a Salesforce POV it doesn't really matter that much, since we won't actually make this field visible on the contact layout. But you do want to keep in mind what PieSync rule you'll construct out of this.

![](//images.ctfassets.net/f2ysq090txql/3Oet6FankIHBjCPwSwm5Em/4df57b22b01d99c5ed302387707e6ce8/image.png)

You also need to give it a label. I would suggest you name it something like "Account ...." for easy reference.

![](//images.ctfassets.net/f2ysq090txql/4uvbcGIp8g4EEkGnSHu8YM/c3b967f8c3ed3bb67abf95bae88daa9b/image.png)

Now we get to defining a formula which is easier than you may think. Hit "Insert field".

![](//images.ctfassets.net/f2ysq090txql/37ZYq5AqUV1Fk5WLL44tDF/7a4f0850751d091f8920a85d56adc460/image.png)

Browse to the field on the Account that you need. In this example, I'm taking the industry which is a value stored on Account. Hit next.

![](//images.ctfassets.net/f2ysq090txql/2pf0HHekATjI7qKBeVLZGR/1568758b46e0c45d2c3105e51ce7cb06/image.png)

When Salesforce returns an error like ... Picklist fields are only supported in certain functions, you will need to tweak your formula by prefixing your formula with TEXT and putting the field in between round brackets.

![](//images.ctfassets.net/f2ysq090txql/3cRCuiFsVpggi3PlBbOfD0/e842539c011c65c2741de4c7111de9c3/duu-0-eu-pqbx.gif)

Need to copy over address fields? Those are composite fields and you can spread them out over different lines with BR() codes. For instance, if you want to bring the billing address down the contact level too, copy this text _Account.BillingStreet & BR() & Account.BillingCity & BR() & Account.BillingState & BR() & Account.BillingPostalCode & BR() & Account.BillingCountry_

![](//images.ctfassets.net/f2ysq090txql/5HPem6694DnAV5IvIezfJ4/d43136b498c514b8b84cd99dc77935d3/x-0-r-9-n-9-c-zyh.gif)

You can get creative with formulas. When you know certain contacts don't have a phone number referenced, but their account does, you can create a **fallback number**. The following formula is what I have behind a field named "Fallback Phone". IF( ISBLANK(Phone), Account.Phone , Phone )

This formula first looks at whether a specific phone number for the contact is available, and only if it isn't, it goes and fetches the general phone on the account instead. This way, when you sync Salesforce contacts to Google Contacts, you are more likely to have a phone number referenced.

![](//images.ctfassets.net/f2ysq090txql/2WJJNp0Cq4i2KChpArVD66/bce38f99c874a64c3372474fddd2b081/image.png)

## Step 2: Create a process flow

PieSync's engine relies on an update of the "last modified timestamp" on the contact. The information that we just copied over to the contact can now be read into by PieSync, however, updating it on the account level doesn't make PieSync detect those updates. In fact, PieSync's engine relies on an update of the "last modified timestamp" on the contact. That's where setting up a process flow with the [Process Flow Builder](https://trailhead.salesforce.com/en/content/learn/modules/business_process_automation/process_builder) comes in.

This is necessary so that any updates you make also give a little update - a nudge so you will - to the underlying contact. The Process Flow is going to be a very easy one.

Create a new process by giving it a name. You'll want to do this so you remember why you did this when in 2 years you stumble on this page again.

![](//images.ctfassets.net/f2ysq090txql/5boXJaYgjGhHy5cObqBXcc/26702adf9af6ad44d71ee0e3fd194454/image.png)

We're going to keep this process very simple. This process flow will run each time an Account is created or edited, so that's exactly what we're putting in the fields it's asking for.

![](//images.ctfassets.net/f2ysq090txql/76qfoLnzwMb98UmcqKCdk2/9fece0d6f9a34cf9571edbf57ae613bd/image.png)

Next step - criteria. We want this process flow to run whenever the fields that we are copying over actually change. You can potentially set this to "No criteria - just execute the actions" too.

![](//images.ctfassets.net/f2ysq090txql/2JIF4Bfod7VYTZSpye5HZu/c35cf1dbb27b663affc55bbbc078ef97/image.png)

Under action, we need to force a change on the contact. Choose the action "Update records" and refer to the Record type of Contacts. Here, since I'm never using the business fax number anyhow, I'm updating that fax value with a random number.

![](//images.ctfassets.net/f2ysq090txql/4KLWCumZZc23gV7EapvSiy/29f551423e76095c7b8c9aa8ea917d00/image.png)

Activate this process flow.

## Step 3: Now you can set up those field mappings in PieSync!

The rules will allow you to refer to filter out contacts that only have a certain value on the account. You refer to the field on the contact, but based on the steps you completed above the information is actually coming from the account.

![](//images.ctfassets.net/f2ysq090txql/2sYmLyo93GpZdHLxvox0Dt/ff77fa031f1040647a571346d81a6bc5/image.png)

And it also works in the mappings!

![](//images.ctfassets.net/f2ysq090txql/5LDVse7ESQFhUgdImh1p4n/3bc91eb915991e2fd0af234280f52e83/image.png)

Do you need to setup a sync from Salesforce data to another app and the data you need sits on the Account instead of the Contact?  The fields you can choose to sync to your other app with are only those from the contact level. Data you store on th...

Want to learn more?

Salesforce: Copying account data to contact level

At PieSync we feel it is important that our end-users are aware of these attention points with regards to proper deployment of self-hosted applications.

## Terms & Conditions (T&C)

### Users connecting self-hosted applications agree to the following T&C:

*   The **version** of the self-hosted application will be kept up to date with the one of the partner-hosted application. PieSync will do its best to keep backward compatibility with older versions, but cannot be held accountable in case an old version leads to some unexpected API behavior.
*   The self-hosted domain will be exposed in a secure way. **Non-https domains will not be accepted**.
*   The infrastructure of the self-hosted application has to be able to deliver acceptable **API** **performance** (normal response times, limited time-outs, high availability, etc).  
    In the interest of maintaining stable syncs for all its users, PieSync has the right to stop - or at least reduce capacity for - a sync of a customer in case it is seriously underperforming. We will inform the customer when we do this and look for solutions.
*   As PieSync has no experience with - and cannot be fully aware of - the exact infrastructure setup of the self-hosted application, the PieSync **support** team cannot be held responsible for debugging basic connectivity issues with self-hosted applications.  
    We recommend an IT administrator of the self hosted application to set up PieSync in this case. The PieSync support team will obviously try to help out where possible (as we do for our other users).
*   Users cannot hold PieSync accountable if their data was sent to an unintended recipient due to **wrong input when specifying** **the target domain**.  
    PieSync will assure that some malicious domains are automatically being blocked, but cannot guarantee a full coverage against all malicious domains.

### Definitions

_**self-hosted application**_**:** Under self-hosted applications PieSync considers all applications that are not hosted directly on the domain of the partner application.

For example you want to integrate with the application "My Favorite CRM", which is on the domain myfavoritecrm.com. In that case all applications which are not hosted on myfavoritecrm.com are considered self-hosted applications by PieSync. This can be any of the following:

*   An application i**nstalled on your own PC** (but still connected to the internet)
*   An application **hosted by yourself on a cloud server** (for instance on Amazon Web Services)
*   An application **hosted by an external cloud hosting provider** (for instance on the domain myfavoritecrm-hosting.com)

_**partner-hosted application**_**:** Under partner-hosted applications PieSync considers all applications that are hosted directly on the domain of the partner application. These applications are considered stable by PieSync, and run the latest version of the software.

## FAQ

### Why does PieSync impose additional Terms & Conditions (T&C) for self-hosted applications?

A self-hosted application can work in exactly the same way as the application hosted by the partner but in practice there are often some differences:

*   Application version (and hence API versions) can differ with the parter-hosted application, which can lead to different sync functionality
*   The API performance of the self-hosted application - and hence of the sync - could be below the standard we're used to for the partner-hosted application
*   The IT infrastructure of the self-hosted application can prevent us from taking certain actions to improve service
*   There is a shift of liability in allowing an end-user to specify the domain that needs to be connected to. When an end-user enters the wrong domain, authentication data or customer data will be sent to potentially malicious recipients.

At PieSync we feel it is important that our end-users are aware of these attention points with regards to proper deployment of self-hosted applications.  Terms & Conditions (T&C)  Users connecting self-hosted applications agree to the following T&...

How to manage your PieSync account and set up billing

Account

Self-hosted applications - Terms & Conditions

In case you couldn’t find the answer in our knowledge base, feel free to reach out via email at support@piesync.com or chat with us live! You can see the live chat option on the PieSync website or PieSync dashboard when you're logged in. **We love to help you out!**

<TipBox>**Live Support (chat) - CET from 9 AM to 5 PM**</TipBox>

<TipBox>**We reply within 24 hours via support@piesync.com from Monday to Friday** </TipBox>

<InfoBox>Book a call with us [here](https://calendly.com/piesync)</InfoBox>

In case you couldn’t find the answer in our knowledge base, feel free to reach out via email at support@piesync.com or chat with us live! You can see the live chat option on the PieSync website or PieSync dashboard when you're logged in. We love t...

Get personalized help for all kinds of errors as well as unexpected behavior in your syncs

I couldn't find my answer, how can I get support?

<Embed src="https://www.youtube.com/watch?v=2Le-Z2eqlbs" />

In the connection settings you have the option to choose a winning app. It looks something like this:

We need you to choose the 'winning app', because in the rare occasion that PieSync does encounter a conflict, it needs to know how to act.

![](//images.ctfassets.net/f2ysq090txql/6xB8eDykmAW09E8kkMNpFa/987b144cf09ea8bf3aadce919d3df302/image.png)

**Chances of having a conflict are very small.** PieSync will only encounter a conflict in two scenario's:

### 1. Most commonly: during the initial sync

When matching your databases it is possible that there's a difference between two contact fields. For instance, in Autopilot the First Name of a contact is 'Dave' while in Intercom the first name of that same contact states 'David'. This is a conflict that PieSync will resolve by looking at the winning app.

<TipBox>When your winning app has empty fields, we won't delete any field information in the other app.</TipBox>

### 2. Very rare: When a contact in sync is being updated in both apps at the same time

In the rare occasion that the field of the same contact is being altered from both apps at the exact same time, PieSync will encounter a conflict. In this case, PieSync will have the losing app take on the value of the winning app.

<InfoBox>Once a contact is in sync, there are inherently no conflicts. The Conflict management Setting does not dictate [sync direction](/help/features/sync-direction/).</InfoBox>

  In the connection settings you have the option to choose a winning app. It looks something like this:  We need you to choose the 'winning app', because in the rare occasion that PieSync does encounter a conflict, it needs to know how to act.  Ch...

The essentials of setting up a two-way or one-way sync between your apps.

Getting started

When a field's value is different (conflict management)

## What exactly does this mean?

PieSync is able to expose Company related fields when syncing Contacts. Let's have a look at the example below:

*   The orange section shows the Contact record, together with its Contact fields.
*   The green section shows the Company record, together with its Company fields.
*   The blue arrow reflects to the Company fields available on the contact record (= exposing Company related information).

![](//images.ctfassets.net/f2ysq090txql/5AwryUnnyO5JvgHo1VXtoH/c547b9e67358ca22faf86196832bbea9/screen-shot-2020-01-13-at-10-29-58.png)

## How can we distinguish between Contact and Company fields?

Company fields will always have a \[Company\] prefix.

![](//images.ctfassets.net/f2ysq090txql/UQZAdXkNoqgKekrsMdSPU/62ce5a1c634d89cccd52057df9124fb9/screen-shot-2020-01-13-at-10-49-07.png)

<TipBox>Company fields can be used in both the PieSync rules and custom mappings.</TipBox>

## Limitations

<WarningBox>Syncing company related fields is limited to a one-way direction.</WarningBox>

1.  The one-way nature of these fields means that you are able to filter based on \[Company\] fields but can't update them via the actions.

![](//images.ctfassets.net/f2ysq090txql/2XmSK87v4COYJnziTGgmQP/8b1fa7452b0514c2578385bd4a4b7722/screen-shot-2020-01-21-at-11-19-03.png)

2.  Echoing this behaviour to the custom mappings section, will result in an arrow pointing in one direction.

![](//images.ctfassets.net/f2ysq090txql/yVVt5QooqEdAYQsLtRCg1/6955288f30387073a55549fcb2a28903/screen-shot-2020-01-14-at-11-46-31.png)

## Possible use cases

1.  Syncing contacts based on the Number Of Employees towards MailChimp in order to create a specific segmentation allows you to create specific marketing targets.

![](//images.ctfassets.net/f2ysq090txql/2ic9NJt55wUmdNyXKUGDrw/119c298f34f6195b65bcee36c73d15ae/screen-shot-2020-01-13-at-11-03-05.png)

2.  Similar as above, Syncing contacts based on the Annual Revenue towards ActiveCampaign in order to create specific segmentation.

![](//images.ctfassets.net/f2ysq090txql/1CkCWNZOPQl3eFXWw3MZxX/609d768fd41c6d3e67ad7de1bb114bfe/screen-shot-2020-01-14-at-12-03-23.png)

## Integrations

This feature has been released for the following apps:

*   [Bitrix24](/help/connector-apps/bitrix-crm/)
*   [HubSpot](/help/connector-apps/hubspot/)
*   [Ms Dynamics 365](/help/connector-apps/microsoft-dynamics/)
*   [Ontraport](/help/connector-apps/ontraport/)
*   [Outreach](/help/connector-apps/outreach/)
*   [Salesforce](/help/connector-apps/salesforce/)
*   [SugarCRM](/help/connector-apps/sugarcrm/)
*   [Zendesk](/help/connector-apps/zendesk/)

<InfoBox>We will gradually add other applications to this list.</InfoBox>

What exactly does this mean?  PieSync is able to expose Company related fields when syncing Contacts. Let's have a look at the example below:  The orange section shows the Contact record, together with its Contact fields. The green section shows t...

Syncing company related information on the contact level.

_You just made the perfect configuration. And you are ready to start syncing all that contact data. You close your eyes and press the button. Suddenly you've been redirected to our Health. Nothing seems to be happening. You're slightly panicking. Palms are sweaty, but then you see a little icon beneath the empty timeline. It says: 'Scanning your data - this might take some time...'. Well, what now?_

![Screen Shot 2020-08-31 at 16 27 35](//images.ctfassets.net/f2ysq090txql/2mvgNWBKveiWZvUKWYDfwa/05b299ba5c6cd0972d50496e8c554c28/Screen_Shot_2020-08-31_at_16_27_35.png)

Great question! **What is our system actually trying to communicate to you?** Or better yet, how does our sync work? In this article we'll take a closer look at some of the dashboard states that might not be so obvious.

## Active and listening for changes

This is probably the message that you'll see most often. This means PieSync has synced everything it was able to sync. Now it's **actively monitoring your contact databases** for any recent updates it needs to sync. PieSync syncs all your data in real time, which means it will scan every contact approximately every 4 to 5 minutes. When it detects an update to a contact in app A, it will immediately sync that data in app B.

## Scanning your data - this might take some time...

This is the primary stage. When you're syncing small databases with each other, you might not even notice this state existed. PieSync is **scanning** your databases, **processing** the data, looking at the email addresses to match contacts, the properties of each contact in that database. When you have set up filters, it needs to know which contacts to sync and which must remain outside the sync.

## Synchronisation has been paused. Resume it!

This state speaks for itself. You can only pause the sync yourself. When you pause a sync, you don't delete the connection, but you instead ask it to stop actively monitoring your data for updates and changes. In this state no data will be synced by PieSync.

## We're having trouble connecting to the timeline. (Reconnecting/Trying again in 2…)

This message just means that we **couldn't visualise the sync activity**. This normally only occurs shortly and refreshing the page normally always fixes it. There won't be anything wrong with the sync. It's just the UI that has difficulties analysing the activity. It could mean that we won't see the contact creations/updates on the dashboard for a short time, but that should recover on its own soon.

## Possible changes detected - waiting in queue

If it's in the queue, this usually means one of two things:

1.  There is **another sync running** on one of the same accounts
2.  There is an **unusually high load** on our platform (meaning there will be many more syncs that are queued, not only for this user)

However, if this takes longer than 24 hours, we recommend contacting customer support (support@piesync.com). They can check if everything is going as planned.

## We've sent heavy traffic to one of your apps, we'll wait for it to cool down before proceeding

The underlying principle of this message is that some of the apps we integrate with have a limit on the amount of requests we can send. This can be a limit per second, per minute or even per hour or per day. At the moment we hit such API limits, we have to **wait until the applicable time period has passed** before we can do new requests to their API. Once the time has been exceeded, we will automatically try again, so you don't need to take any action on this.

You just made the perfect configuration. And you are ready to start syncing all that contact data. You close your eyes and press the button. Suddenly you've been redirected to our Health. Nothing seems to be happening. You're slightly panicking. P...

What are the Different Sync States on the Health page?

<InfoBox>**[GETTING STARTED GUIDE](/help/features/getting-started/): How to set up a new connection?**</InfoBox>

<InfoBox>[**ALL FEATURES EXPLAINED**](/help/features): **All our features/functionality explained in detail - no app-specifics.**</InfoBox>

Front is the first shared inbox for teams that unifies your email, customer communication channels, and apps in one platform, helping teammates work better together.

**Below you'll find detailed information, specifically for Front integrations:**

## Supported Front Integrations

<Widget src="https://cdn.piesync.com/widget.js" left="front" />

## Authorizing Front

**When you click 'next', a pop-up window appears asking you to log in and allow access**.

![](//images.ctfassets.net/f2ysq090txql/31petJB0xFbpnrcGMI63uu/0d9bc91a0a03830765240c6884377fa7/screen-shot-2018-03-30-at-15.09.30.png)

**For Front, we need authorization per TEAM. This means you need to set up a new connection for each TEAM you want to keep in sync.**

![](//images.ctfassets.net/f2ysq090txql/5VlWvsKJvRX4zeL6F63E11/e08654d6a1f840c545f78373f3f77310/screen-shot-2018-04-05-at-15.34.41.png)

<InfoBox>The integration will not have access to your private contacts. More info can be found [here.](https://dev.frontapp.com/#limitations)   
</InfoBox>

If you already authorized Front account(s) in the past or in any other PieSync integration, you'll be able to skip the first part of the authorization and choose from your **CONNECTED ACCOUNTS**.

![](//images.ctfassets.net/f2ysq090txql/3Hrs8zJACKaa1gdqmgrhvC/df09a5d95cab419472b4bcefed88cbdf/screen-shot-2018-03-30-at-15.14.28.png)

<WarningBox>**PieSync only syncs the Team Contacts and not the Private Contacts.** This is important to remember as Front's search bar prioritised your Private Contacts over your Team Contacts, potentially misleading the actual sync results.</WarningBox>

## \[IF\] Supported Conditions/Filters

*   IN GROUP
*   FIELD VALUES (_INCLUDING CUSTOM FIELDS_)
*   ALREADY EXISTING IN APP YOU SYNC WITH 

![](//images.ctfassets.net/f2ysq090txql/6trarJaVitu3rpAUgN5cCS/e9e137a44f88bb4fcdd8b5f9baa575c2/screen-shot-2018-03-30-at-15.13.21.png)

## \[THEN\] Supported Actions

*   ADD TO GROUP
*   REMOVE FROM GROUP
*   ADD TO TEAM (IF NEW)
*   UPDATING FIELD VALUES (_INCLUDING CUSTOM FIELDS_)

![](//images.ctfassets.net/f2ysq090txql/1WbIyEQLaOff0e9cIsIKKM/5f1feb61f2a891b23b42a1caa4db8630/screen-shot-2018-03-30-at-15.13.40.png)

## Default Field Mapping

Depending on the other app you're syncing with, you'll see a number of standard Front fields being mapped by default. For instance, in a connection with Google Contacts, the default field mapping looks like this:

![](//images.ctfassets.net/f2ysq090txql/4wWoEmgOLXEDIRhcBMLnKy/15784e8a5cc4e1b1c341b90c6471532a/screen-shot-2018-03-30-at-15.13.52.png)

<InfoBox>PieSync syncs the default name field(s) that come with the apps. Sometimes they have a different structure in both apps you connect. E.g. first and last names are separate in app A and joint in a single field in app B. In the background, PieSync joins first and last names together from app A to B and separates them again from app B to A. Our algorithm is smart about which part it updates in app B.</InfoBox>

## Customizable Field Mapping

You can custom map your Front Custom Fields and any additional standard fields that aren't included in the default mapping yet. Bear in mind a mapping between two fields can only exist if the types of fields are compatible, and the particular compatibility will determine the direction of the mapping as well. More information on Customizable Field Mapping [here](/help/features/new-customizable-field-mapping/).

![](//images.ctfassets.net/f2ysq090txql/3axazc43helbYDLuLvgrGx/890de6d4c25e09cac64839f342cca282/screen-shot-2018-03-30-at-15.14.03.png)

## Additional Options

### Syncing Deletions

Currently, there are no Front integrations on the PieSync platform that support our [deletions sync](/help/features/syncing-deletions/).  

### Syncing Unsubscribes

Currently, there are no Front integrations on the PieSync platform that support our [unsubscribes sync](/help/features/syncing-unsubscribes/).  

<InfoBox>The availability to Sync Unsubscribes/Deletions is app and connection dependent. If the box (screenshots above) is not there to tick, it's simply not possible. We need to be able to detect unsubscribes/deletions on one side and at the same time be able to create add the tag 'PieSync Unsubscribes' or ‘PieSync Trash’ on the other side. More Information on Syncing Unsubscribes [here](/help/features/syncing-unsubscribes/) or on Deletions [here](/help/features/syncing-deletions/).</InfoBox>

<TipBox>Thanks to the feedback we have already received, we created a list of popular apps that we’re going to work on very soon. By [voting them up in our pipeline](http://www.piesync.com/connections/#vote), YOU decide which connectors we’ll release first. If you don’t see your app on the list or need any further help, drop us a line - [support@piesync.com](mailto:support@piesync.com).  **Don't forget to read our [blog](http://blog.piesync.com/) for the latest in productivity, apps, and technology!**</TipBox>

GETTING STARTED GUIDE: How to set up a new connection?  ALL FEATURES EXPLAINED: All our features/functionality explained in detail - no app-specifics.  Front is the first shared inbox for teams that unifies your email, customer communication chann...

How to set up specific apps, what rules are available and mapping overviews

Supported Apps

A few considerations to take in reference to some of the free/native/other 3rd party integrations out there:

1.  Is it a [full 2-way sync](/help/features/sync-direction/)?  Put differently: is it capable of syncing your entire history of contacts, and not just trigger one-time updates to new contacts?

2.  Is it being as actively developed as PieSync?  (After all, it's not just the _core_, but the _only_ business our ever expanding [team](http://www.piesync.com/about/) is involved in.)

3.  Can it sync directly to [all the apps your team](/help/faq/which-connectors-do-you-support/) is using? What happens if your company wants to switch software?

4.  Does it offer the same level of [elaborate IF/THEN segmentation](/help/features/conditions-and-actions/)?

5.  Does it let you choose a [master app](/help/features/master-app/), in other words: can you control which app gets priority in case of conflicts?

6.  Can it map your app's [custom fields](/help/features/new-customizable-field-mapping/)?

7.  Can it handle contacts being [deleted](/help/features/syncing-deletions/)?

8.  What about contacts [unsubscribing](/help/features/syncing-unsubscribes/) from my marketing lists? 

9.  Can you seek [support](/help/faq/i-didn-t-find-the-answer-i-was-looking-for-here-how-can-i-get-in-touch/) specifically about the sync features, or is customer support aimed at the generic app functionalities?

10.  How transparent is the sync? Is there a [feedback log](/help/features/pie-sync-dashboard-logging/) to inform you on which contacts got synced and when?

&nbsp;

<InfoBox>Related articles:  
[What's the difference between PieSync and Zapier?](/help/faq/what-s-the-difference-between-piesync-and-zapier/)</InfoBox>

A few considerations to take in reference to some of the free/native/other 3rd party integrations out there:  Is it a full 2-way sync?  Put differently: is it capable of syncing your entire history of contacts, and not just trigger one-time update...

Why prefer PieSync over other (native/free) integrations?

Running a sync for the first time can sometimes take a while.

*   In case you have a lot of contacts in your applications, the initial sync will take a bit longer, even if you configured PieSync only to sync a subset of your contacts. 
*   During the initial scan, we need to process all of your contacts (also the contacts outside the chosen subsets) to avoid duplicates during the sync.
*   Once the sync status is active _(green)_, it should never take more than 2 to 3 minutes for any update or create to appear.

<TipBox>Notice anything unusual? Contact us at support@piesync.com</TipBox>

Running a sync for the first time can sometimes take a while.  In case you have a lot of contacts in your applications, the initial sync will take a bit longer, even if you configured PieSync only to sync a subset of your contacts. During the init...

Why does it take so long to see the first contacts appear?

## What is possible? 

### Contacts 

The beating heart of our syncing engine can help you with keeping your contact information in sync, at all times. 

Depending on the app you're using, you might see alternative names such as Audiences, Customers, Users, etc.
The basic principle is that we display the same name as the entity the app uses as its contact repository. 

In the example below, we are syncing contacts between HubSpot and QuickBooks. In this case, the respective contact repositories are called "Contacts" and "Customers":
![Screen_Shot_2020-06-17_at_18_54_14.png](//images.ctfassets.net/f2ysq090txql/6QtXWvDkZby3VGbRueaieA/b1869c44db996b8e5b63234cfa6f5760/Screen_Shot_2020-06-17_at_18_54_14.png)

### Leads

Similar to our contact sync, our engine is also able to sync the leads entity in your apps. 

<InfoBox> Learn more about our Leads sync [here](https://www.piesync.com/help/faq/syncing-leads/ "Syncing Leads"). </InfoBox>

#### Some key take aways: 

- Some applications have a standalone Leads entity. PieSync is able to incorporate that in the sync. You can choose which contact type you wish to sync during the 3rd step of the configuration process, as shown in the example below for Microsoft Dynamics 365:
![Screen Shot 2020-06-17 at 20 09 24](//images.ctfassets.net/f2ysq090txql/7LMmtESf1P17iJx6aqGPId/fc8ee1f5f550b1cb8b04ff6a42a13654/Screen_Shot_2020-06-17_at_20_09_24.png)

- It might be that your application doesn't have a leads entity, while you can see leads in your account. In such cases, the leads are stored within the Contacts section and distinguished by a particular field (e.g "Status"). We are able to incorporate those in the sync as well. 


### Companies

Also known as "Accounts" or "Organizations", this is the third entity that PieSync is able to sync. It does come with a nuance though.

- Our companies sync is only available for a limited number of applications. A full overview of the supported apps can be found at the bottom of [this page](https://www.piesync.com/help/faq/can-i-sync-company-account-information/ "Syncing Company / Account info").

- PieSync only offers a company to company sync. This means companies or accounts can't be synced to a contact entity. Doing so will result in the following error message: "The selected combination of entities cannot be synced"
![Gif KB](//images.ctfassets.net/f2ysq090txql/6g2SKlBqZ5ohwXATA8uYX1/77dea4fe62601ad7c3984637d9e1d0d0/Gif_KB.gif)

- For some integrations, PieSync is able to expose Company related fields when syncing Contacts. This allows you to sync company related information on the contact level. 
More information on this can be found [here](https://www.piesync.com/help/faq/syncing-company-related-information-on-contact-level/)

When available, these fields will be visible in the sync configuration as shown in the example below:
![Screen Shot 2020-06-17 at 21 11 39](//images.ctfassets.net/f2ysq090txql/nkle72OLNjoqH01AmkKCj/2119244dc2be432fe3ff011dd5ff046e/Screen_Shot_2020-06-17_at_21_11_39.png)
<InfoBox> Learn more about the possibilities of our Companies sync [here](https://www.piesync.com/help/faq/can-i-sync-company-account-information/ "Syncing Company / Account info"). </InfoBox>


## What PieSync doesn't sync today 


- Deals / Opportunities. 
- Tasks
- Notes / Logs / Activities
- Orders / Products
- Emails
- Invoices / Quotes
- Campaigns
- Custom Objects

At this point, we focus on syncing your contact data. The entities listed above cannot be synced at the moment. However, this doesn't mean we won't support them in the future. On the contrary! Our developers are currently working on ways to implement some of these features as well.

Feel free to share what you'd like to sync through [this small survey](https://piesyncforms.typeform.com/to/Erb2jN "typeform").
It only takes a few minutes and allows us to capture valuable feedback regarding the priority of these features. 

Additionally, by filling in this survey, you’ll automatically receive a notification when the feature you’re looking for is being launched.


What is possible?  Contacts  The beating heart of our syncing engine can help you with keeping your contact information in sync, at all times.  Depending on the app you're using, you might see alternative names such as Audiences, Customers, Users,...

What does PieSync sync? 

## 5 quick steps to do before you hit "Sync!"

![](//images.ctfassets.net/f2ysq090txql/54ScpBCj0sW99qoJjUfpuR/86ae7b3b17adbd3463fd0bf62dc4f5d4/larry.gif)

<InfoBox>Hesitant to "Start syncing now" after you configured a sync?  
Follow these steps to gain peace of mind! </InfoBox>

**1) Pause other syncs to your apps**

Turn off or pause any existing integrations in parallel (other PieSyncs, Zapier, Fullcontact, etc). Leaving these syncs on can lead to unpredictable results. Check your CRM's account settings, you may already be syncing some data (one way).

**2) Back up your data**

In the next step, we'll give you some tips on cleaning up your data. That's why it's wise to make a backup first should you be too enthusiastic in cleaning contacts. [Google Contacts, Icloud, ContactsPlus save a temporal state of your Contacts so you can always go back to a state prior to a sync](/help/want-to-learn-more/revert-a-sync/). Have contacts on your phone? [Here's a checklist.](/help/faq/get-your-phone-contacts-in-sync/)

**3) Time to clean**

Delete contacts you won't ever need anymore. You may want to empty Google's ["Other Contacts" folder](https://support.google.com/mail/answer/1069522?hl=en&visit_id=1-636459121173695326-1876924094&rd=1) filled with legacy contacts. Make sure your source & target data is rid of duplicates. Use the “find & merge duplicates” features of Google/iCloud/Outlook or from your CRM. 

*   [Instructions for Google Contacts](https://support.google.com/mail/answer/1069522?hl=en) (+ [9 extra tips provided by FullContact](https://www.fullcontact.com/blog/clean-up-google-contacts/))
*   [Instructions for iCloud](https://support.apple.com/en-us/HT203565)
*   [Instructions for Outlook.com](http://ccm.net/faq/39487-outlook-com-how-to-remove-duplicate-contacts)
*   [Instructions for CRM, for example Pipedrive](https://www.google.com/search?q=dedupe+pipedrive+contacts)

Once the sync is started, you can continue performing these clean up operations. PieSync [can detect cleaning](/help/want-to-learn-more/cleaning-up-duplicates-in-your-crm/) up contacts.

**4) Do a sanity check**

Perform a human check on whether the find&merge duplicates did its job. Merge whichever duplicates that weren’t detected automatically, delete old contacts or old addresses. By default, PieSync will only sync contacts that have an e-mail address, which is what we then use on the other side of the sync to keep your contacts unique. 

**5) Run a test sync**

If you want to test PieSync on a limited dataset, you can apply some intelligent rules to narrow down the sync. 

<Embed src="//www.youtube.com/embed/Bk_OSkK-JvQ" />

  

*   For instance, adapt rules to only sync contacts with a specific dedicated test-tag, and have it update a specific field on the other side as extra proof. If you only tag one contact in your CRM with this very specific tag, only this contact will sync. The other contacts remain untouched.![](//images.ctfassets.net/f2ysq090txql/4H8IOtuSEcAwFFWpEMv4A4/4315bb78f5091ac100c72fcc71ac5f69/blob)
*   Don't have tags in your app? Consider creating a test contact with a dummy or test e-mail address and only leave this rule enabled. Works just as well. Just know that sometimes a dummy e-mail address won't get created inside your ESP client.
    
    ![](//images.ctfassets.net/f2ysq090txql/3B3AD2S36pvyK2G2UtmyfS/b460cd55b694b72ea77f9a1f4e57f04e/blob)
    
*   Furthermore, you can always disable rules to prevent contacts from being created into an environment where you want to avoid unexpected contacts from being pushed towards! 
    
    ![](//images.ctfassets.net/f2ysq090txql/2HCSnFK21Pn9hVNi3Q1yTV/99282c381394ca36cbfc1bc7e6e1e1d1/screen-flow.gif)
    

[What are you waiting for? Start syncing! ](/help/features/getting-started/)

<TipBox>Still in doubt? Feel free to [schedule a call](https://calendly.com/piesync) with our support team.</TipBox>

5 quick steps to do before you hit "Sync!"  Hesitant to "Start syncing now" after you configured a sync? Follow these steps to gain peace of mind! 1) Pause other syncs to your apps  Turn off or pause any existing integrations in parallel (other Pi...

Preparing your data for PieSync

hubspot logo

HubSpot

Copper-icon-circle-pink

Copper

Contacts+ Logo Mark (1)

Contacts+

salesforce

Salesforce

aircall-icon@2x (1)

Aircall

google contacts logo

Google Contacts

sharpspring

SharpSpring

unnamed (4)

123FormBuilder

1CRM-logo-box

1CRM

logo-3dcart

3dcart

act!

Act! 365

actpremium

Act! Premium

apps.41598.37145b45-309a-44d2-8a3a-8ef5dd923138.b03415bf-0d24-4925-924c-d111c87e195a.e4b8a9d0-ed9e-44f4-81d3-524fbe3257b6

Actionstep

activecampaign

ActiveCampaign

activedemand

ActiveDEMAND

activetrail-1502192111-logo

ActiveTrail

Acumatica

Acumatica CRM

agendor_logo

Agendor

agilecrm

Agile CRM

allclients

AllClients

amocrm

amoCRM

apollo.io logo 

Apollo

apptivo

Apptivo

aproplan

Aproplan

apto_logo

Apto

Aritic-Logo

Aritic PinPoint

Aritic Sales CRM

AT & T

AT&T Office@Hand

autoklose logo png 

Autoklose

autopilot

Autopilot

aweber

AWeber

benchmark

Benchmark

bexio

bigcommerce

BigCommerce

bigcontacts

BigContacts

bill.com logo

Bill.com

bitrix

Bitrix24 CRM

bombbomb

BombBomb

bookeo

Bookeo

boomtown

BoomTown

Brivity CRM

btcloudphone

BT Cloud Phone

bubble_piesync

Bubble

bullhorn

Bullhorn

campaignmonitor

Campaign Monitor

campaigner

Campaigner

capsulecrm

Capsule

cats-logo

CATS

chargebee

Chargebee

Chime-Logo (1) (1)

Chime

cin7_logo_piesync

Cin7

cxsocial

Clarabridge Engage

Classy-icon-coral

Classy

click-send_logo_piesync

ClickSend

clio

Clio Manage

closeio

Close

companyHub

CompanyHub

connectwisemanage

ConnectWise Manage

constantcontact

Constant Contact

Contactlab Marketing Cloud

contactually

Contactually

convergehub

ConvergeHub

Seva (formerly ConvertKit)

ConvertKit

bpmonline

Creatio

Crisp

currentrms

Current RMS

datavalidation

DataValidation

daylite

Daylite

d-logo-L-transparent

Debitoor

Delivra

desk

Desk

logo-digitaleo

Digitaleo

directmailmac

Direct Mail for Mac

DD-roundel-512x512

dotdigital Engagement Cloud

dotloop

Dotloop

drift_logo

Drift

drip

Drip

dubb-logo-full

Dubb

easybill

EasyBill

efficycrm

Efficy CRM

Start syncing your Front contacts
two-way with more than 240 other apps

Discover how PieSync can make your cloud apps work together

Accurate & real-time data

Save time

Easy & Secure

Free Trial

Start syncing Front with one of our 242 apps

Help Articles related to syncing Front

How do I disable the Avoid Duplicates option for my KW Command connection?

Salesforce: Copying account data to contact level

Self-hosted applications - Terms & Conditions

I couldn't find my answer, how can I get support?

When a field's value is different (conflict management)

Syncing company related information on the contact level.

What are the Different Sync States on the Health page?

Front

Why prefer PieSync over other (native/free) integrations?

Why does it take so long to see the first contacts appear?

What does PieSync sync?

Preparing your data for PieSync

Start syncing your Front contacts two-way with more than 240 other apps

Discover how PieSync can make your cloud apps work together

Accurate & real-time data

Save time

Easy & Secure

Free Trial

Start syncing Front with one of our 242 apps

Help Articles related to syncing Front

How do I disable the Avoid Duplicates option for my KW Command connection?

Salesforce: Copying account data to contact level

Self-hosted applications - Terms & Conditions

I couldn't find my answer, how can I get support?

When a field's value is different (conflict management)

Syncing company related information on the contact level.

What are the Different Sync States on the Health page?

Front

Why prefer PieSync over other (native/free) integrations?

Why does it take so long to see the first contacts appear?

What does PieSync sync?

Preparing your data for PieSync

Start syncing your Front contacts
two-way with more than 240 other apps