Services · Take-Over Assessment
Before an engagement handover, we capture the legacy system in a structured way — inventory, customization audit, risk evaluation. Fixed price, no surprises. You get handover-ready documentation and a clear recommendation: take over, rebuild, or drop — per component.
Management · Owner
A provider switch without a structured intake is the most common cause of six-figure follow-up costs. We deliver a fixed-price audit (pricing on request) that creates clarity before the contract is signed: what exists technically, who has which rights, where the risks lie — and what the handover realistically costs?
Department head · Business unit
You get a handover report that holds up internally: 9-dimension intake, risk matrix with mitigation actions, customization inventory with complexity rating, security audit, and a concrete handover plan with milestones. Ready for CIO, CFO, and steering committee.
IT leadership · CIO · Solution Architect
Code inventory (plugins, JavaScript, PCF, Power Fx components) with risk flags. ALM repointing to your Azure DevOps org. Customization inventory per solution with dependency graph. Integration endpoints, service accounts, secrets inventory, workflow status — fully handover-ready.
For Managing Directors · partner switch without a six-figure surprise
The most expensive version of a provider switch is the blind flight. We make the risk visible before you sign a contract: 9-dimension intake at a fixed price, clear handover report, risk matrix with mitigation actions, and a realistic cost frame for the handover. You decide on a data basis — not on sales promises — and reduce switch risk to a calculable level.
For department heads · steering-committee-ready handover plan
A structured first engagement with documented results: 9-dimension intake, risk matrix with concrete mitigation actions, customization inventory with complexity score, security audit, data-quality samples, and a handover plan with milestones. A complete decision template for CIO, CFO, and steering committee — you do not have to build the template yourself.
For IT leadership · technical code-takeover list
You get a technical handover package at architecture level: plugin and JavaScript inventory with function description and risk flags, PCF and Power Fx component list, solution inventory with dependency graph, ALM repointing to your Azure DevOps org with documented pipeline setup, service-account and secrets inventory, integration endpoints with connector status. No black-box handover — everything named, documented, takeable.
What we capture
Before an engagement handover, it must be clear what exists technically, how it is configured, who has which rights, and where the risks lie. We capture all nine dimensions in a structured way.
Microsoft 365 and Dataverse environments, regions, hierarchy, links. Which tenants talk to each other, which are isolated?
Current license assignment per user, add-ons, premium connector consumption, NCE dates, unused seats. Foundation for the renewal strategy.
Solutions, tables, columns, relationships, forms, views, charts, dashboards. Inventory with complexity rating.
Code inventory with function description, trigger configuration, dependencies, risk flags. Complete capture of all code extensions.
Classic workflows, Power Automate cloud flows, business process flows. Status (active / failed / orphaned), triggers, endpoints.
Interfaces to third-party systems (ERP, DMS, webshops, banking). Dataverse connectors, Logic Apps, Azure Functions, direct DB access.
Sample audit: required-field discipline, duplicates, orphaned records, owner distribution. Reality versus expected data-model state.
Security roles, business units, team logic, field-level security, record-sharing rules. Audit on consistency and compliance maturity.
What is documented? How current? How handover-ready? Concrete gaps that must be closed for a handover.
Three size tiers
Which tier fits depends on tenant count, customization depth, and integration density. We clarify the tier in the initial conversation — binding before contract signature.
Pricing on request (net)
Single tenant, manageable customizations, few integrations, clear security structure. Up to 50 users, up to 10 central customizing solutions, up to 3 external interfaces.
Pricing on request (net)
1–2 tenants, medium customization depth, several integrations, complex security model. 50–250 users, mixed plugin and flow inventory.
Pricing on request (net)
Multi-tenant setups, deep customizations, many integrations, international license mix, regulated industries. 250+ users, separate subsidiary logic, compliance requirements.
Deliverables
What you have in hand at the end — handover-ready, classically documented, without special tools.
Structured list of all components: solutions, tables, plugins, flows, connectors, integrations. Per entry: name, purpose, complexity, status, risk flag. Format: Excel and PDF.
Visualization of the customization architecture — which component calls which, what data flows exist, where the nodes are. Format: architecture diagram as PDF and editable source (Lucid or draw.io).
Severity-classified findings: technical risks (code quality, performance bottlenecks), organizational risks (knowledge concentration, documentation gaps), license and compliance risks. With recommendations per finding.
One recommendation per main component: take over (clean, documented, sustainable), rebuild (not sustainable, refactoring effort higher than a rebuild), or drop (function no longer used or replaceable by standard). With effort estimate per path.
Frequently asked questions
No. The Take-Over Assessment is priced as a standalone and delivers handover-ready documentation. You can use it internally, hand it to another provider, or continue with us. The separation is deliberate — we want the handover decision to be made on a clean basis, not on an engagement pitch.
That is your call. In open mode, we work with the previous provider (orderly handover, knowledge-transfer sessions). In discreet mode, the assessment runs without contact — access exclusively through your accounts, without informing the previous provider. Both modes are legitimate and contractually clean.
Reverse engineering: we read the code directly — plugins, JavaScript, PCF, Power Fx formulas, workflows. From the code analysis we reconstruct function, data flows, and business logic. Where code analysis is not enough (e.g., complex process logic), we propose targeted interviews or process mining — see our Knowledge Recovery offering.
That depends on your contract with the current provider. The assessment delivers the functional and technical foundation — inventory, risk evaluation, handover readiness. The legal evaluation of contract termination is a matter for your legal counsel. We recommend running both in parallel so that you can act on the cut-off date.
We focus on the Microsoft stack (Dynamics 365, Power Platform, Microsoft 365, Azure integrations). If the legacy system contains adjacent non-Microsoft components (e.g., SAP interface, external SaaS), we evaluate the Microsoft side and describe the interface. We do not take on pure non-Microsoft evaluations.
Related services
A structured second opinion when the handover has not yet been decided — discreet and independent.
Read more →
When knowledge is missing after the handover — reverse engineering, interviews, process mining.
Ongoing support after the handover — fixed-price service with a defined scope.
Read more →
Book take-over conversation
30-min initial conversation — we clarify system complexity, tier classification, and mode (open or discreet). Fixed price — pricing on request. You get handover-ready documentation and a clear recommendation per component.
To take away · two materials
Two depths for different reading needs. The factsheet is quick reference (3–5 min) and immediately downloadable. The whitepaper is market education with methodology and comparison data (15–30 min) — you receive it by email after a short request.
3–5 min reading time · direct download · no form
Compact overview: scope, key figures, pricing model, approach — ideal for forwarding to CFO, procurement, or business unit.
15–30 min reading time · by email on request
Methodology, comparison data, recommendation framework — material for internal argumentation toward stakeholders.
