Integrating Microsoft Dynamics 365 with Pursuit

Last updated: June 9, 2026

Introduction

This guide provides step-by-step instructions to integrate Pursuit with Microsoft Dynamics 365. By following this guide, you'll connect Dynamics 365 to Pursuit, configure field mappings, and set up automatic syncing. The instructions are designed for both technical and non-technical users, with clear steps and explanations.

Prerequisites

Before starting, make sure you have the following:

Admin access to Microsoft Dynamics 365 (System Administrator or System Customizer security role)
An active Pursuit account with Admin role
Your Dynamics 365 organization URL
- e.g., https://yourorg.crm.dynamics.com

Connect Dynamics 365

The first step is to establish the connection between Pursuit and Dynamics 365. Pursuit will automatically create the required tracking fields during this process.

Find your organization URL
Your Dynamics 365 organization URL looks like https://yourorg.crm.dynamics.com. Log into Dynamics 365 and look at the URL in your browser's address bar. Copy the base URL — do not include anything after .com.
Initiate connection in Pursuit
Log in to the Pursuit app and navigate to the Integrations section.
Connect to Dynamics 365
Click the Connect button for Dynamics 365. A dialog will ask for your organization URL.
Enter your organization URL
Paste your Dynamics 365 URL (must start with https://). Click Connect.
Authorize Pursuit
You will be redirected to a Microsoft login screen. Sign in with your Dynamics 365 admin credentials and grant permission for Pursuit to access your data.
Automatic field setup
After authorization, Pursuit will automatically create the required Pursuit ID tracking fields on both your Account and Contact entities in Dynamics 365. You'll see a progress indicator showing each step.
Confirmation
Once complete, you will be returned to Pursuit. The connection is now established.

Note: Pursuit uses OAuth 2.0 for a secure connection and does not see or store your Microsoft username/password. All data transfer is encrypted in transit.

Permissions: The connecting user must have the System Administrator or System Customizer security role in Dynamics 365 to allow Pursuit to automatically create the tracking fields.

If automatic field setup fails

If the automatic field setup encounters a permissions error, Pursuit will still complete the connection but you must manually create the required fields.

Critical: You only need to follow these manual steps if the automatic setup failed. If you saw green checkmarks for all steps during connection, skip this section.

Ask your Dynamics 365 administrator to create the following fields:

Go to make.powerapps.com and select the correct environment.
In the left navigation, click Tables.
Select the Account table → click Columns → click + New column.
Create each field with these exact settings:

Table

Display Name

Schema / API Name

Data Type

Max Length

Account

Pursuit ID

new_pursuit_id

Single line of text

Contact

Pursuit ID

new_pursuit_id

Single line of text

⚠ Critical: The API name must be exactly new_pursuit_id on both entities. The new_ prefix is automatically added by Dynamics when creating fields in the default solution. Verify it matches exactly — if the names don't match, the sync will fail.

⚠ Critical: Once these fields are created in Dynamics 365, do not delete them. Deleting these fields will cause sync errors.

After creating both fields, click Publish All Customizations in the solution to make the fields available.

Create recommended fields

Pursuit can provide additional data about entities and contacts. You may want to create the following recommended fields to capture this information in Dynamics 365:

Table	Display Name	Suggested API Name	Data Type	Purpose
Account	Pursuit URL	`new_pursuit_url`	URL	Link to the entity's page on Pursuit
Account	Pursuit Parent ID	`new_pursuit_parent_id`	Single line of text	The Pursuit ID of the parent entity
Contact	Pursuit URL	`new_pursuit_url`	URL	Link to the contact's page on Pursuit
Contact	Confidence Score	`new_confidence_score`	Whole Number	Pursuit's match confidence score for this contact

Set Export Limits

Configure export limits for your CRM integration.

Unlimited: Allows non-admin users to export all available records.
Custom Limit: Enter a specific number to restrict how many records can be exported in a single action.

Tip: Use export limits to manage data flow and prevent accidental large exports by non-admin users.

Schedule Syncs

Pursuit can automatically and incrementally sync data with Dynamics 365 on a schedule you define.

Select Days — Choose which days of the week Pursuit should sync data with Dynamics 365.
Set the Time — Pick the time of day you want Pursuit to run the sync.
Confirm Your Timezone — Review the current timezone and update it if needed to match your team's local or CRM timezone.
Save Changes — Once saved, Pursuit will automatically sync your data according to your configured schedule.

Tip: You can adjust your sync schedule anytime to match your team's workflow or data update cadence.

Configure Field Mapping

Once connected, configure what data flows from Pursuit to Dynamics 365 and how it maps to your Dynamics fields.

Start configuration — In Pursuit's Integrations section, click the Dynamics 365 Mapping button.
Map Pursuit fields to Dynamics 365 fields
- Contact Fields: Email address is used as the unique identifier. Map Pursuit ID to the Pursuit ID Contact field, and Confidence Score to the Confidence Score Contact field.
- Entity Fields: Pursuit ID is used to identify the account. Map Pursuit ID to the Pursuit ID Account field, plus any other entity-level fields you want synced.
- Static Values (optional): Map a constant value to a field — for example, set "Data Source" to always be "Pursuit" for all records updated by this integration.
Set overwrite preferences — For each mapped field, decide if Pursuit should overwrite existing data. By default, Pursuit only fills in a field if it's empty. Enable Hard Overwrite if you want Pursuit's data to always replace whatever is in Dynamics 365 for that field. We recommend leaving Hard Overwrite off for most fields initially.
Review settings — Double-check that all mappings are correct and the desired fields are set to overwrite or not.
Save integration — Your Pursuit–Dynamics 365 integration is now configured.

Configure Filter Properties

Select the filters you want to import from your CRM to add to Pursuit's existing filters. This allows you to filter Pursuit's dataset by CRM properties directly within the app (e.g., filter entities by "Owner" or "Account Category").

In Pursuit's Integrations section, click the Dynamics 365 Mapping button and scroll down to Filter Properties. Recommended fields to import: Owner, Account Category, Industry, or any custom field relevant to your team.

Note: After enabling a new filter property, it may take 10+ minutes for Pursuit to sync all existing values. Once synced, you'll see these filter options in your Pursuit dashboard alongside Pursuit's own filters.

Data Enrichment

Account Enrichment

To avoid duplicate records and ensure Pursuit can match its data to your existing Dynamics 365 accounts, bulk-add Pursuit's unique IDs to all your current accounts using Pursuit's Data Enrichment tool.

Create an export: In Dynamics 365, navigate to Accounts and create a view (or use Advanced Find) that includes: Account ID, Account Name, Address 1: State/Province, Website, and optionally a unique identifier like FIPS Code or Census ID (strongly recommended — improves match accuracy).
Export to CSV: Click Export to Excel and save as CSV format.
Enrich Accounts: Follow the 📄 Account Enrichmentguide, including the step to import enriched accounts back into Dynamics 365.

Contact Enrichment

To avoid duplicate records and ensure Pursuit can match its data to your existing Dynamics 365 contacts, bulk-add Pursuit's unique IDs to all your current contacts.

Create an export: In Dynamics 365, navigate to Contacts and create a view that includes: Contact ID, First Name, Last Name, Company Name (Parent Account), Address 1: State/Province, and optionally Email, Job Title, or Company Website.
Export to CSV: Click Export to Excel and save as CSV format.
Enrich Contacts: Follow the guide, including the step to import enriched contacts back into Dynamics 365.

Frequently Asked Questions

Will Pursuit ever delete or overwrite data in my Dynamics 365?

Pursuit will never delete your Dynamics 365 records. Overwrites are only done for fields you've explicitly allowed via the Hard Overwrite setting. Otherwise, Pursuit adds data without disturbing your existing information.

What permissions does the connecting user need?

The connecting user needs the System Administrator or System Customizer security role for initial setup. For ongoing sync operations, the user needs at minimum Read and Write access to Account and Contact records.

Can I test the integration in a sandbox environment first?

Yes. Connect Pursuit to your sandbox by using the sandbox organization URL (e.g., https://yourorg-sandbox.crm.dynamics.com) during the connection step.

How does Pursuit connect to Dynamics 365? Is it secure?

Pursuit connects via OAuth 2.0 through Microsoft's identity platform (Microsoft Entra ID). You authenticate directly with Microsoft — Pursuit never sees your password. All data transfer is encrypted in transit. You can revoke Pursuit's access at any time from your Azure Active Directory app registrations or by disconnecting in Pursuit.

My organization URL uses a different region (e.g., .crm4.dynamics.com). Is that supported?

Yes. Pursuit supports all regional Dynamics 365 URLs — just enter your full organization URL as it appears in your browser.

The automatic field setup failed. What should I do?

Pursuit will still connect successfully — you just need to create the tracking fields manually. See the "Manually create required fields" section under Step 1. If you're unsure, ask your Dynamics 365 System Administrator to create the fields for you.