Microsoft Dynamics CRM
Migrate from Microsoft Dynamics CRM 2016 on premises to Dynamics 365, Salesforce, HubSpot or any CRM: load, check and sync your data, then switch.
Book a demoMigrate from Microsoft Dynamics CRM to the CRM you choose.
Microsoft Dynamics CRM 2016 on premises is out of support: extended support ended on January 13, 2026, so there are no more security updates. engini moves you off Dynamics CRM to the CRM you choose, Dynamics 365, Salesforce, HubSpot, Zoho CRM or another: it reads accounts, contacts, leads, opportunities, cases, activities, notes and your custom entities where CRM runs, loads them into the new CRM with their relationships, 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 CRM on your schedule. To the CRM you choose, with every record accounted for.
Extended support for Dynamics CRM 2016 ended on January 13, 2026, according to Microsoft, so every month on it is a month without security updates. engini connects to Dynamics CRM where it runs today and to the CRM 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 CRM as it is
The On-Prem Agent reaches the CRM Web API and the CRM database inside your network, with no inbound ports and nothing installed on the CRM.
Map and check
An AI agent proposes how CRM accounts, contacts, leads, opportunities, cases, activities, owners and custom entities map to the new CRM 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
Accounts, contacts, opportunities, cases, activities 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 and changed records in Dynamics CRM sync to the new CRM on a schedule, so sales and service never work from stale data until the day you switch. Afterwards, agents can still answer questions from the Dynamics CRM history.
Source: Microsoft's 2026 end-of-support list, Dynamics CRM 2016 extended support ended January 13, 2026.
Moving off Microsoft Dynamics CRM? 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 CRM. For the move, and until the day you switch.
The Microsoft Dynamics CRM 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 customers and prospects with their owners.
Read the pipeline and service history.
Read emails, calls, appointments, notes and files.
Read any entity, custom entities included, with a filter.
Read data with a FetchXML query. Read only.
Extract an entity with its relationships in batches, for the move.
Write
Keep records current until the switch.
Add pipeline and service records.
Write to any entity you allow.
Triggers
Records of the entities you choose, 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 Microsoft Dynamics CRM. Four ways in, one set of permissions.
Claude, ChatGPT, Cursor
Create an MCP server in engini with your Microsoft Dynamics CRM 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 CRM 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 CRM 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 CRM 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 CRM through engini
{
"mcpServers": {
"engini-microsoft-dynamics-crm": {
"url": "<your engini MCP server address>"
}
}
}
Create the MCP server in engini with your Microsoft Dynamics CRM 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 CRM tools in the agent's toolset or MCP server. If a tool is not allowed, the agent cannot call it.
What teams do with Dynamics CRM and engini. The move, and the months around it.
CRM 2016 to Dynamics 365 or Salesforce
Accounts, contacts, opportunities and activities load into the new CRM with their owners and relationships, checked by an agent.
Case history that comes along
Open and closed cases move with their notes and attachments, so agents in the new CRM see the full history.
Duplicates cleaned on the way
An agent finds duplicate accounts and contacts before the load and proposes which to merge.
Integrations that survive the move
The ERP and marketing tools keep syncing with CRM until the switch, then with the new CRM, through the same workflows.
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 CRM and another system engini connects is available.
You decide what each agent may do in Microsoft Dynamics CRM. engini enforces it on every call.
Only the tools you allow
A toolset lists the Microsoft Dynamics CRM 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 CRM account and engini acts as that person, with their Microsoft Dynamics CRM 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 CRM behind your firewall.
If Dynamics CRM 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 CRM 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 CRM in three steps. Then decide what each agent may do.
Sign in to Microsoft Dynamics CRM
Install the engini On-Prem Agent on a server that can reach Dynamics CRM, create a CRM user with read access to the entities you are moving, then connect the CRM 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 CRM from Claude, ChatGPT, Cursor or your own code.
Microsoft Dynamics CRM and engini. Straight answers.
Can an AI agent write to Microsoft Dynamics CRM, or only read?
Both. engini has tools to create and update records in Dynamics CRM. For the move itself, engini writes to the new CRM. 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 CRM?
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 CRM to a CRM other than Dynamics 365?
Yes. engini connects to Dynamics 365, Salesforce, HubSpot, Zoho CRM and Pipedrive, so you choose the CRM that fits the team.
Do we have to switch everything on one day?
No. Load the new CRM first, then keep Dynamics CRM 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 CRM history?
Bring the history you need into the new CRM, or keep Dynamics CRM 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.
Is Dynamics CRM 2016 still supported?
No. Microsoft lists January 13, 2026 as the end of extended support for Dynamics CRM 2016. Earlier versions ended before it.
Does the agent act as me in Microsoft Dynamics CRM?
It acts as the CRM user behind the connection, with that user's security roles. Every run is recorded under the person who started it.
Can a change in Microsoft Dynamics CRM start work?
Yes. Scheduled triggers check CRM for new or changed records, which keeps the new CRM in sync during the parallel run. A workflow can include an AI agent step.