Skip to content
CRM ⇄ Database

Microsoft Dynamics 365 Sales to SAP Hana integration — real-time, two-way sync

Keep Microsoft Dynamics 365 Sales and SAP Hana 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 Microsoft Dynamics 365 Sales and SAP Hana

Treat Microsoft Dynamics 365 Sales like part of your database: its records live in SAP Hana as real tables, and writes in either place sync to the other in seconds.

Product and engineering teams constantly need CRM data, and the CRM API is a poor way to get it: rate limits, pagination, custom objects, and integration code that breaks when an admin renames a field. What they actually want is the data in SAP Hana, where it can be queried and joined like everything else.

Stacksync mirrors Opportunities, Quotes, Orders, Invoices from Microsoft Dynamics 365 Sales into SQL views, Schemas, Sequences, Triggers in SAP Hana with real-time, bi-directional sync. Read CRM records with plain queries; write updates from your application and they appear in Microsoft Dynamics 365 Sales with validation intact. Go-to-market teams keep working in the CRM, engineers keep working in the database, and neither has to think about the other.

Common use cases

  • 01 Feed BI models with continuously updated CRM data instead of scheduled exports.
  • 02 Bi-directional sync of accounts, contacts, and opportunities with a SQL database so teams query CRM data without OData or FetchXML.
  • 03 Read SYS.TABLES and TABLE_COLUMNS system views to auto-discover schema and generate field mappings when new tables are added to the sync.
  • 04 Detect inserts, updates, and deletes on high-write tables via AFTER triggers or a last-modified column and replicate the deltas downstream near-real-time.

Common sync patterns

Query the CRM like a database

Accounts, contacts, and custom objects from Microsoft Dynamics 365 Sales become tables in SAP Hana you can join with application data directly.

Product events onto CRM records

Signup, usage, or lifecycle changes written to SAP Hana sync onto the matching records in Microsoft Dynamics 365 Sales, giving go-to-market teams live product context.

Internal tools without API code

Back-office apps read and write the synced tables; Stacksync handles the Microsoft Dynamics 365 Sales API, limits, and retries.

What you can sync between Microsoft Dynamics 365 Sales and SAP Hana

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.

Microsoft Dynamics 365 Sales objects SAP Hana objects How this pairing syncs
Opportunities Deal records with stages and estimated revenue; synced for pipeline reporting and close-triggered workflows. Triggers AFTER INSERT/UPDATE/DELETE triggers capture changes into a shadow/logging table so updates and deletes are detected near-real-time without full scans. Opportunities is specific to Microsoft Dynamics 365 Sales and Triggers to SAP Hana — each maps to any object or custom field on the other side.
Quotes Pricing proposals; often synced with CPQ or ERP pricing data. System-versioned temporal tables Column store tables with a history table tracking each row's validity period; used to reconstruct update and delete history for change capture. Quotes is specific to Microsoft Dynamics 365 Sales and System-versioned temporal tables to SAP Hana — each maps to any object or custom field on the other side.
Orders Confirmed sales; handed off to ERP systems for fulfillment and billing. System views (SYS schema) Catalog and monitoring views such as SYS.TABLES and TABLE_COLUMNS; read to discover schema and auto-generate field mappings for new tables. Orders is specific to Microsoft Dynamics 365 Sales and System views (SYS schema) to SAP Hana — each maps to any object or custom field on the other side.
Invoices Billing records; usually mastered in the ERP and mirrored back for seller visibility. Column store tables HANA's default table type, optimized for analytics; synced two-way as rows over the SQL interface with the primary key driving upserts and delete tracking. Invoices is specific to Microsoft Dynamics 365 Sales and Column store tables to SAP Hana — each maps to any object or custom field on the other side.
Activities Emails, calls, appointments, and tasks; read out for activity analytics. Row store tables OLTP-oriented tables held fully in memory; read and written the same way through the SAP HANA client for high-write operational tables. Activities is specific to Microsoft Dynamics 365 Sales and Row store tables to SAP Hana — each maps to any object or custom field on the other side.
Custom Tables Tenant-defined Dataverse tables; exposed through the same Web API as standard tables. Calculation views Modeled analytic views over base tables; read-only sources for pushing aggregated or joined results into a warehouse or downstream app. Custom Tables is specific to Microsoft Dynamics 365 Sales and Calculation views to SAP Hana — each maps to any object or custom field on the other side.

