< Back to all integrations

Microsoft Dynamics NAV

ERP & Finance

Migrate from Microsoft Dynamics NAV to Business Central, NetSuite, Acumatica or any ERP: load, check and sync your NAV data, then switch on your schedule.

Book a demo
[ Microsoft Dynamics NAV + engini ]

Migrate from Microsoft Dynamics NAV to the ERP you choose.

Microsoft Dynamics NAV is at the end of its life: extended support for NAV 2018, the last release, ends on January 11, 2028, and older versions are already out of support. engini moves you off NAV to the ERP you choose, Business Central, NetSuite, Acumatica, Sage Intacct or another: it reads customers, vendors, items, G/L accounts and dimensions, open entries and history from NAV where it runs, loads them into the new ERP, keeps both in sync during the parallel run, and lets AI agents check every step. Until you switch, the same connection lets agents and workflows work in NAV. Connect from Claude, ChatGPT or Cursor over MCP, from your code, or build in Workflow Studio.

MCPPython and TypeScript SDKCLIREST APIWorkflow Studio
End of supportNAV 2018 extended support ends January 11, 2028; older NAV versions are already out of support
Move toAny ERP engini connects: Business Central, NetSuite, Acumatica, Sage Intacct and more
ReachNAV web services and the SQL Server database, through the On-Prem Agent
[ Migration ]

Move off Dynamics NAV on your schedule. To the ERP you choose, with every record accounted for.

Extended support for NAV 2018, the last release, ends on January 11, 2028, and NAV 2016 and 2017 come off support before it. Customizations make the move harder, so start with the data. engini connects to Dynamics NAV where it runs today and to the ERP you are moving to, so you can load the new system, run both side by side and switch when the numbers match. We help you with the move, working with your team or your implementation partner.

Step 01

Connect Dynamics NAV as it is

The On-Prem Agent reaches NAV web services and the NAV database on SQL Server inside your network, with no inbound ports and nothing installed on the ERP.

Step 02

Map and check

An AI agent proposes how NAV customers, vendors, items, G/L accounts, dimensions, open entries and your custom tables map to the new ERP and lists the records that would not load: missing fields, closed accounts, duplicates. Your team corrects the mapping before anything is written.

Step 03

Load in batches

Master data, open receivables and payables, balances and the history you choose move in batches. Every record is in History, so nothing is lost or loaded twice, and failed rows are retried.

Step 04

Run side by side, then switch

During the parallel run, new transactions in Dynamics NAV sync to the new ERP on a schedule, so both sets of books match until the day you switch. Afterwards, agents can still answer questions from the Dynamics NAV history.

[ We help you migrate ]

Moving off Microsoft Dynamics NAV? We help you do it.

Tell us what you run today and where you are moving. We help you plan the move, map and check the data, load it and run both systems side by side until you switch, working with your team or your implementation partner.

[ 01 / What agents can do ]

What your agent can do in Dynamics NAV. For the move, and until the day you switch.

The Microsoft Dynamics NAV tools in engini, grouped by what they change. Read tools are safe to hand out widely. Write and delete tools go only to the agents that need them.

Read

Get Customers, Get Vendors, Get Items

Read master data from the NAV company you choose.

Read
Get G/L Accounts, Get G/L Entries, Get Dimensions

Read the chart of accounts, posted entries and dimension values.

Read
Get Customer Ledger Entries, Get Vendor Ledger Entries

Read open and closed receivables and payables.

Read
Get Sales Documents, Get Purchase Documents

Read open orders, invoices and credit memos.

Read
Get Records from a Web Service

Read any page or query you publish as a web service, custom ones included.

Read
Run Query

Read any NAV table with a SQL query, custom tables included. Read only.

Read
Export Company Data

Extract a NAV company's master data, open entries and history in batches, for the move.

Read

Write

Create Customer, Create Vendor, Create Item

Add master data through NAV web services.

Write
Create Sales Order, Create Purchase Order

