Can you integrate Microsoft Dynamics NAV with Splunk?

Yes. Stacksync provides a managed, real-time two-way integration between Microsoft Dynamics NAV and Splunk: authenticate both systems, choose the objects to sync (such as Microsoft Dynamics NAV's Vendors and Items), map fields visually, and changes propagate both ways in milliseconds — no code required.

How does the Microsoft Dynamics NAV to Splunk sync work?

Change detection on Microsoft Dynamics NAV: Polling on modified/timestamp fields, or SQL Server change tracking/CDC on on-premises databases; no native webhooks. On Splunk: Time-range searches over indexed events (earliest/latest on _time or _indextime); events are immutable once indexed, so incremental extraction advances a time cursor rather than a modified-date CDC feed. Config objects such as saved searches and KV Store are polled; alerts can push via a saved-search webhook action. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.

Which Microsoft Dynamics NAV objects can I sync with Splunk?

On the Splunk side: Indexes, HTTP Event Collector, Users and Roles, Dashboards, plus custom fields where Splunk exposes them. On the Microsoft Dynamics NAV side: Dimensions, Companies, Customers, Vendors. Stacksync auto-detects both schemas and converts types between the two systems.

Can the Microsoft Dynamics NAV–Splunk sync run one-way instead of two-way?

Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.

How do teams use the Microsoft Dynamics NAV and Splunk integration?

Common patterns for Microsoft Dynamics NAV and Splunk: Where Microsoft Dynamics NAV runs operations: inventory and fulfillment metrics; Where Microsoft Dynamics NAV is the HR system of record: workforce and cost analysis; Write-back where Microsoft Dynamics NAV exposes writable fields: segments and scores return. Operational records from Microsoft Dynamics NAV become measurable in Splunk, joinable with the rest of what the company tracks for supply and fulfillment reporting.

What should I know about the two APIs?

Microsoft Dynamics NAV: SOAP and OData web services published from NAV pages and codeunits; direct SQL Server access on-premises. Authentication: Windows authentication or NavUserPassword credentials. Splunk: REST API (management API + HTTP Event Collector). Authentication: HTTP Basic (username/password), or a session key from POST /services/auth/login sent as Authorization: Splunk , or a bearer authentication token (Authorization: Bearer ). The HTTP Event Collector uses its own per-input token (Authorization: Splunk ). Management API defaults to port 8089; HEC to port 8088 (443 on Splunk Cloud). Stacksync manages authentication, retries, and rate limits on both sides.

ERP ⇄ Analytics

Microsoft Dynamics NAV to Splunk integration — real-time, two-way sync

Keep Microsoft Dynamics NAV and Splunk 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

Live sync

stacksync.com

Microsoft Dynamics NAV

Splunk

<1s: latency
2-way: sync
100M+: records

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 NAV and Splunk

Put Microsoft Dynamics NAV's records into Splunk as live data for reporting and dashboards, without nightly exports, and send the segments and metrics Splunk computes back where Microsoft Dynamics NAV can use them.

ERP data is some of the most requested data for analysis and some of the hardest to pull: the record types are many, the APIs are strict, and export jobs break on every upgrade. Whether Microsoft Dynamics NAV carries financials, operations, workforce data, or all three, those numbers belong in Splunk, next to the product, behavioral, and web data the team already measures.

Stacksync syncs Dimensions, Companies, Customers, Vendors from Microsoft Dynamics NAV into Splunk continuously, handling API limits and schema drift as it goes, so each record type arrives as Indexes, HTTP Event Collector, Users and Roles, Dashboards ready to report on. The connection is bi-directional, so segments, scores, and metrics computed in Splunk can be written back to fields in Microsoft Dynamics NAV where that is useful.

Common use cases

01 Read and write KV Store collections to keep Splunk lookups — asset inventories, allow/deny lists, enrichment tables — in sync with an external source of truth in both directions.
02 Provision and update Saved Searches, alerts, and Dashboards from a Git-backed config repository so detections and reports stay versioned and consistent across search heads.
03 Push ecommerce orders into NAV sales orders through published page services.
04 Replicate G/L and ledger entries into a warehouse for consolidated finance reporting.

Common sync patterns

Where Microsoft Dynamics NAV runs operations: inventory and fulfillment metrics

Operational records from Microsoft Dynamics NAV become measurable in Splunk, joinable with the rest of what the company tracks for supply and fulfillment reporting.

Where Microsoft Dynamics NAV is the HR system of record: workforce and cost analysis

Worker and organization data from Microsoft Dynamics NAV syncs into Splunk for headcount, cost, and utilization reporting alongside other company data.

Write-back where Microsoft Dynamics NAV exposes writable fields: segments and scores return

Segments, scores, or metrics computed in Splunk sync onto the matching records in Microsoft Dynamics NAV, so operations act on what the analysis found.

What you can sync between Microsoft Dynamics NAV and Splunk

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 NAV objects		Splunk objects	How this pairing syncs
Vendors Vendor cards aligned with procurement and AP tools.	⇄	Fired Alerts Triggered alert instances listed at /services/alerts/fired_alerts; alert configuration (conditions, schedule, actions) lives on the corresponding saved search. Landed in a database for alert-trend and detection-coverage reporting.	Vendors is specific to Microsoft Dynamics NAV and Fired Alerts to Splunk — each maps to any object or custom field on the other side.
Items Item cards and availability mirrored to ecommerce and planning systems.	⇄	KV Store Collections App-scoped, MongoDB-backed key-value collections at /servicesNS/{owner}/{app}/storage/collections/data/{collection} with full CRUD and batch endpoints. Genuinely bidirectional lookup/state store — read records out or write records in.	Items is specific to Microsoft Dynamics NAV and KV Store Collections to Splunk — each maps to any object or custom field on the other side.
Sales Orders & Invoices Sales documents created from external orders and read back for posting status.	⇄	Indexes Index inventory and settings (retention, max size, event counts) via /services/data/indexes, with create and edit; loaded into a database for capacity, retention, and data-onboarding tracking.	Sales Orders & Invoices is specific to Microsoft Dynamics NAV and Indexes to Splunk — each maps to any object or custom field on the other side.
Purchase Orders Purchasing documents reconciled with receiving and vendor systems.	⇄	HTTP Event Collector The write-in path: POST events and metrics to /services/collector (port 8088, or 443 on Splunk Cloud) authenticated with a per-input HEC token, so external records are indexed alongside logs for search and correlation.	Purchase Orders is specific to Microsoft Dynamics NAV and HTTP Event Collector to Splunk — each maps to any object or custom field on the other side.
G/L Entries Posted ledger entries replicated to warehouses for finance reporting.	⇄	Users and Roles Accounts at /services/authentication/users and role/capability definitions at /services/authorization/roles, with full CRUD; exported for access reviews or provisioned from an identity source of truth.	G/L Entries is specific to Microsoft Dynamics NAV and Users and Roles to Splunk — each maps to any object or custom field on the other side.
Item Ledger Entries Inventory movement history read for stock and costing analytics.	⇄	Dashboards Simple XML dashboard and view definitions at /servicesNS/{owner}/{app}/data/ui/views; exported for backup and audit, or created and updated programmatically from version control.	Item Ledger Entries is specific to Microsoft Dynamics NAV and Dashboards to Splunk — each maps to any object or custom field on the other side.

How changes propagate between Microsoft Dynamics NAV and Splunk

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 NAV Splunk Sub-second propagation

DetectionChanges in Microsoft Dynamics NAV are captured at the source via change data capture — no polling loop against its API. Polling on modified/timestamp fields, or SQL Server change tracking/CDC on on-premises databases.

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

Splunk Microsoft Dynamics NAV Sub-second propagation

DetectionSplunk notifies Stacksync of record changes through webhook events. Time-range searches over indexed events (earliest/latest on _time or _indextime).

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

Rate-limit considerations

Splunk: The management REST API throttles through search-concurrency quotas — max concurrent searches per user and role, plus per-CPU historical search limits in limits.conf — rather than a fixed per-request rate; exceeding quota queues or blocks jobs. HEC has per-token and per-instance throughput limits, and Splunk Cloud adds ingestion and API limits on top.

What ships with Microsoft Dynamics NAV ⇄ Splunk

Connect Microsoft Dynamics NAV and Splunk for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Microsoft Dynamics NAV–Splunk connection.

Real-time

Two-way sync

Changes in Microsoft Dynamics NAV or Splunk instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Microsoft Dynamics NAV or Splunk 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 NAV or Splunk record.

Observability

Monitoring

Track your Microsoft Dynamics NAV ⇄ Splunk 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 NAV and Splunk.

How the Microsoft Dynamics NAV and Splunk connectors work

Microsoft Dynamics NAV

Integration surface: SOAP and OData web services published from NAV pages and codeunits; direct SQL Server access on-premises
Authentication: Windows authentication or NavUserPassword credentials
Change detection: Polling on modified/timestamp fields, or SQL Server change tracking/CDC on on-premises databases; no native webhooks
Capabilities: read · write · CDC

Splunk

Integration surface: REST API (management API + HTTP Event Collector)
Authentication: HTTP Basic (username/password), or a session key from POST /services/auth/login sent as Authorization: Splunk <key>, or a bearer authentication token (Authorization: Bearer <token>). The HTTP Event Collector uses its own per-input token (Authorization: Splunk <hec-token>). Management API defaults to port 8089; HEC to port 8088 (443 on Splunk Cloud).
Change detection: Time-range searches over indexed events (earliest/latest on _time or _indextime); events are immutable once indexed, so incremental extraction advances a time cursor rather than a modified-date CDC feed. Config objects such as saved searches and KV Store are polled; alerts can push via a saved-search webhook action.
Capabilities: read · write · webhooks
Rate limits: The management REST API throttles through search-concurrency quotas — max concurrent searches per user and role, plus per-CPU historical search limits in limits.conf — rather than a fixed per-request rate; exceeding quota queues or blocks jobs. HEC has per-token and per-instance throughput limits, and Splunk Cloud adds ingestion and API limits on top.

How it works

How to connect Microsoft Dynamics NAV to Splunk — 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.

01
Connect your apps

Authenticate Microsoft Dynamics NAV and Splunk 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 NAV connected
Splunk connected

OAuth 2.0
SSH tunnel
SSL certificate
VPC peering
02
Choose tables

Pick the Microsoft Dynamics NAV and Splunk 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 NAV ⇄ Splunk

Customers 12,480
Sales Orders 8,213
Invoices 5,902
Items 1,344
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 NAV Splunk

Company company_name text
Email email text
Amount amount numeric
Created created_at timestamp

Try interactive demo

FAQ

Microsoft Dynamics NAV and Splunk 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 476 integrations available for Microsoft Dynamics NAV and Splunk.

Popular · 6 of 476

All Microsoft Dynamics NAV integrations All Splunk 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

Microsoft Dynamics NAV to Splunk integration — real-time, two-way sync

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