Legacy · audit · risk map
Audit and stabilization of a legacy project
Category: Legacy
Stack: Bitrix24 D7, PHP, MySQL, cron, logs
Timeline: 1–2 weeks
Problem
The project works but breaks periodically; there is no documentation; integrations fail for no clear reason; the previous developer left and touching the code is scary.
Constraints
Hidden business logic, no logs or test environment, edits by many authors over the years.
What I did
- Collected entry points and a module map
- Checked cron/agents and background processes
- Found spots without logging and error control
- Identified critical scenarios and risks
- Built a problem map with priorities
- Proposed a step-by-step fix plan
Architecture
Entry points
→ cron / agents
→ Business logic
→ Risk map
→ Fix plan
Result
The team got a clear problem map and could fix the project in stages, without a risky rewrite from scratch.
What can be reused
Audit checklist
Entry-point map
Risk prioritization approach
What was out of scope
- ✗Full architecture rewrite from scratch
- ✗Server infrastructure setup
- ✗Support of third-party APIs without access to logs
- ✗Fixing all historical data