Skip to content
Security and identity ⇄ CRM

Active Directory to HubSpot integration — real-time, two-way sync

Keep Active Directory and HubSpot in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Active Directory and HubSpot

Keep the people HubSpot and Active Directory both track in agreement in real time: the internal users who own records in HubSpot, and the customer login accounts in Active Directory.

A CRM and an identity system usually describe different populations. HubSpot tracks customers, contacts, and the deals in motion; Active Directory governs who is allowed to sign in and what they can reach. Where the two meet is people. The reps who own records in HubSpot are the same employees Active Directory provisions and disables, and when Active Directory also runs the login accounts for your product, the customers in HubSpot are the same users Active Directory authenticates. Left unconnected, a departure in Active Directory leaves stale ownership sitting in HubSpot, and a signup in Active Directory never reaches the account it belongs to.

Stacksync syncs Pipeline, Stages, Audit, Contact in HubSpot with Organizational units, Organizational contacts, Users, Groups in Active Directory in real time and in both directions, matching on email or an external ID and mapping field by field. You decide which system owns which fields, and new users, role and group changes, deactivations, and account status move within seconds instead of waiting on a quarterly access review or a manual export.

Common use cases

  • 01 Write warehouse-computed lead and account scores back to HubSpot properties on a schedule or in near real time.
  • 02 Sync HubSpot Tickets with an internal support database to unify service reporting across channels.
  • 03 Read Users, Groups, and directoryRole assignments into a warehouse for periodic access reviews and SOC 2 audit evidence.
  • 04 Keep security-group memberships aligned with application entitlement tables so access reflects the right teams as they change.

Common sync patterns

Where a closed deal should provision access: HubSpot drives Active Directory

A won or activated customer in HubSpot can create or update the corresponding user or account in Active Directory, so provisioning starts from the CRM record instead of a separate ticket.

Where Active Directory governs your workforce: CRM users kept current

New employees in Active Directory become active users in HubSpot with the right role, and group or department changes update their access and team, so the CRM's user list matches the directory without an admin re-keying it.

Deactivation and record hand-off

When someone is disabled in Active Directory, the matching user in HubSpot is deactivated too, and the accounts, contacts, and deals they owned are flagged for reassignment, so nothing goes unattended after they leave.

What you can sync between Active Directory and HubSpot

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Active Directory objects HubSpot objects How this pairing syncs
Service principals & applications App registrations and enterprise apps; read-mostly for entitlement and license inventory. Stages Synced with incremental and full sync per the Stacksync docs. Service principals & applications is specific to Active Directory and Stages to HubSpot — each maps to any object or custom field on the other side.
Organizational units On-prem AD DS containers (LDAP organizationalUnit) used to scope which users and groups a sync includes. Audit Synced with incremental and full sync per the Stacksync docs. Organizational units is specific to Active Directory and Audit to HubSpot — each maps to any object or custom field on the other side.
Organizational contacts Directory contact objects (orgContact); synced for shared address-book and CRM person records. Contact Synced with incremental and full sync per the Stacksync docs. Organizational contacts is specific to Active Directory and Contact to HubSpot — each maps to any object or custom field on the other side.
Users User accounts in Entra ID and on-prem AD DS; synced two-way to create, update attributes, and enable or disable accounts. Company Synced with incremental and full sync per the Stacksync docs. Users is specific to Active Directory and Company to HubSpot — each maps to any object or custom field on the other side.
Groups Security and Microsoft 365 groups; synced two-way including name, type, and owner, with membership tracked separately. Deal Synced with incremental and full sync per the Stacksync docs. Groups is specific to Active Directory and Deal to HubSpot — each maps to any object or custom field on the other side.
Group memberships Member and owner links between users and groups; membership add/remove changes are surfaced by delta query. Line Item Synced with incremental and full sync per the Stacksync docs. Group memberships is specific to Active Directory and Line Item to HubSpot — each maps to any object or custom field on the other side.

How changes propagate between Active Directory and HubSpot

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Active Directory HubSpot Sub-second propagation

DetectionActive Directory notifies Stacksync of record changes through webhook events. Microsoft Graph delta query (change tracking) for Users and Groups, plus change-notification subscriptions (webhooks) for near-real-time triggers.

DeliveryEach detected change is written to HubSpot through its API, with automatic retries and rate-limit backoff.

HubSpot Active Directory Sub-second propagation

DetectionHubSpot pushes changes as they happen — webhook events backed by change data capture. Records: incremental near-real-time change tracking.

DeliveryEach detected change is written to Active Directory through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Active Directory: Graph throttles by resource-unit cost per app per tenant in 10-second windows (about 3,500–8,000 units by tenant size); directory delta tokens expire after ~7 days.
  • HubSpot: Request limits vary by subscription tier and API type.
What ships with Active Directory ⇄ HubSpot

Connect Active Directory and HubSpot for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Active Directory–HubSpot connection.

Real-time

Two-way sync

Changes in Active Directory or HubSpot instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Active Directory or HubSpot data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Active Directory or HubSpot record.

Observability

Monitoring

Track your Active Directory ⇄ HubSpot sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Active Directory and HubSpot.

How the Active Directory and HubSpot connectors work

Active Directory

Integration surface
Microsoft Graph REST API (Entra ID / cloud) and LDAP/LDAPS (on-premises AD DS)
Authentication
OAuth 2.0 via the Microsoft identity platform — an app registration with application or delegated permissions (e.g. User.ReadWrite.All, Group.ReadWrite.All) and admin consent; on-prem AD DS uses a bound service account over LDAPS.
Change detection
Microsoft Graph delta query (change tracking) for Users and Groups, plus change-notification subscriptions (webhooks) for near-real-time triggers; on-prem AD DS uses the DirSync control and uSNChanged polling.
Capabilities
read · write · webhooks
Rate limits
Graph throttles by resource-unit cost per app per tenant in 10-second windows (about 3,500–8,000 units by tenant size); directory delta tokens expire after ~7 days.

HubSpot

Integration surface
REST API (CRM v3)
Authentication
OAuth (choose HubSpot account and authorize Stacksync); requires a HubSpot 'Super Admin' to grant access; optional "Grant access to sensitive fields" checkbox for sensitive/highly sensitive fields
Change detection
Records: incremental near-real-time change tracking. Associations: HubSpot has no native association CDC
Capabilities
read · write · CDC · webhooks
Rate limits
Request limits vary by subscription tier and API type.
HubSpot setup guide
How it works

How to connect Active Directory to HubSpot — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Active Directory and HubSpot with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Active Directory connected
    HubSpot connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Active Directory and HubSpot objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Active Directory ⇄ HubSpot
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Active Directory HubSpot
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Active Directory and HubSpot integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 534 integrations available for Active Directory and HubSpot.

Popular · 8 of 534
All Active Directory integrations All HubSpot integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own