Best Practices Analyzer · pattern code · Repository structure
BPA code NBCC: Non-backward-compatible node changes
When Adobe's Best Practices Analyzer reports NBCC, it has found non-backward-compatible node changes on your AEM instance. Here is what that means for a move to AEM as a Cloud Service.
What to do
Re-apply customisations through supported extension points.
Can it be fixed automatically?
- Not by Adobe's Content Transformer, which only handles content findings (ACV, CAV, DOPI, OAUI, PCX, REP and URS).
- In our pipeline, automation for this pattern is rated partial: agents prepare part of the change; design decisions stay with an engineer.
How much work is it?
Our readiness scan plans about 1 hour per finding at MAJOR importance (1.5× for CRITICAL, 0.5× for ADVISORY), plus a small fixed cost, capped at 80 hours for this code. INFO rows are treated as inventory and not costed. These are planning figures, not a quote.
Reading the row in results.csv
Filter the code column for NBCC. The importance column says how urgent each row is, identifier usually holds the repository path, and message describes the finding. See how to read a BPA report for every column.
Source: Adobe Pattern Detector documentation for NBCC. Checked 19 October 2026.