< Back to all integrations

Microsoft Dynamics GP

ERP & Finance

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

Book a demo
[ Microsoft Dynamics GP + engini ]

Migrate from Microsoft Dynamics GP to the ERP you choose.

Microsoft retires Dynamics GP on December 31, 2029, and new sales have already stopped. engini moves you off GP to the ERP you choose, Business Central, NetSuite, Sage Intacct, Acumatica or another: it reads customers, vendors, items, the chart of accounts, open documents and history from GP 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 GP. Connect from Claude, ChatGPT or Cursor over MCP, from your code, or build in Workflow Studio.

MCPPython and TypeScript SDKCLIREST APIWorkflow Studio
End of supportMicrosoft retires Dynamics GP on December 31, 2029
Move toAny ERP engini connects: Business Central, NetSuite, Sage Intacct, Acumatica, SAP, Oracle and more
ReachGP company databases on SQL Server, and eConnect for writes, through the On-Prem Agent
[ Migration ]

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

Microsoft retires Dynamics GP on December 31, 2029. Its own path leads to Business Central, but the choice of ERP is yours. engini connects to Dynamics GP 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 GP as it is

The On-Prem Agent reaches the GP company databases on SQL Server and eConnect inside your network, with no inbound ports and nothing installed on the ERP.

Step 02

Map and check

An AI agent proposes how GP customers, vendors, items, accounts, segments and open documents 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 GP 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 GP history.

Source: Microsoft lifecycle page for Dynamics GP, retirement date December 31, 2029. New GP sales have ended; existing customers keep support until that date.

[ We help you migrate ]

Moving off Microsoft Dynamics GP? 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 GP. For the move, and until the day you switch.

The Microsoft Dynamics GP 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 GP company you choose.

Read
Get GL Accounts, Get Account Balances

Read the chart of accounts, segments and balances by period.

Read
Get Open Receivables, Get Open Payables

Read what customers owe and what you owe, document by document.

Read
Get Sales Documents, Get Purchase Orders

Read SOP and POP documents, open and historical.

Read
Get GL Transactions

Read posted journal history for the periods you choose.

Read
Run Query

Read any GP table or view with a SQL query. Read only.

Read
Export Company Data

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

Read

Write

Create Customer, Create Vendor, Create Item

Add master data in GP through eConnect.

Write
Create Sales Invoice, Create Sales Order

Enter SOP documents.

Write
Create Payables Transaction

Enter a vendor invoice.

Write
Create GL Journal Entry

Enter a journal entry for posting in GP.

Write

Triggers

Check for New or Changed Records

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

Scheduled
Check for Posted Transactions

New posted GL transactions.

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 GP. Four ways in, one set of permissions.

MCP

Claude, ChatGPT, Cursor

Create an MCP server in engini with your Microsoft Dynamics GP 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 GP 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 GP 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 GP 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 GP 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 GP through engini
// .cursor/mcp.json: Cursor, connected to Microsoft Dynamics GP through engini
{
"mcpServers": {
"engini-microsoft-dynamics-gp": {
"url": "<your engini MCP server address>"
}
}
}

Create the MCP server in engini with your Microsoft Dynamics GP 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 active customers and vendors do we have in GP?”
“Which customer records would fail to load into NetSuite, and why?”
“Compare the GP trial balance for October with Business Central.”
“Which open invoices in GP have no match in the new ERP yet?”
“Export the item list with prices from GP.”
“Sync yesterday's GP sales invoices to Sage Intacct.”

Each request runs through the Microsoft Dynamics GP 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 GP and engini. The move, and the months around it.

Finance

GP to Business Central or NetSuite

Customers, vendors, items and open documents load from GP into the new ERP in batches, checked by an agent, with every record logged.

Microsoft Dynamics GPDynamics 365 Business CentralNetSuite
Controllers

A parallel run that balances

During the parallel run, GP transactions sync to the new ERP every night, and an agent compares trial balances and lists the differences.

Microsoft Dynamics GPSage Intacct
Operations

Integrations that survive the move

Orders from Shopify and data from Salesforce flow into GP today and into the new ERP after the switch, through the same workflows.

ShopifySalesforceMicrosoft Dynamics GP
Everyone

History you can still ask about

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

Microsoft TeamsMicrosoft Dynamics GP

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 GP and another system engini connects is available.

[ 04 / Agent Policy ]

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

Toolsets

Only the tools you allow

A toolset lists the Microsoft Dynamics GP 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 GP account and engini acts as that person, with their Microsoft Dynamics GP 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 GP behind your firewall.

If Dynamics GP 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 GP 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 GP in three steps. Then decide what each agent may do.

Step 01

Sign in to Microsoft Dynamics GP

Install the engini On-Prem Agent on a server that can reach the GP SQL Server, create a SQL login with read access to the GP company databases, and, if workflows will write to GP, an eConnect user. 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 GP from Claude, ChatGPT, Cursor or your own code.

[ 06 / Questions ]

Microsoft Dynamics GP and engini. Straight answers.

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

Both. engini has tools to create customers, vendors, items, sales documents, payables transactions and journal entries in GP. 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 GP?

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 GP 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 GP 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 GP history?

Bring the history you need into the new ERP, or keep Dynamics GP 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 GP end?

Microsoft's lifecycle page lists December 31, 2029 as the retirement date for Dynamics GP. New sales have already ended.

Which GP versions does it work with?

Dynamics GP 2015 and later on SQL Server, including GP 18. Older versions can be read through SQL Server too.

Does the agent act as me in Microsoft Dynamics GP?

It reads as the SQL login and writes as the eConnect user behind the connection. Every run is recorded under the person who started it.

Can a change in Microsoft Dynamics GP start work?

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