Microsoft Dynamics SL
Migrate from Microsoft Dynamics SL (Solomon) to Deltek, Business Central, NetSuite, Sage Intacct or any ERP: load, check and sync your SL data, then switch.
Book a demoMigrate from Microsoft Dynamics SL to the ERP you choose.
Microsoft Dynamics SL, the project ERP many still call Solomon, is near the end of its life: extended support for SL 2018, the last release, ends on July 11, 2028, and year-end tax updates have already stopped. engini moves you off SL to the ERP you choose, Deltek, Unit4, Business Central, NetSuite, Sage Intacct or another: it reads projects, customers, vendors, the chart of accounts, open documents and history from SL where it runs, loads them into the new ERP, 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 Dynamics SL on your schedule. To the ERP you choose, with every record accounted for.
Extended support for Dynamics SL 2018, the last release, ends on July 11, 2028, and year-end payroll and tax updates have already stopped. engini connects to Dynamics SL 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.
Connect Dynamics SL as it is
The On-Prem Agent reaches the SL application and system databases on SQL Server inside your network, with no inbound ports and nothing installed on the ERP.
Map and check
An AI agent proposes how SL projects, tasks, customers, vendors, accounts, subaccounts 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.
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 transactions in Dynamics SL 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 SL history.
Source: Microsoft lifecycle page for Dynamics SL 2018, extended support end date July 11, 2028.
Moving off Microsoft Dynamics SL? 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 Dynamics SL. For the move, and until the day you switch.
The Microsoft Dynamics SL 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 projects, tasks, budgets and costs to date.
Read master data.
Read the chart of accounts and balances by period.
Read what clients owe and what you owe.
Read time by employee and project.
Read any SL table with a SQL query. Read only.
Extract SL master data, open items and history in batches, for the move.
Write
Add a vendor and enter an invoice in SL.
Add a project with its tasks.
Enter a journal for posting in SL.
Triggers
Projects, documents or vendors added or changed in SL, 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 Microsoft Dynamics SL. Four ways in, one set of permissions.
Claude, ChatGPT, Cursor
Create an MCP server in engini with your Microsoft Dynamics SL 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 Microsoft Dynamics SL 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 Microsoft Dynamics SL 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 Microsoft Dynamics SL 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 Microsoft Dynamics SL through engini
{
"mcpServers": {
"engini-microsoft-dynamics-sl": {
"url": "<your engini MCP server address>"
}
}
}
Create the MCP server in engini with your Microsoft Dynamics SL 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 Microsoft Dynamics SL tools in the agent's toolset or MCP server. If a tool is not allowed, the agent cannot call it.
What teams do with SL and engini. The move, and the months around it.
SL to a project ERP
Projects, budgets and open documents load from SL into Deltek, Unit4 or Business Central, checked by an agent, with every record logged.
A parallel run that balances
During the parallel run, SL transactions sync to the new ERP every night, and an agent compares balances by project and account.
Timesheets and payroll through the switch
Time from the timesheet system keeps flowing into SL until the switch, then into the new ERP, through the same workflow.
History you can still ask about
After the switch, an agent in Teams answers questions from SL history. 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 Microsoft Dynamics SL and another system engini connects is available.
You decide what each agent may do in Microsoft Dynamics SL. engini enforces it on every call.
Only the tools you allow
A toolset lists the Microsoft Dynamics SL 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 Microsoft Dynamics SL account and engini acts as that person, with their Microsoft Dynamics SL 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.
Dynamics SL behind your firewall.
If Dynamics SL 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 SL 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 →Connect Microsoft Dynamics SL in three steps. Then decide what each agent may do.
Sign in to Microsoft Dynamics SL
Install the engini On-Prem Agent on a server that can reach the SL SQL Server, create a SQL login with read access to the SL databases and, if workflows will write to SL, an SL user. Then connect the ERP 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 Microsoft Dynamics SL from Claude, ChatGPT, Cursor or your own code.
Microsoft Dynamics SL and engini. Straight answers.
Can an AI agent write to Microsoft Dynamics SL, or only read?
Both. engini has tools to create vendors, AP vouchers, projects and journal transactions in SL. 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 SL?
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 SL 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 SL 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 SL history?
Bring the history you need into the new ERP, or keep Dynamics SL 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 SL end?
Microsoft's lifecycle page lists July 11, 2028 as the end of extended support for Dynamics SL 2018, the last SL release.
Does the agent act as me in Microsoft Dynamics SL?
It reads as the SQL login and writes as the SL user behind the connection. Every run is recorded under the person who started it.
Can a change in Microsoft Dynamics SL start work?
Yes. Scheduled triggers check SL for new or changed records, which keeps the new ERP in sync during the parallel run. A workflow can include an AI agent step.