QuickBooks Desktop
Migrate from QuickBooks Desktop to QuickBooks Online, NetSuite, Sage Intacct, Acumatica or any ERP: load, check and sync your data, then switch.
Book a demo
Migrate from QuickBooks Desktop to the system you choose.
Intuit has stopped selling new QuickBooks Desktop Pro, Premier and Mac subscriptions in the US, and each Desktop version leaves support on a yearly schedule. engini moves you off QuickBooks Desktop to the system you choose, QuickBooks Online, NetSuite, Sage Intacct, Acumatica, Xero or another: it reads customers, vendors, items, the chart of accounts, open invoices and bills, and history from the company file where it runs, loads them into the new system, keeps both in sync during the parallel run, and lets AI agents check every step. Connect from Claude, ChatGPT or Cursor over MCP, from your code, or build in Workflow Studio.
Cursor, your code
audit log

in engini
Move off QuickBooks Desktop on your schedule. To the system you choose, with every record accounted for.
Intuit stopped selling new US subscriptions of QuickBooks Desktop Pro Plus, Premier Plus and Mac Plus after September 30, 2024, and each Desktop version leaves support on a yearly schedule. Growing companies use the move to step up to an ERP. engini connects to QuickBooks Desktop where it runs today and to the system 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.
Connect QuickBooks Desktop as it is
The On-Prem Agent runs on the machine with the QuickBooks company file and reads it through the QuickBooks SDK, with no inbound ports and no file to export by hand.
Map and check
An AI agent proposes how QuickBooks customers, vendors, items, accounts, classes and open invoices and bills map to the new system and lists the records that would not load: missing fields, closed accounts, duplicates. Your team corrects the mapping before anything is written.
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.
Run side by side, then switch
During the parallel run, new invoices, bills and payments in QuickBooks Desktop sync to the new system on a schedule, so both sets of books match until the day you switch. Afterwards, agents can still answer questions from the QuickBooks Desktop history.
Source: Intuit's announcement that new US subscriptions of Desktop Pro Plus, Premier Plus and Mac Plus end after September 30, 2024. QuickBooks Desktop Enterprise is still sold.
Moving off QuickBooks Desktop? 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.
What your agent can do in QuickBooks Desktop. For the move, and until the day you switch.
The QuickBooks Desktop 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
Read master data from the company file.
Read the chart of accounts and classes.
Read what customers owe and what you owe.
Read invoices, bills, payments and journal entries for the dates you choose.
Run a QuickBooks report, such as the trial balance or aging.
Extract the company file's lists, open items and history in batches, for the move.
Write
Add list entries in QuickBooks Desktop.
Enter documents.
Record a customer payment.
Triggers
Invoices, bills, payments or list entries added or changed, for the parallel run.
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.
Connect your AI agent to QuickBooks Desktop. Four ways in, one set of permissions.
Claude, ChatGPT, Cursor
Create an MCP server in engini with your QuickBooks Desktop 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 →Python and TypeScript
Hand your agent a toolset of QuickBooks Desktop tools. The SDK gives OpenAI and Anthropic models the tools in the format they expect and runs the ones they pick.
SDK guide →For coding agents
The engini CLI connects QuickBooks Desktop and runs its tools from a terminal, with machine-readable output, so an AI coding agent can drive it without getting stuck.
CLI guide →Any language
Every QuickBooks Desktop tool is an endpoint. Call it with exact inputs from a scheduled job or a sync, with no model in the loop.
API reference →.cursor/mcp.json. Claude Code: claude mcp add.// .cursor/mcp.json: Cursor, connected to QuickBooks Desktop through engini
{
"mcpServers": {
"engini-quickbooks-desktop": {
"url": "<your engini MCP server address>"
}
}
}
Create the MCP server in engini with your QuickBooks Desktop 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.
Each request runs through the QuickBooks Desktop tools in the agent's toolset or MCP server. If a tool is not allowed, the agent cannot call it.
What teams do with QuickBooks Desktop and engini. The move, and the months around it.
Desktop to Online, or to an ERP
Lists, open invoices and bills and the history you choose load from QuickBooks Desktop into QuickBooks Online, NetSuite or Sage Intacct, checked by an agent.
A parallel run that balances
During the parallel run, Desktop transactions sync every night, and an agent compares trial balances and lists the differences.
Store and CRM orders through the switch
Orders from Shopify and deals from HubSpot flow into Desktop until the switch, then into the new system, through the same workflows.
History you can still ask about
After the switch, an agent answers questions from the old company file. Its toolset holds read tools only.
Every integration runs both ways, so any of these flows can also run in reverse. These are examples, not the limit: any flow between QuickBooks Desktop and another system engini connects is available.
You decide what each agent may do in QuickBooks Desktop. engini enforces it on every call.
Only the tools you allow
A toolset lists the QuickBooks Desktop 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.
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.
Whose permissions apply
Connect a person's own QuickBooks Desktop account and engini acts as that person, with their QuickBooks Desktop permissions. Use a shared integration account and it acts as that account. Every run is recorded under the user who started it.
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.
Every call on record
Every call lands in History and the audit log, which you can export or stream to your SIEM.
Test before production
Workspaces keep teams apart, and development, staging and production environments keep a test agent away from live data.
The company file stays where it is.
Install the engini On-Prem Agent on the Windows machine or server that runs QuickBooks Desktop. It reads the company file through the QuickBooks SDK and opens every connection itself, out to engini over HTTPS on port 443, so you open no inbound ports.
On-Prem Agent guide →Connect QuickBooks Desktop in three steps. Then decide what each agent may do.
Sign in to QuickBooks Desktop
Install the engini On-Prem Agent on the machine with QuickBooks Desktop and allow it access to the company file in QuickBooks. Then connect the system you are moving to.
Choose the tools
Add the connection to an MCP server or a toolset with only the tools each agent needs.
Build or ask
Use the connection as a step in a workflow, or ask your agent to work in QuickBooks Desktop from Claude, ChatGPT, Cursor or your own code.
QuickBooks Desktop and engini. Straight answers.
Can an AI agent write to QuickBooks Desktop, or only read?
Both. engini has tools to create list entries, invoices and bills and to receive payments in QuickBooks Desktop. For the move itself, engini writes to the new system. 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 QuickBooks Desktop?
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 QuickBooks Desktop to a system other than QuickBooks Online?
Yes. Many companies use the move to step up to NetSuite, Sage Intacct or Acumatica instead of QuickBooks Online. engini connects to all of them.
Do we have to switch everything on one day?
No. Load the new system first, then keep QuickBooks Desktop 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 QuickBooks Desktop history?
Bring the history you need into the new system, or keep QuickBooks Desktop 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.
Which Desktop editions does it work with?
QuickBooks Desktop Pro, Premier and Enterprise, US editions, on the Windows machine or server that runs them.
Does the agent act as me in QuickBooks Desktop?
It acts as the QuickBooks user the On-Prem Agent was allowed to use, on the company file you choose. Every run is recorded under the person who started it.
Can a change in QuickBooks Desktop start work?
Yes. Scheduled triggers check the company file for new or changed records, which keeps the new system in sync during the parallel run. A workflow can include an AI agent step.