PieSync Help Center

Explore our help center for quick answers

KW Command and Outlook

Frans Leys

If you're new to PieSync, this guide will you get started with the essentials.

When you sync Command with Outlook, you can customize the following three elements to your sync.

  1. Sync direction
  2. Connection rules
  3. Connection settings
  4. Field mappings

There is no one typical use case, no one best practice that can be documented to sync Command and Outlook. We'll provide various different tips, rules, and field mappings for you to draw inspiration from. You don't have to use them all!

Sync direction

Start by choosing the direction of your sync. You can consider three different settings.

  1. Most agents opt for a two-way sync, allowing records to be modified by PieSync in either system. This is the setup we see most commonly as it would enable contacts to move from Command into Outlook as well as the other way round.

KW- Outlook 2way arrows

  1. You could choose for a strict one-way sync from Outlook into Command. You could for instance only sync certain Outlook contacts into Command in a certain way. And you don't want Command to be touching your Outlook contacts ever.

KW-Outlook one-way arrow

  1. Of course, there's the opposite way too. Through PieSync you define which data can move into Outlook. We will cover more possible filters in the next part on Rules.

Kw-Outlook oneway arrow

Connection rules

On to the connection rules. These define which contacts are in the scope of the sync. In a secondary use case, rules are capable of translating Command states into Outlook states or vice versa. Rules come with filters and actions.

KW-Outlook all to all sync

With this setup, PieSync would create in Outlook any newly created Command contacts (1), as well as in fact create any existing Command contacts (2). Once they are created or identified, it would update and keep those contacts in continuous sync (3). It would do the same in the other way round, requiring PieSync to identify which contacts are potentially already present in both systems.

Only in a rare number of cases would you want to run these rules in unfiltered fashion. Here are different rule examples - inspired by you, our customers!

note: Regardless of what rules start out with, they can still see data sync two-way.

Tag syncing

Make syncing dependent from a tag in Command. We argue this is the best practice setup. It enables you to keep the sync rule setup simple and constant inside of PieSync. Merely applying (or removing) the tag in Command would allow contacts to start (or stop) syncing.

KWOutlook tag syncing

Stages syncing

Some two-way rules here that can be read in both directions, indicating that there is sales outreach happening in both platforms, so the Stage (Command) and Category (Outlook) need to move in tandem!

KWOutlook stage syncing

Connection Settings

Underneath the rules, we give you some easy toggles to play around with to tweak your connection even more.

Only sync contacts with an email address

'Avoid Duplicates' is enabled in the configuration set-up so that PieSync will only sync 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. Read more about this KWOutlook avoid dupl

Field mappings

Default field mappings

The field mapping defines how contacts will sync. A huge time & lifesaver in PieSync is that most of these are automatically set for all basic contact fields that Command & Outlook share by default.

Typically it's best to keep these default field mappings all activated as they represent the essential contact attributes that you would not want to grow out of sync in any circumstance.

KW Outlook default fields

Customizable field mappings

Field mapping also includes ability to custom map both text fields as well as date & checkboxes fields. This is fully customizable not only before setting up a new sync, but it can also be modified for an ongoing sync.

KWOutlook custom fields

PieSync syncs more than just Outlook

Being able to sync Command with Outlook aids in frictionless selling because it keeps the underlying contact data in sync, and saves time in manual import/export operations.

That ease of use & data consistency comes in handy as well when syncing contacts to a billing app, or a secondary CRM, a VOIP system, or even another dedicated marketing platform.

Here’s what this could look like syncing not only Command and Outlook, but Dotloop and Mailchimp as well.

KW outlook overview Dotloop - Mailchimp

PieSync is not only a turnkey solution to sync Command and Outlook exclusively. In fact, it solves a data problem that goes beyond these two apps. On average, users tend to connect 3-4 applications all through PieSync.

Do I need to sync iCloud, Google Contacts, Outlook, or all three at once?

They are all contacts management clouds. You've probably got data in all three clouds, but you don't need to keep all these accounts in sync.

As a KW agent, you may even want to consider to sync Gsuite/Google Contacts that are attached to your @kw.com address instead?

If you happen to have contacts sitting in disparate contact clouds, you can choose to sync those with Command too - but you don't need to keep these syncs running permanently.

Whatever you do: you choose one account and stick with it. Watch this PieSync Tutorial Series on 'Contacts Management' to become an expert.

Setting up your iPhone?

Go to your settings and make Outlook your “default account”, as seen in the screenshot below. This ensures that new contacts are added to Outlook and synced to your CRM. Outlook on phone as default

On this page