Integration mission · Microsoft Dynamics
Dynamics, and the tool beside it.
You run Business Central, or Dynamics 365, or a Navision that everyone still calls Navision. Beside it there's a vertical tool, a webshop or a planning system, and between them a gap your partner quoted in months. Meanwhile someone exports, someone imports, and the two never quite agree.
Book a 30-minute callWhat we do here.
We connect the tool beside Dynamics through the interfaces Microsoft publishes, from the outside: the standard APIs and web services for Business Central, Dataverse for the CRM side, the data entities for Finance & Operations. We don't build inside as extensions unless a case truly needs it, and here's why that matters: Business Central updates itself twice a year with monthly patches in between, and everything built inside has to keep up. A connection built beside it doesn't.
The plan decides what the connection means: which system owns the customer, the item, the price and the stock; what an order does to inventory and to finance when it arrives from outside; what happens on conflict, on failure, on deletion. It's written down, with a fixed quote, before anything is built. Most of what a partner spends months on is this decision; we do it in two days with the people who know your process.
Weeks to a running connection, tested and monitored, running on your side. When the process changes, the connection follows in days.
What you get.
-
A connection that runs on your side, in your accounts
-
An alert when something didn't sync, before month-end finds it
-
Tests around it, so a change doesn't break it
-
Documentation someone else can pick up
-
Upkeep priced in from day one, so "it follows your business" stays true
How it runs.
1
The plan, two days
We sit with the people who use both systems, then write the plan: what connects to what, which system owns which data, what happens on conflict, on failure, on deletion, and what it will cost to build.
2
The build, quoted in the plan
A block of days. Tests around the connection, monitoring, documentation, code running on your side.
3
It runs, and we watch it
The first weeks monitored by us. After that, the bucket of days for changes.
Proof
A thirty-year-old scheduling product · twenty days, embedded
The one engineer who knew it all was retiring. Twenty days later, two others were working in his code.
A ten-person software company, a codebase started in the eighties, and every module owned by exactly one person. We embedded, built a feature that touched the oldest parts, left two hundred tests and a converter that moved their version control with its history intact. Then two of their developers worked, unsupervised, in code they had never seen, and one of them was closing tickets in the thirty-year-old core.
200 tests · 2 repositories migrated · 2 developers crossed over · 20 days
Read the caseThree questions.
- We have a Dynamics partner. Where do you fit?
- Beside them. We don't modify what they maintain; we connect to it through the standard interfaces. If your partner prefers to review the plan, they're welcome in the room.
- Business Central, Finance & Operations or the CRM: does it matter?
- Only for the interface we use. The plan and the way of working are the same.
- Our IT department will want to see this.
- Good. The plan is written for them as much as for you: data ownership, failure modes, access, where the code runs and who can read it.
Price.
Integration plan.
Two days, €1,500 excl. VAT. The plan is yours. Build it with us, or with anyone.
Build.
Quoted in the plan, as a block of days, monitoring for the first weeks included. Most connections land between €4,000 and €9,000. Changes afterwards from the bucket of days.
Not for.
- A tool with no interface at all. We'll tell you in the first call, and what the alternatives are.
- A one-off data migration. Different job; ask us anyway.
- Anyone who wants the system of record customised from the inside.
Tell us about Microsoft Dynamics.
Lean builders. We deliver.