Real-time
Two-way sync
Changes in Atlassian or Microsoft Dynamics NAV instantly reflect in both systems. No stale data, no manual imports.
Business productivity ⇄ ERP
Atlassian to Microsoft Dynamics NAV integration — real-time, two-way sync
Keep Atlassian and Microsoft Dynamics NAV 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 Atlassian and Microsoft Dynamics NAV
Bridge the tools people work in and the system the business runs on: real-time, two-way sync between Atlassian and Microsoft Dynamics NAV.
The ERP holds the records the business is run on, and it is rarely where day-to-day work happens. Atlassian is closer to the work, and the two often need the same facts about the same people, organizations, and transactions. Bridging them by hand, or by nightly file transfer, leaves each side out of date for hours at a time.
Stacksync syncs Issue Comments, Attachments, Custom Fields, Workflows and Statuses in Atlassian with Companies, Customers, Vendors, Items in Microsoft Dynamics NAV bi-directionally and in real time, with field-level mapping and rules for which system wins on conflict. Changes made where the work happens reach the system of record within seconds, and the reverse.
Common use cases
- 01 Sync Confluence page metadata into a knowledge index so other tools can link to current documentation.
- 02 Mirror Jira projects into a SQL database for engineering throughput and SLA reporting.
- 03 Sync customers, items, and orders between NAV and a CRM in both directions.
- 04 Push ecommerce orders into NAV sales orders through published page services.
Common sync patterns
Master data corrections travel
A customer, supplier, or contact detail corrected in either system updates the other, ending duplicate maintenance.
Where Atlassian faces customers and Microsoft Dynamics NAV carries account records
Order, invoice, or account status from Microsoft Dynamics NAV appears alongside the customer in Atlassian, so front-line teams answer from live data.
Where Microsoft Dynamics NAV is the HR or people system of record
Worker and organization data from Microsoft Dynamics NAV stays current in Atlassian, so the tools people use daily reflect the org as it actually is.
What you can sync between Atlassian and Microsoft Dynamics NAV
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.
| Atlassian objects | Microsoft Dynamics NAV objects | How this pairing syncs | |
|---|---|---|---|
| Workflows and Statuses Status transitions mapped to stages in the paired system. | Purchase Orders Purchasing documents reconciled with receiving and vendor systems. | Workflows and Statuses is specific to Atlassian and Purchase Orders to Microsoft Dynamics NAV — each maps to any object or custom field on the other side. | |
| Users and Groups Assignees and reporters matched to identities in other tools. | G/L Entries Posted ledger entries replicated to warehouses for finance reporting. | Users and Groups is specific to Atlassian and G/L Entries to Microsoft Dynamics NAV — each maps to any object or custom field on the other side. | |
| Confluence Pages Documentation content readable and writable through the Confluence REST API. | Item Ledger Entries Inventory movement history read for stock and costing analytics. | Confluence Pages is specific to Atlassian and Item Ledger Entries to Microsoft Dynamics NAV — each maps to any object or custom field on the other side. | |
| Confluence Spaces Namespaces that scope page syncs and permissions. | Dimensions Analytical codes carried on documents and entries for reporting splits. | Confluence Spaces is specific to Atlassian and Dimensions to Microsoft Dynamics NAV — each maps to any object or custom field on the other side. | |
| Jira Issues The central work item, synced two-way with CRMs, support desks, and other trackers. | Companies Per-company data partitions that scope every sync. | Jira Issues is specific to Atlassian and Companies to Microsoft Dynamics NAV — each maps to any object or custom field on the other side. | |
| Jira Projects Containers that scope issues, workflows, and permissions for a sync. | Customers Customer cards synced with CRMs so sales sees ERP balances and terms. | Jira Projects is specific to Atlassian and Customers to Microsoft Dynamics NAV — each maps to any object or custom field on the other side. |
How changes propagate between Atlassian and Microsoft Dynamics NAV
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.
Atlassian Microsoft Dynamics NAV Sub-second propagation
DetectionAtlassian notifies Stacksync of record changes through webhook events. Webhooks on issue and page events, plus JQL polling on the updated timestamp for backfill.
DeliveryEach detected change is applied to Microsoft Dynamics NAV as a row-level write, with types converted between the two schemas.
Microsoft Dynamics NAV Atlassian 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 Atlassian through its API, with automatic retries and rate-limit backoff.
What ships with Atlassian ⇄ Microsoft Dynamics NAV
Connect Atlassian and Microsoft Dynamics NAV for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Atlassian–Microsoft Dynamics NAV connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Atlassian or Microsoft Dynamics NAV 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 Atlassian or Microsoft Dynamics NAV record.
Observability
Monitoring
Track your Atlassian ⇄ Microsoft Dynamics NAV sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Atlassian and Microsoft Dynamics NAV.
How the Atlassian and Microsoft Dynamics NAV connectors work
Atlassian
- Integration surface
- REST APIs per product (Jira Cloud and Confluence Cloud)
- Authentication
- OAuth 2.0 (3LO) for apps or API tokens with basic auth for scripts
- Change detection
- Webhooks on issue and page events, plus JQL polling on the updated timestamp for backfill
- Capabilities
- read · write · webhooks
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
How it works
How to connect Atlassian to Microsoft Dynamics NAV — 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 Atlassian and Microsoft Dynamics NAV with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Atlassian
connected
Microsoft Dynamics NAV
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Atlassian and Microsoft Dynamics NAV 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.
objects · Atlassian ⇄ Microsoft Dynamics NAVCustomers 12,480Sales Orders 8,213Invoices 5,902Items 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.
Atlassian Microsoft Dynamics NAVCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Atlassian and Microsoft Dynamics NAV 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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 444 integrations available for Atlassian and Microsoft Dynamics NAV.
Popular · 1 of 444
No integrations match .
