Skip to content
Storage ⇄ ERP

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

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

Move the documents and data that Microsoft Dynamics NAV produces into Amazon S3 as files, and let files stored in Amazon S3 update the records they belong to in Microsoft Dynamics NAV, continuously and without exports or manual filing.

Microsoft Dynamics NAV runs the business on structured records: Vendors, Items, Sales Orders & Invoices, Purchase Orders. Amazon S3 holds files and the metadata that describes them: Multipart uploads, Buckets, Objects, Object metadata. The two do not share a customer table or an order ledger. What they share is documents. Nearly every record Microsoft Dynamics NAV touches produces a file that belongs in storage, whether an invoice, a purchase order, a statement, or a shipping doc, and many files that land in Amazon S3, from signed contracts to vendor bills to receipts, describe a transaction Microsoft Dynamics NAV needs to record. Left unconnected, that link is maintained by hand: someone exports a PDF and drags it into a folder, or downloads a file and keys its details into a record.

Stacksync keeps Vendors, Items, Sales Orders & Invoices, Purchase Orders in Microsoft Dynamics NAV and Multipart uploads, Buckets, Objects, Object metadata in Amazon S3 in sync, bi-directionally and in real time. A document and its details, the customer, the type, the date, an amount, an order or invoice number, are mapped field by field, so a file arrives in Amazon S3 already labeled and filed, and metadata captured against a stored file can create or update the matching record in Microsoft Dynamics NAV. Changes on either side show up within seconds, with conflict resolution in place of nightly exports and manual filing.

The result is that a transaction and the document that backs it stay together. Finance, operations, and audit teams find the file behind a record without digging through folders, and the record in Microsoft Dynamics NAV and the file in Amazon S3 never describe two different versions of the same document.

Common use cases

  • 01 Push ecommerce orders into NAV sales orders through published page services.
  • 02 Replicate G/L and ledger entries into a warehouse for consolidated finance reporting.
  • 03 Trigger a database or ERP record update the moment an S3 Event Notification fires an object-created event, for example when a partner drops an EDI or invoice file into an inbound prefix.
  • 04 Reconcile Object versions and delete markers into an audit table so teams track when files under a compliance prefix were added, replaced, or removed.

Common sync patterns

Audit-ready retention

Every transaction's supporting file lives in Amazon S3 beside its metadata, giving finance and audit teams a complete, searchable trail tied back to the record in Microsoft Dynamics NAV.

Documents filed with their context

Files that Microsoft Dynamics NAV produces land in Amazon S3 labeled with the customer, document type, and reference number they belong to, so the right copy is one search away instead of buried in a folder.

Metadata that files itself

Record fields from Microsoft Dynamics NAV, like customer, date, amount, type, and reference number, become the metadata and tags on the stored file in Amazon S3, so storage stays organized without anyone tagging by hand.

What you can sync between Amazon S3 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.

Amazon S3 objects Microsoft Dynamics NAV objects How this pairing syncs
Multipart uploads In-progress large-object uploads assembled from parts; objects above ~100 MB (required above 5 GB) are written this way, and incomplete uploads persist until completed or aborted. Companies Per-company data partitions that scope every sync. Multipart uploads is specific to Amazon S3 and Companies to Microsoft Dynamics NAV — each maps to any object or custom field on the other side.
Buckets Top-level, region-scoped containers that hold objects; enumerated to discover the namespaces and prefixes a sync should cover. Customers Customer cards synced with CRMs so sales sees ERP balances and terms. Buckets is specific to Amazon S3 and Customers to Microsoft Dynamics NAV — each maps to any object or custom field on the other side.
Objects Files stored under a key; content is read with GET and written with PUT, and each object's key/size/ETag/LastModified is the unit indexed into a database. Vendors Vendor cards aligned with procurement and AP tools. Objects is specific to Amazon S3 and Vendors to Microsoft Dynamics NAV — each maps to any object or custom field on the other side.
Object metadata System metadata (Content-Type, size, ETag, LastModified) plus user-defined x-amz-meta-* headers; user metadata is fixed at write time and only changeable by rewriting the object. Items Item cards and availability mirrored to ecommerce and planning systems. Object metadata is specific to Amazon S3 and Items to Microsoft Dynamics NAV — each maps to any object or custom field on the other side.
Object tags Up to 10 key-value tags per object, mutable in place via the tagging API independent of content, so classification and retention labels sync two-way without rewriting files. Sales Orders & Invoices Sales documents created from external orders and read back for posting status. Object tags is specific to Amazon S3 and Sales Orders & Invoices to Microsoft Dynamics NAV — each maps to any object or custom field on the other side.
Object versions When bucket versioning is enabled every write creates a new version ID; prior versions and delete markers are readable for history and audit syncs. Purchase Orders Purchasing documents reconciled with receiving and vendor systems. Object versions is specific to Amazon S3 and Purchase Orders to Microsoft Dynamics NAV — each maps to any object or custom field on the other side.

How changes propagate between Amazon S3 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.

Amazon S3 Microsoft Dynamics NAV Sub-second propagation

DetectionAmazon S3 notifies Stacksync of record changes through webhook events. S3 Event Notifications push object-created, object-removed, and object-tagging events to SNS, SQS, Lambda, or EventBridge.

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

Microsoft Dynamics NAV Amazon S3 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 Amazon S3 through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Amazon S3: S3 sustains at least 3,500 PUT/COPY/POST/DELETE and 5,500 GET/HEAD requests per second per partitioned prefix and scales higher automatically; bursts can return HTTP 503 SlowDown while it repartitions.
What ships with Amazon S3 ⇄ Microsoft Dynamics NAV

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

How the Amazon S3 and Microsoft Dynamics NAV connectors work

Amazon S3

Integration surface
S3 REST API (also via AWS SDKs and the S3-compatible endpoint)
Authentication
AWS IAM credentials — an access key ID and secret access key signed with AWS Signature Version 4; supports temporary STS credentials and cross-account IAM roles
Change detection
S3 Event Notifications push object-created, object-removed, and object-tagging events to SNS, SQS, Lambda, or EventBridge; there is no modified-since query, so polling relies on each object's LastModified from ListObjectsV2
Capabilities
read · write · webhooks
Rate limits
S3 sustains at least 3,500 PUT/COPY/POST/DELETE and 5,500 GET/HEAD requests per second per partitioned prefix and scales higher automatically; bursts can return HTTP 503 SlowDown while it repartitions.

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 Amazon S3 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.

  1. 01

    Connect your apps

    Authenticate Amazon S3 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Amazon S3 connected
    Microsoft Dynamics NAV connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Amazon S3 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Amazon S3 ⇄ Microsoft Dynamics NAV
    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
    Amazon S3 Microsoft Dynamics NAV
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Amazon S3 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.

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 495 integrations available for Amazon S3 and Microsoft Dynamics NAV.

Popular · 7 of 495
All Amazon S3 integrations All Microsoft Dynamics NAV 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