Enter documents with their lines.

Write
Call Codeunit

Run a codeunit you publish as a web service, such as a posting routine.

Write

Triggers

Check for New or Changed Records

Customers, vendors, items or documents added or changed in NAV, for the parallel run.

Scheduled
Check for New G/L Entries

New posted entries.

Scheduled

A trigger starts a workflow, and a workflow can include an AI agent step. In Code, a trigger delivers the event to your own endpoint.

[ 02 / Connect your agent ]

Connect your AI agent to Microsoft Dynamics NAV. Four ways in, one set of permissions.

MCP

Claude, ChatGPT, Cursor

Create an MCP server in engini with your Microsoft Dynamics NAV connection and only the tools you choose. Add its address to your client and sign in through engini. There is no key to copy.

MCP client setup →
SDK

Python and TypeScript

Hand your agent a toolset of Microsoft Dynamics NAV tools. The SDK gives OpenAI and Anthropic models the tools in the format they expect and runs the ones they pick.

SDK guide →
CLI

For coding agents

The engini CLI connects Microsoft Dynamics NAV and runs its tools from a terminal, with machine-readable output, so an AI coding agent can drive it without getting stuck.

CLI guide →
REST API

Any language

Every Microsoft Dynamics NAV tool is an endpoint. Call it with exact inputs from a scheduled job or a sync, with no model in the loop.

API reference →
MCP in four steps
In engini, connect Microsoft Dynamics NAV and create an MCP server with that connection and the tools this agent may use.
Claude: Settings, Connectors, Add custom connector, then paste the server address.
Cursor: add the address to .cursor/mcp.json. Claude Code: claude mcp add.
Sign in through engini when the client asks. The agent sees only the tools you chose.
Cursor, connected to Microsoft Dynamics NAV through engini
// .cursor/mcp.json: Cursor, connected to Microsoft Dynamics NAV through engini
{
"mcpServers": {
"engini-microsoft-dynamics-nav": {
"url": "<your engini MCP server address>"
}
}
}

Create the MCP server in engini with your Microsoft Dynamics NAV connection and the tools this agent may use, then paste its address. The client signs in through engini on first use. Claude, VS Code and other clients take the same address: see the MCP client setup guide.

Try asking your agent
“How many customers in NAV have had no activity in three years?”
“Which items would fail to load into Business Central, and why?”
“Compare the NAV trial balance for October with the new ERP.”
“List our custom tables and how many records each has.”
“Export open customer ledger entries from NAV.”
“Sync yesterday's NAV sales invoices to NetSuite.”

Each request runs through the Microsoft Dynamics NAV tools in the agent's toolset or MCP server. If a tool is not allowed, the agent cannot call it.

[ 03 / What teams build ]

What teams do with NAV and engini. The move, and the months around it.

Finance

NAV to Business Central, or somewhere else

Master data, open entries and history load from NAV into the new ERP in batches, checked by an agent, with every record logged.

Microsoft Dynamics NAVDynamics 365 Business CentralNetSuite
Controllers

A parallel run that balances

During the parallel run, NAV entries sync to the new ERP every night, and an agent compares balances by dimension and lists the differences.

Microsoft Dynamics NAVAcumatica
IT

Customizations understood before the move

An agent lists custom tables and fields and how much data each holds, so the team knows what to carry over and what to leave.

Microsoft Dynamics NAVClaude
Everyone

History you can still ask about

After the switch, an agent in Teams answers questions from NAV history. Its toolset holds read tools only.

Microsoft TeamsMicrosoft Dynamics NAV

Every integration runs both ways, so any of these flows can also run in reverse. These are examples, not the limit: any flow between Microsoft Dynamics NAV and another system engini connects is available.

[ 04 / Agent Policy ]

You decide what each agent may do in Microsoft Dynamics NAV. engini enforces it on every call.

Toolsets

Only the tools you allow

