In shortA client's Priority environment had been customized over many years, and an upgrade was on the way. Before it started, Niv Dekel scanned the environment for standard triggers that had been changed, standard fields that had been modified, and custom code, and turned the findings into a clear work list and a more transparent conversation with the client.
The situation
When a Priority environment has been customized over the years, the important question before an upgrade is what might not work the same way in the new version — and how to find out before the upgrade, not after it.
What was checked
- Standard triggers that had been changed.
- Standard fields that had been modified.
- Custom code.
What came out of it
The findings became a clear work list, which also made the conversation with the client more transparent: what will be affected, why, and where the work starts.
Watch the walkthrough
In Hebrew, 3:50. Shared with the client's approval; identifying details are hidden.
What this means for your upgrade
If your environment has been customized over the years, the same check shows you before the upgrade what's yours, what's at risk and where to start, so the estimate and the conversation with your partner rest on findings.
Last updated 19 October 2026.