Discover
Process workshops, data audit, and a fit-gap against the standard product.
Phase 1 · Awareness
Enterprise architecture and ecosystem integration
Clean core and dual-write: extending Dynamics 365 without breaking the upgrade path
How to extend Finance and Operations and Dataverse with the Power Platform and Azure while keeping every update a routine event, not a project.
The short answer
Keep the core standard, build around it, and connect through documented interfaces. Every extension should answer one question: what does this cost us at the next update?
Stages
The extension ladder
-
1
Configure Use setup, workflow, security and personalisation first. Nothing to maintain at update time.
-
2
Compose Use Power Platform, Power Automate and Power BI around the system, on Dataverse, with the platform's own connectors.
-
3
Integrate Use Azure services, business events and APIs to talk to other systems, with a visible failure path.
-
4
Extend Write an extension only where the product stops, using extension points and never overlayering.
-
5
Retire Review extensions at every release wave and remove what the product now does as standard.
Decision points
Three questions that change the answer
Can standard configuration do it?
YesConfigure it. Stop here.
NoMove down the ladder.
Does it need to run outside the ERP?
YesCompose it on the Power Platform or Azure and integrate through an API.
NoConsider a small extension in the ERP.
Do two systems need the same record in near real time?
YesUse dual-write for the shared tables and own the sync errors.
NoUse a scheduled or event-driven integration instead.
Milestones
What done looks like, and when
- Design Extension register opened: every extension has an owner and a cost at update.
- Build Extensions use extension points. No overlayering.
- Each update wave Regression tests run on a copy, and extensions are re-justified.
- Yearly Extension register reviewed and trimmed.
Principles we hold to
- Configure first, extend second, and customise last.
- Every extension has an owner and an update cost.
- Dual-write is for shared master data that must agree, not for every table.
- Update waves are routine because the core is standard.
Frequently asked questions
What is a clean core in Dynamics 365?
A standard system that is extended only through supported extension points and companion services, so Microsoft updates apply without rework.
When should we use dual-write?
When the same business record, such as a customer or product, must stay in step between Finance and Operations and Dataverse applications, and you are prepared to own the sync monitoring.
Take this to your own programme.
Tell us where you are. We will tell you plainly what this means for your estate and what we would do first.
Book a consultation
Next: Legacy ERP migration: Dynamics AX, SAP and Dynamics GP to cloud-native Dynamics 365 →
How an engagement runs
01
02
03
04
It starts with a 45-minute consultation, then a discovery and fit-gap workshop on your own processes. You receive a written fit-gap and a phased plan before a programme is agreed. Four phases follow, each with something you can use and review.
Design
Solution blueprint, integration map, and the extensions we will actually need.
Deploy
Configuration, migration rehearsal, role-based training, UAT and phased cutover.
Support
Hypercare, managed services, client portal, scheduled optimisation reviews.
What drives the cost: users, legal entities and currencies, integrations, data migration and the gaps found against standard. See how pricing works, run the three-minute readiness score, or book a consultation.