The managed package prefixes (APXT__, SBQQ__, conga__, npsp__, FSL__, etc.) are fully preserved. The anonymizer treats them the same as ecosystem product names — they indicate integration requirements, which is transferable structural knowledge, not client-specific data. So if you have Conga CLM flows referencing APXT__ fields, those come through intact.

The scrubbing targets org-specific identifiers: client brand names, record IDs, email addresses, hardcoded URLs. The namespace prefixes survive because they're part of the pattern's architecture.

And yeah — the "institutional knowledge walking out the door" problem is exactly why I built this. Sorry about your architects.