Levitate + Microsoft Dynamics 365 Sales Integration

Overview

The Microsoft Dynamics 365 Sales integration allows Levitate to sync your contact data and activity history so you can automate outreach and maintain strong client relationships.

Industry: Any
Integration Type: API
Sync Frequency: Twice daily
Writeback: Supported (notes, emails, calls, texts, etc.)

How Data Syncs

Levitate connects securely to your Dynamics account via API
Contacts and associated data sync into Levitate automatically
Updates occur twice daily
One designated sync user is used to pull data

What Will Sync into Levitate

Contact Information

First and last name
Nickname
Job title
Email addresses (up to 3)
Phone numbers (multiple types)
Addresses (multiple supported)

Contacts must have sufficient data (name or email) to be imported.

Ownership & User Mapping

Ownership is based on the "Owner" field in Dynamics
Contacts are assigned to Levitate users via mapping
Only mapped users' contacts will sync into Levitate

Note: On most accounts the Owner is an individual, mapped 1:1 to a Levitate user. If your contacts are owned by a team rather than a person, map the team to bring its contacts into Levitate.

Key Facts

Levitate automatically creates key reminders such as:

Birthdays
Custom date fields (for review reminders, lifecycle tracking, etc.)

Custom date fields can power dashboard cards and automations.

Writeback Capabilities

Levitate can send activity data back into Dynamics:

Notes, texts, handwritten cards → saved as annotations
Emails → saved as email activities
Phone calls → saved as phone call activities

This ensures your CRM remains your system of record.

Integration Settings

Core Settings

Mapping By: Owner (only option)
Primary Email Only: Choose whether to import one or multiple emails
Segment by Tags: Filter which contacts are synced
Writebacks: Enable/disable specific activity types

Key Fact Settings

Pull in custom date fields from Dynamics
These become reminders or key dates in Levitate

Tag Settings

Choose standard tags (location-based)
Enable custom fields as tags
Multi-select fields create multiple tags
Long tags are automatically shortened

Sync Behavior & Expectations

Initial sync begins after setup is completed
Ongoing sync runs twice daily
Custom fields populate after the first full sync
Sync performance depends on data volume

Requirements for Setup

To connect Dynamics to Levitate, you'll need:

Appropriate access to Dynamics
A configured Dynamics app (handled by your technical team)
CRM domain (your Dynamics URL)
Custom field prefixes (if using custom fields)
At least one connected user to act as the sync user

FAQs

Q: Does Levitate write back to Dynamics?

A: Levitate does not push contact data changes back to Dynamics. However, if writebacks are enabled, engagement activities (emails, notes, calls, texts, and handwritten cards) are logged back into Dynamics. Dynamics remains your source of truth for contact information.

Q: Can multiple users connect?

A: Yes, but only one user is used for syncing data.

Q: Why aren't contacts showing up?

A: Contacts must:

Have sufficient data
Be assigned to a mapped user

Q: Can we use custom fields?

A: Yes—custom fields can be used for both tags and key facts.

Q: Will a contact's nickname replace their first name in email greetings?

A: Yes. By default, if a Dynamics contact has a nickname, Levitate uses it in place of the first name for email personalization (for example, the {{first name}} greeting). If you'd prefer the legal first name always be used, reach out to your Success Manager or Levitate Support at support@levitate.ai — this is adjusted on our end, and the change takes effect on the next sync.

Q: If I enable a custom date field (such as "Next review date") in the Dynamics integration, will it automatically trigger an existing automation?

A: Enabling a custom date field in the Dynamics Key Facts settings syncs that date into Levitate as a key fact reminder. Whether it triggers an existing automation — such as a Client Review automation — depends on how the automation was configured and whether the field is mapped to the same date type the automation is looking for. Existing automations do not automatically switch to use a newly enabled custom date field. Contact your Success Specialist to confirm whether your custom date field can be configured to trigger your automation, and to discuss any steps needed to connect the two.