Knowledge of the licensed product itself generally cannot, because it is the vendor's and is widely held. Knowledge of how the petitioning organization configured, extended and operates that product may qualify if it is described concretely and shown to be uncommon.
Draw the line before an adjudicator draws it for you
Cases built on a familiar product name fail when the petition never distinguishes the platform from the practice. The workable approach is to write two lists. The first is what any trained user of the product knows: its modules, its standard reports, its administrative screens.
The second is what only this organization knows: the assessment logic it wrote, the escalation thresholds it chose and why, the integrations it built, the data model that links its own operational decisions, and the accumulated judgement about what works in its facilities. The petition should assert nothing about the first list and everything about the second, supported by internal documents. Where the second list turns out to be short, that is important information for the employer, because it suggests the transfer should be built on a different basis or a different person.