Skip to content
ERP ⇄ Marketing

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

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

Feed the real customer, order, and revenue records from Microsoft Dynamics NAV into Rollworks so campaigns run on who actually bought what, and let contact and consent changes flow back in real time.

Marketing runs on lists of people, but the list rarely knows which of those people are paying customers, what they ordered, or what they are worth. Microsoft Dynamics NAV holds exactly that: G/L Entries, Item Ledger Entries, Dimensions, Companies that record who the customer is, what they bought, and what they owe. When the two are joined only by a periodic export, campaigns go out against stale audiences, existing customers get prospecting emails, high-value accounts look the same as cold leads, and a canceled order still counts toward a segment.

Stacksync syncs G/L Entries, Item Ledger Entries, Dimensions, Companies in Microsoft Dynamics NAV with Campaigns, Ad Groups and Ads, Reporting and Attribution, Target Account Lists in Rollworks in real time, and where both sides accept writes, in both directions. Customer, order, and invoice data maps field by field onto the contacts, audiences, or accounts Rollworks works with, so segmentation and personalization run on current purchase history instead of a month-old snapshot. Contact details and consent changes that originate in Rollworks flow back onto the record in Microsoft Dynamics NAV.

The strongest bridge between the two is identity and purchase history, who the customer is and what they have bought, so that is where most of the value sits. Because the sync is field-level, each system keeps the attributes the other has no use for; only the shared records are held in agreement.

Common use cases

  • 01 Run parallel sync during a NAV-to-Business Central migration so both systems stay usable.
  • 02 Sync customers, items, and orders between NAV and a CRM in both directions.
  • 03 Activate high-intent accounts by writing them into a Target Account List tier when a product or intent signal fires in an operational database.
  • 04 Create and edit Prospecting v2 Campaigns and Ad Groups programmatically so budgets and targeting stay in step with an internal planning system.

Common sync patterns

Purchase history drives segmentation

Orders, invoices, and revenue totals from Microsoft Dynamics NAV land on the matching contact or account in Rollworks, so audiences are built from what customers actually bought and spent rather than from guesses.

Suppress or target existing customers

Because Microsoft Dynamics NAV knows who is already a paying customer, Rollworks can exclude them from acquisition campaigns or single them out for renewal and cross-sell.

One customer identity across both systems

A person or company's contact details corrected in either system update the other, so marketing and the back office stop maintaining separate versions of the same record.

What you can sync between Microsoft Dynamics NAV and Rollworks

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 Rollworks objects How this pairing syncs
Customers Customer cards synced with CRMs so sales sees ERP balances and terms. Reporting and Attribution Delivery and attribution metrics (impressions, clicks, cost, conversions, view-throughs) from the GraphQL Reporting API; read-only, aggregated by campaign, ad, and account domain. Customers is specific to Microsoft Dynamics NAV and Reporting and Attribution to Rollworks — each maps to any object or custom field on the other side.
Vendors Vendor cards aligned with procurement and AP tools. Target Account Lists Named lists of B2B accounts for ABM; managed through /audience/v1/target_accounts so a CRM or warehouse can push and reconcile the accounts RollWorks advertises against. Vendors is specific to Microsoft Dynamics NAV and Target Account Lists to Rollworks — each maps to any object or custom field on the other side.
Items Item cards and availability mirrored to ecommerce and planning systems. Account Tiers Groups within a Target Account List; an account belongs to only one tier per list, so tier assignments are written from source-of-truth data to drive tiered targeting. Items is specific to Microsoft Dynamics NAV and Account Tiers to Rollworks — 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. Accounts (TAL Items) Individual accounts identified by domain; added or removed via the tier items endpoint (POST/DELETE) so an operational database can control which domains are targeted. Sales Orders & Invoices is specific to Microsoft Dynamics NAV and Accounts (TAL Items) to Rollworks — each maps to any object or custom field on the other side.
Purchase Orders Purchasing documents reconciled with receiving and vendor systems. Audience Segments CRM (email), custom (cookie or ID), and lookalike segments created via /audience/v1/segments; membership is written from a warehouse with a duration of 1 to 540 days. Purchase Orders is specific to Microsoft Dynamics NAV and Audience Segments to Rollworks — each maps to any object or custom field on the other side.
G/L Entries Posted ledger entries replicated to warehouses for finance reporting. Campaigns Prospecting v2 campaigns running on Web and LinkedIn with budget, KPI, and flight settings; created and edited via API and read back for status and pacing. G/L Entries is specific to Microsoft Dynamics NAV and Campaigns to Rollworks — each maps to any object or custom field on the other side.

How changes propagate between Microsoft Dynamics NAV and Rollworks

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 Rollworks 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 Rollworks through its API, with automatic retries and rate-limit backoff.

Rollworks Microsoft Dynamics NAV Interval-based propagation

DetectionStacksync polls Rollworks for changes on an incremental schedule, reading only records changed since the previous pass. Polling — reporting is pulled via GraphQL queries and account/audience membership is reconciled on a schedule.

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

Rate-limit considerations

  • Rollworks: NextRoll does not publish explicit rate limits; access tokens expire 24 hours after issue and refresh tokens rotate on use, so long-running syncs must keep refreshing credentials.
What ships with Microsoft Dynamics NAV ⇄ Rollworks

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

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

Real-time

Two-way sync

Changes in Microsoft Dynamics NAV or Rollworks 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 Rollworks 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 Rollworks record.

Observability

Monitoring

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

How the Microsoft Dynamics NAV and Rollworks 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

Rollworks

Integration surface
REST APIs (Audience, Prospecting v2) plus a GraphQL Reporting API
Authentication
OAuth 2.0 via NextRoll (Authorization Code grant, Bearer tokens per RFC 6749/6750); Personal Access Tokens supported for server-side scripts
Change detection
Polling — reporting is pulled via GraphQL queries and account/audience membership is reconciled on a schedule; no change webhooks or CDC feed is published
Capabilities
read · write
Rate limits
NextRoll does not publish explicit rate limits; access tokens expire 24 hours after issue and refresh tokens rotate on use, so long-running syncs must keep refreshing credentials.
How it works

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

    Choose tables

    Pick the Microsoft Dynamics NAV and Rollworks 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 ⇄ Rollworks
    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 NAV Rollworks
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

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

Popular · 5 of 368
Coworkers laughing in front of a laptop in a casual office setting

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