A toolset lists the Microsoft Dynamics NAV tools an agent may call and the connection each one uses. Give one agent read tools only and another the write it needs. engini refuses any call outside the toolset.

MCP servers

Scoped when you set them up

An MCP server exposes only the connections and tools chosen when it is created, and engini shows who uses each server.

Identity

Whose permissions apply

Connect a person's own Microsoft Dynamics NAV account and engini acts as that person, with their Microsoft Dynamics NAV permissions. Use a shared integration account and it acts as that account. Every run is recorded under the user who started it.

Credentials

Kept out of prompts

Your agent never needs your credentials: engini stores them and adds them when it runs each call, so keys stay out of prompts and tool inputs.

Audit

Every call on record

Every call lands in History and the audit log, which you can export or stream to your SIEM.

Environments

Test before production

Workspaces keep teams apart, and development, staging and production environments keep a test agent away from live data.

SOC 2 Type IIISO 27001GDPRSecurity at engini →
[ Behind your firewall ]

Dynamics NAV behind your firewall.

If Dynamics NAV runs in your own data center, install the engini On-Prem Agent on a server inside your network. It opens every connection itself: out to engini over HTTPS on port 443, and to Dynamics NAV while it runs a task. You open no inbound ports or firewall rules. Calls through it run on the same engine as MCP, the API and workflows, and each one is recorded in History.

On-Prem Agent guide →
[ 05 / Set up ]

Connect Microsoft Dynamics NAV in three steps. Then decide what each agent may do.

Step 01

Sign in to Microsoft Dynamics NAV

Install the engini On-Prem Agent on a server that can reach NAV, publish the pages and codeunits the workflows need as web services, and create a NAV user and a SQL login with read access. Then connect the ERP you are moving to.

Step 02

Choose the tools

Add the connection to an MCP server or a toolset with only the tools each agent needs.

Step 03

Build or ask

Use the connection as a step in a workflow, or ask your agent to work in Microsoft Dynamics NAV from Claude, ChatGPT, Cursor or your own code.

[ 06 / Questions ]

Microsoft Dynamics NAV and engini. Straight answers.

Can an AI agent write to Microsoft Dynamics NAV, or only read?

Both. engini has tools to create customers, vendors, items and documents in NAV and to call published codeunits. For the move itself, engini writes to the new ERP. Whether a given agent may use them is up to you: give it a toolset or an MCP server with read tools only, and it cannot call the rest.

Does engini help with the migration from Dynamics NAV?

Yes. We help you plan the move, map and check the data, load it and run the parallel period until you switch, working with your team or your implementation partner. Book a call and tell us what you run today and where you are moving.

Can we move from Dynamics NAV to an ERP other than Business Central?

Yes. engini connects to Business Central, NetSuite, Sage Intacct, Acumatica, SAP, Oracle and more, so you choose the ERP that fits the business, not the one the old vendor points to.

Do we have to switch everything on one day?

No. Load the new ERP first, then keep Dynamics NAV and the new system in sync during a parallel run, area by area if you like, and switch when the numbers match.

What happens to our Dynamics NAV history?

Bring the history you need into the new ERP, or keep Dynamics NAV read-only and let agents answer questions from it, through the same connection, until you retire it.

Can our implementation partner use engini?

Yes. Partners use engini to load, check and sync data during the move, and the same connections keep running the integrations after go-live.

When does support for Dynamics NAV end?

Microsoft's lifecycle page lists January 11, 2028 as the end of extended support for NAV 2018, the last NAV release. Earlier versions end sooner or have already ended.

Which NAV versions does it work with?

NAV 2013 and later through web services and SQL Server. Older versions can be read through SQL Server.

Does the agent act as me in Microsoft Dynamics NAV?

It acts as the NAV user and SQL login behind the connection. Every run is recorded under the person who started it.

Can a change in Microsoft Dynamics NAV start work?

Yes. Scheduled triggers check NAV for new or changed records and posted entries, which keeps the new ERP in sync during the parallel run. A workflow can include an AI agent step.