Microsoft Dynamics 365 is hired as a business-operations suite covering sales, service and finance. Where finance or supply chain is in use, its records tie to the general ledger, so this page leads with caution. The realistic route is to narrow the modules and users you license, keep the system of record, and replace a module only after a full close has run alongside it.
A suite like this spreads. One team adopts the sales module, another the service module, and finance moves its processes in later. Each addition ties more of the company's work and data to the same platform, and each license is bought with a different person's budget.
Leaving is not only a software decision. It touches the books, the audit trail and people who have learned to work in it. That is a fair reason to be careful and a poor reason to stop checking what you license. The first question is not what could replace it but how much of it you still use.
Only alternatives we have checked. An open-source project is listed with the license its repository reports, on the date shown; one whose license could not be read as a single standard id is not offered as open source. Read the license guide before running any of them.
| Alternative | Kind | License | Read from |
|---|---|---|---|
| ERPNext | Open source | GPL-3.0 | ERPNext repositoryChecked Oct 25, 2026 |
| A narrow tool for the one module the company really uses | Custom build | — | Written for the one job |
Each feature below is what the product's own page or README says, linked to where we read it on the date shown. Pros and cons are limited to what those pages state and to what the path itself changes. We do not rank products on quality.
Dynamics 365 is a suite, and Microsoft's pricing overview lists its products separately on the checked date, among them sales, customer service, finance and supply chain management. Companies often license more of the suite than they use. Where finance or supply chain is in use, the platform holds operational records that tie to the general ledger.
So the honest advice is to narrow before replacing. Find the single module that justifies the licenses and see whether the rest can shrink first. Do not replace the ledger as a cost-saving move. Keep the system of record until a replacement has run a full close alongside it, and involve your accountant and auditors before moving any record that supports financial statements.
Samples are made up and are not Microsoft Dynamics 365's prices. Type in the figures from your own invoice or order form.
Build a small tool or keep paying for one: the cost of each over your horizon and the month the build breaks even.
Paid seats against seats in use: what the idle ones cost a year, and what you save by right-sizing at renewal.
Arithmetic only, not tax, accounting or legal advice. Check the figures against your own order form.
This is a project run with your accountant, not a switch. The order matters more than the speed.
Find the one module that justifies the licenses. List the products, users, customizations and integrations, and mark which are used and which are leftovers.
Mark which records tie to the general ledger and which are operational only. Anything that supports financial statements needs your accountant's approval before it is moved.
Ask your accountant and auditors in writing what they need to see: the form of the records, the audit trail, and how long they must remain retrievable.
Remove unused licenses and modules where the agreement allows. This is often the largest safe saving and needs no migration.
If a module will move, pilot the replacement on a copy of the data. Compare opening balances, open items and a sample of transactions line by line against the source.
Run the replacement alongside Dynamics 365 for a full close. Reconcile every balance the module touches, and sign off with your accountant before relying on it.
Cut over the module only after sign-off. Keep the old system available, read-only if possible, through the retention period your accountant sets, and end the licenses inside the notice window.
If only one module justifies the licenses, a narrow tool for that job can be worth building. It is written from scratch for that module, with no copied code, screens or branding from any vendor, and it covers only the steps your team really performs.
A build is not a replacement for the ledger. Do not build accounting logic casually: posting rules, period controls and audit trails are easy to get subtly wrong. Costs of building a replacement internally may be capitalizable as internal-use software or expensed. Decide that with a CPA before you begin.
Run the vendor report for QuickBooks Online or Xero, then open the free audit.
General information, not legal advice. See cancelling without penalties. Last reviewed Oct 25, 2026. Product names belong to their owners and are used only to identify them.
Send us the export and see which lines are worth a second look. A connected version is planned. Microsoft Dynamics 365 is one of the lines worth a look.
Worked example. Type over it.
Result
| Year | Buy, cumulative | Build, cumulative |
|---|---|---|
| 1 | 9,000.00 | 8,040.00 |
| 2 | 18,000.00 | 10,080.00 |
| 3 | 27,000.00 | 12,120.00 |
Undiscounted, and it leaves out the vendor's price rises and your own overruns. A tool built for one job is not the whole product: list what you would lose before you count the saving.
Worked example. Type over it.
Result
“In use” is your call: last sign-in in the past 30 or 90 days from the vendor's admin report. A seat for someone on leave is not idle.