First diagnostic
Run a diagnostic before every Dolibarr upgrade. It is your insurance against an unexpected production outage.
When to run a diagnostic
- Before any major upgrade (e.g. 20.x → 21.x)
- After large custom module or extrafield changes
- When preparing cloning to a target instance
Steps
- Open Knot › Migration › Mission Control.
- Pick the source version (auto-detected) and a signed target reference version.
- Confirm: the engine builds a snapshot (5–30 s on an average instance).
- The comparator downloads the target reference snapshot and renders the analysis report.
- Review schema, modules, extrafields, and integration sections.
Severity levels
| Level | Typical action |
|---|---|
| Information | Document, no blocker |
| Warning | Schedule a fix before cutover |
| Critical | Block the upgrade until resolved |
Partial failures
An unreadable custom module does not abort the whole diagnostic: see Degraded modes and Diagnostic failed.
Next
Analysis workflow Detailed operator walkthrough.
Snapshots Understand the frozen capture.