The WinDev modernization guide
WinDev migration guide
A long-running WinDev system holds decisions your business still depends on. This guide shows how to carry those decisions into a new stack: find the rules, map dependencies, let the business validate, convert in slices, and check the result.
VideoFrom WinDev project to a new system
See the full path from WinDev source to a knowledge base, a phased conversion, and a check of the business rules.
Read chapter →Find the rules before you count screens
Business rules in WinDev live in events, queries, procedures, and project initialization—not only in windows.
Read chapter →Map what depends on what
Use the project's dependency graph to understand calls, data use, navigation, and the order of conversion.
Read chapter →Let the business validate behavior
Turn code paths into decision tables and diagrams that domain experts can review before conversion.
Read chapter →Imported is not yet understood
Separate source import from explanations, rule coverage, and conversion readiness.
Read chapter →Convert in slices your team can approve
Build a phased roadmap from dependencies and business rules, then approve each cut with human judgment.
Read chapter →Check every rule in the converted code
A compiling screen is only the start; compare the rule catalog with the delivered implementation.
Read chapter →Tutorials
VideoImport a WinDev project into the Knowledge Base
Follow the source ZIP, optional schema, enrichment, audit, and roadmap approval shown in the import walkthrough.
Read chapter →VideoInside the Knowledge Base
Explore explanations, rules, wireframes, diagrams, and graph views produced from a WinDev project.
Read chapter →VideoDesign a prototype from the Knowledge Base
Choose a visual template, brief the Design cockpit with project knowledge, review the prototype, and mark changes on screen.
Read chapter →