Services · Knowledge Recovery
The original developer has resigned. The consultant is unreachable. Documentation is missing. We reconstruct knowledge from code, data, and interviews — structured and handover-ready. At the end you get documentation that looks as if it had never been missing.
Managing Directors · Owners
When the only developer resigns, the consultant is unreachable, or knowledge lives in two heads instead of the system, you have a material risk in your organization. We extract that knowledge in structured form from code, data, and targeted interviews — fixed price (prices on request). The result is documentation that any successor can read, every handover can rely on, and any buyer will accept in due diligence.
Department Head · Business Unit
You're taking over a system whose history no one fully knows anymore. We deliver a knowledge-transfer report with functional map, process paths, data model, customization inventory, and owner list. Structured interviews with power users, admins, and business owners are run and documented methodically. The result is presentable internally — to management, compliance, and the successor team.
IT Lead · CIO · Solution Architect
We read plug-ins, JavaScript web resources, PCF components, workflows, Power Automate flows, and solutions directly from the tenant. From this we reconstruct code map, data-flow diagrams, Dataverse schema, plug-in registrations, trigger logic, and dependency graph. If needed including an ALM reset: clean solution structure, source-control setup, pipeline restoration — so the knowledge is not only documented but operationally controllable again.
For Managing Directors · Risk reduction
Knowledge Recovery is insurance against the bus factor — and at the same time the preparation for any serious handover, partner change, or due-diligence phase. Fixed price (prices on request), 2 to 8 weeks delivery, written documentation at the end. If the original developer is still around, we talk to them. If not, we read the code.
For Department Heads · Knowledge-transfer report
Deliverables: functional inventory, process descriptions from interview material, data-model sketch, customization list with owner mapping, critical special cases and known stumbling blocks. Plus a one-page management summary so you can present the result internally. Documentation in standard format, structured and audit-proof — no half-sentence wiki entries.
For IT leads · Reverse engineering and ALM reset
Direct conversation with the architect. Topics: plug-in code reverse (C# IL and source), JavaScript web-resource mapping, PCF component analysis, Power Automate flow inventory, Dataverse schema export, solution-layering audit, source-control bootstrapping with Git and Power Platform CLI, pipeline rebuild in Azure DevOps or GitHub Actions. Optional process mining on audit logs to validate the reconstructed paths.
Three recovery paths
Which path leads depends on what's still there. In the initial conversation we determine which sources are productive and which mix makes sense.
We read plug-ins, JavaScript, PCF components, workflows, flows, and solutions directly. From the code analysis we reconstruct function, trigger, data flows, dependencies. Code is the most honest source — it does what it does, regardless of whether anyone remembers.
Suitable when: Code access available, original developer no longer reachable.
Structured questioning of remaining employees who worked with the system — power users, admins, business owners. We know which questions to ask to make implicit process knowledge explicit.
Suitable when: Code access limited, but operational users still in the company.
We analyze operational logs (audit logs, workflow runs, telemetry) and derive the actual process paths. You see how the system is really used — as opposed to how it was originally conceived.
Suitable when: Logs available, process understanding missing.
Three recovery packages
Price on request (net)
A specific component or a bounded functional area. Typical: a plug-in set, a critical Power Automate logic, a workflow cluster. Code reverse plus 2–3 targeted interviews.
Price on request (net)
A complete solution of medium complexity — one business application with several modules, integrations, and processes. All three recovery paths combined, depending on the situation.
Price on request (net)
Complex or critical systems — multi-module setups, many integrations, regulated industries. Deep code reverse, extensive interview phase, full process mining.
Scope of delivery
You should be able to maintain the knowledge yourself afterward. That's why we deliberately document in formats that are readable and editable in any Microsoft environment.
Function descriptions, technical specifications, configuration rationale. Format: Markdown or Word, with structures that transfer to Confluence, SharePoint, or DevOps wiki.
Component diagrams, data-model overviews, integration maps, deployment topology. Format: Lucid or draw.io — editable, no vendor lock-in.
Business processes consolidated from code reverse, interviews, and process mining. Per process: trigger, steps, participants, data flows, exception paths. Format: BPMN-oriented diagrams.
What we discovered: implicit assumptions, questionable design decisions, untested edge cases, knowledge gaps that could not be closed. With recommendations for subsequent hardening or refactoring.
Frequently asked questions
Based on our engagements, typically 70–90 percent of the essential business logic and functional structure. What can't be reconstructed: the original rationale for odd-looking design decisions, detailed workarounds for edge cases that have long since disappeared, verbal agreements without a code or data trace. In the recovery report we also document what we explicitly could not clarify — so you know where residual risk still sits.
Then we focus on code reverse and process mining. Code is the most honest source: it does what it does, regardless of whether anyone remembers why. From plug-ins, JavaScript, workflows, and the data model, function can almost completely be reconstructed. Process mining complements operational reality — what actually happens, as opposed to what was intended.
Dynamics 365 (CE, F&O, BC) — plug-ins, JavaScript, workflows, business rules, solutions. Power Platform — apps, flows, pages, connectors, Power Fx formulas. Microsoft 365 — SharePoint solutions, Teams apps, classic SharePoint workflows. Azure integrations — Logic Apps, Functions, Event Grid. Not in scope: deep Azure infrastructure forensics (specialists do that better).
We read the code directly from the solution or repository. Plug-in DLLs are decompiled (when code ownership permits), JavaScript and PCF components are read, workflows and flows are exported as structures. From the code analysis we reconstruct function description, trigger logic, data flows, and dependencies. Result: technical documentation that looks as if the original developer had written it.
Yes. The recovery documentation is deliberately in standard formats: Markdown or Word for text, Lucid or draw.io for diagrams, Excel for inventories. You can take the knowledge into your own wiki, Confluence, SharePoint, or DevOps repository and maintain it. On request, we also hand over maintenance guidelines (which documents must be updated at which release step).
Related services
Structured system intake, when an engagement handover is the actual trigger.
Read more →
Complete inventory of a Microsoft landscape — at tenant level, with devonso.
Read more →
Ongoing care after recovery — fixed-price service with a defined scope.
Read more →
Book a recovery conversation
30-min initial conversation — we determine which sources are still productive and which path leads. Quick, Standard, or Deep Recovery. At the end you get documentation your team can maintain itself.
Take-away · two materials
Two depths for different reading needs. The factsheet is a quick reference (3–5 min) and instantly downloadable. The whitepaper is market education with methodology and comparison data (15–30 min) — you get it by email after a short request.
3–5 min read · Direct download · no form
Compact overview: scope, key metrics, pricing model, process — ideal to forward to CFO, procurement, or the business unit.
15–30 min read · by email after request
Methodology, comparison data, recommendation framework — material for internal argumentation toward stakeholders.
