Symmy connects Magento with Microsoft Dynamics NAV. Orders flow from Magento into Microsoft Dynamics NAV, while product and stock data as well as documents travel the other way. For this pair we transfer 7 agendas — each one separately, in the direction and interval you choose. A basic connection of one agenda takes 6–12 hours of work depending on its type; we will refine the exact scope after an initial meeting.
Select the modules to integrate
Tick the modules you want to connect — we will estimate the integration and running costs right away.
Supported modules
Integration price from
Running cost from
/ month
Selected modules:
Fill in your contact details
What we transfer and how often
| Module | Direction | Default interval |
|---|---|---|
| Orders received | Magento → Microsoft Dynamics NAV | 15 min |
| Issued invoices | Microsoft Dynamics NAV → Magento | 60 min |
| Product Cards | Microsoft Dynamics NAV → Magento | 60 min |
| Stock availability | Microsoft Dynamics NAV → Magento | 60 min |
| Price lists | Microsoft Dynamics NAV → Magento | 60 min |
| Customers | Magento → Microsoft Dynamics NAV | 60 min |
| Parcel number transport | Microsoft Dynamics NAV → Magento | 60 min |
E-shops are the most common counterparty, but the same modules also flow to CRM, WMS or B2B portals. These values are defaults, not fixed rules. The direction and interval can be changed for each module, and modules not listed here can be added — we shorten the interval when your operation needs a faster response, or extend it when less frequent synchronisation is enough.
How the connection works
On the Magento side we use: REST and GraphQL API (integration tokens). We connect Microsoft Dynamics NAV via: OData/SOAP web services (depending on the NAV version).
What to watch out for
-
1
NAV versions differ significantly.
An older on-premise NAV exposes different web services than newer versions, and bespoke customisations shift the picture further. We verify what your installation actually offers before we commit to a scope.
-
2
One system must own the stock.
When both NAV and the e-shop keep their own stock levels, they drift apart within days. We recommend NAV as the source of truth, reservations included.
-
3
Every Magento is a different installation.
Custom modules and modifications change the API's behaviour; before going live we verify what your installation actually exposes and confirm the scope after the analysis.
-
4
Indexers and cache decide how fresh the data is.
Changes only show up in Magento after reindexing. We time the synchronisation around the indexers, otherwise the e-shop displays stale data.
What lands where in Dynamics NAV
Microsoft Dynamics NAV — formerly Navision, and continued today as Business Central — is still running in hundreds of companies. The table above says which modules move. This one says what a Magento order becomes inside NAV.
Record mapping
| Magento order | Sales order | One document per order; order items become sales lines. |
| Order item | Sales line | Matched to a NAV item by SKU; a configurable product transfers as the simple variant the customer actually bought. |
| Shipping and payment | Sales line with a charge | Kept separate so VAT stays auditable. |
| Customer and customer group | Customer and price group | A Magento group maps to a NAV price group — that is how B2B pricing is handled. |
| NAV item | Magento product | Name, description and category flow from NAV; the shop stays the presentation layer. |
| Inventory availability | Salable quantity | By NAV location, mapped to a Magento MSI source and stock. |
| NAV price list | Price and tier price | Including quantity pricing for wholesale customers. |
| Posted sales invoice | Document on the order | The document number and file are attached to the order in the shop. |
What we need on your side
- Dynamics NAV with web services published (SOAP or OData); for an on-premise installation, a reachable endpoint or a VPN.
- A dedicated NAV user for the integration, with permissions limited to the pages and codeunits involved.
- A NAV test company holding a copy of your production setup including your customisations — that is what we build and test against.
- A Magento 2 integration token with access to the required resources, plus a picture of your MSI sources and stocks if you run more than one.
- Healthy indexers and cron in Magento. Salable quantity is recalculated by an indexer — when it stalls, the shop shows different numbers from NAV no matter how well the transfer works.
- A decision on how products are matched (SKU, EAN) and how configurable products map to NAV variants.
How the project runs
- 01 Analysis We go through your NAV customisations, the Magento extensions and the module list. The output is the mapping, written down — what becomes what and how records are matched.
- 02 Build against a test company The integration runs against a test company holding your setup. You see the first real orders there before anything touches production.
- 03 Acceptance You run your own cases: a configurable product, an order under a cart price rule, a credit memo, a wholesale customer on tier pricing. Whatever fails, we tune.
- 04 Go-live and monitoring The switch to production, then round-the-clock monitoring. For the first weeks we watch the intervals and tune them to real traffic.
Customer testimonials
Integration of Magento with other systems
Pick the system you want to connect with
I want to integrate Magento with another system
Write to usWhat's new with us
All newsNon-profits get a permanent 50 % off
Non-profit organisations get a permanent 50 % discount on everything we do — integrations, running costs and consulting, with no time limit.
Take a lookA calculator that prices your integration
Pick the systems, the areas and the data volume — the calculator shows straight away what drives the price. No waiting for a quote, no phone call.
Take a lookThe site now speaks Slovak and Polish too
Slovak and Polish join Czech, English and German. All five languages carry the full content — integrations, applications and ERPedia.
Frequently asked questions
How much does the integration cost?
We charge 85 € excl. VAT per hour. Connecting one module takes 6–12 hours depending on its type, more for larger systems — we confirm the exact scope after an initial call. The calculator above gives an estimate for your combination of modules.
What happens when Microsoft Dynamics NAV is unavailable?
The synchronisation retries the connection in the next interval, and keeps retrying until it reconnects. An alert goes out the moment the problem is detected, so you will know about the outage before it shows up in your orders.
Need this integration?
Get in touch — we'll discuss your modules, timeline and the exact tailored price, with no obligation.
Useful tips and insights from the world of ERP and integrations, for free
From time to time we share the experience, advice and know-how we gain from working with our partners.