How changes propagate between Microsoft Dynamics 365 Sales and SAP Hana

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.

Microsoft Dynamics 365 Sales SAP Hana Sub-second propagation

DetectionMicrosoft Dynamics 365 Sales notifies Stacksync of record changes through webhook events. Dataverse change tracking with delta tokens, plus registered webhooks on table events.

DeliveryEach detected change is applied to SAP Hana as a row-level write, with types converted between the two schemas.

SAP Hana Microsoft Dynamics 365 Sales Sub-second propagation

DetectionChanges in SAP Hana are captured at the source via change data capture — no polling loop against its API. Polling on a last-modified timestamp column, or AFTER INSERT/UPDATE/DELETE triggers writing to a shadow table.

DeliveryEach detected change is written to Microsoft Dynamics 365 Sales through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Microsoft Dynamics 365 Sales: Requests are governed by Dataverse service protection limits evaluated per user and time window.
  • SAP Hana: No SaaS-style request quota; throughput is bounded by connection limits, statement memory caps, and workload-class admission control (concurrency/memory limits) that share capacity with production queries.
What ships with Microsoft Dynamics 365 Sales ⇄ SAP Hana

Connect Microsoft Dynamics 365 Sales and SAP Hana for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Microsoft Dynamics 365 Sales–SAP Hana connection.

Real-time

Two-way sync

Changes in Microsoft Dynamics 365 Sales or SAP Hana instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Microsoft Dynamics 365 Sales or SAP Hana 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 Microsoft Dynamics 365 Sales or SAP Hana record.

Observability

Monitoring

Track your Microsoft Dynamics 365 Sales ⇄ SAP Hana sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Microsoft Dynamics 365 Sales and SAP Hana.

How the Microsoft Dynamics 365 Sales and SAP Hana connectors work

Microsoft Dynamics 365 Sales

Integration surface
Dataverse Web API (OData v4 REST)
Authentication
OAuth 2.0 via Microsoft Entra ID
Change detection
Dataverse change tracking with delta tokens, plus registered webhooks on table events
Capabilities
read · write · webhooks
Rate limits
Requests are governed by Dataverse service protection limits evaluated per user and time window.

SAP Hana

Integration surface
SQL over the SAP HANA client (JDBC/ODBC drivers); OData/REST via XS for app-layer access
Authentication
Dedicated database user credentials over an encrypted TLS connection (password sent hashed); Kerberos, SAML, JWT, and X.509 certificate authentication are also supported. SAP HANA Cloud enforces TLS and IP allowlisting.
Change detection
Polling on a last-modified timestamp column, or AFTER INSERT/UPDATE/DELETE triggers writing to a shadow table; system-versioned temporal tables and SLT/SDI provide trigger- and log-based CDC. No native webhooks.
Capabilities
read · write · CDC
Rate limits
No SaaS-style request quota; throughput is bounded by connection limits, statement memory caps, and workload-class admission control (concurrency/memory limits) that share capacity with production queries.
How it works

How to connect Microsoft Dynamics 365 Sales to SAP Hana — 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 Microsoft Dynamics 365 Sales and SAP Hana 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
    Microsoft Dynamics 365 Sales connected
    SAP Hana connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Microsoft Dynamics 365 Sales and SAP Hana 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 · Microsoft Dynamics 365 Sales ⇄ SAP Hana
    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
    Microsoft Dynamics 365 Sales SAP Hana
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Microsoft Dynamics 365 Sales and SAP Hana 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
CSA STAR
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 465 integrations available for Microsoft Dynamics 365 Sales and SAP Hana.

Popular · 5 of 465
All Microsoft Dynamics 365 Sales integrations All SAP Hana 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