An IT manager at an accounting and tax firm reached out last week, partway through a serious hunt for a new ERP (enterprise resource planning system). The firm runs on NetSuite today, the three-year deal is up next spring, and they'd narrowed the field to a few options. What caught their attention was a simple realization: the whole company already runs on Microsoft 365, so maybe the accounting platform should live there too.
It's a fair instinct, and it comes up a lot. If your people already spend their day in Outlook, Teams, Excel, and SharePoint, does choosing a Microsoft-native ERP make life easier? Mostly yes, but it helps to know why, and where the edges are.
What "same ecosystem" gets you
When your ERP sits under the same umbrella as your email, files, and identity, a lot of the plumbing is already connected. You're not bolting a foreign system onto Microsoft 365 with connectors and middleware. Users sign in with the accounts they already have. Data can move between the accounting system and Excel or Power BI without a third-party bridge.
With another platform, you can usually still make those connections. You just tend to need bolt-ons, connectors, or custom development to get there. Inside the same data model, a good chunk of that is ready out of the box.
Ask any ERP vendor to show you exactly how a record flows from their system into Excel, Outlook, and your reporting tool. If the real answer involves a paid third-party connector, factor that into the price and the maintenance.
The firm's real problem was projects, not just the ledger
The bookkeeping in NetSuite was the part they liked. The general ledger worked. The pain was around everything else: clunky project tracking, restrictive license tiers where lower-cost users couldn't see where a project stood, billing and payment-processor headaches, and workarounds just to look up a client the way they wanted to.
That distinction matters. This is a professional services firm. They run engagements, track work against them, and bill from them. For that shape of business, the accounting ledger is only half the story. The other half is project operations: managing tasks, tracking time, and turning that work into invoices.
Where Project Operations and Business Central fit
For a services firm like this, the likely starting point is Microsoft Dynamics 365 Project Operations for the engagement and project side, flowing through to Business Central for the general ledger and core ERP. Think of Project Operations as project management tied directly into an accounting function, so the work and the money aren't tracked in two disconnected places.
We're doing something similar right now for a services group in the water treatment space. Their core is projects, but those projects flow through to Business Central for the general ledger, which we're migrating them onto from an older system.
| Job to be done | Where it lives |
|---|---|
| Track engagements, tasks, and time | Dynamics 365 Project Operations |
| General ledger and core accounting | Business Central |
| Reporting across both | Power BI, same ecosystem |
| Sign-in and email | Microsoft 365 accounts you already have |
About the wish-list items
This firm also had a list: a client portal for documents, invoices, and payments, a lighter magic-link style option for one-off clients, and an appointment scheduler their receptionist could run without re-keying client details. Some of that is straightforward. Some of it, like a clean two-way sync between a scheduling tool and client records, takes a little creativity around the data model.
That's the right time to raise those items, not after you've signed. Once you've got a single, solid source of truth for client data, extending it toward portals, scheduling, and reminders becomes a design question rather than a fight against the platform.
A word on price
Price was top of mind, and reasonably so after a rough vendor experience. Microsoft licensing tends to read as more approachable than some competitors, but the published per-user number is never the whole picture. Implementation, data migration off your current system, and any custom work all belong in the estimate. The fix for that is to get a ballpark scope and price out early rather than five weeks into the process, so nobody is surprised.
If you're an accounting or professional services firm weighing an ERP move and you already live in Microsoft 365, we're happy to talk through where the pieces fit and what it would realistically cost. It is a conversation, not a sales call.