Exactly. The field existence vs functionality check is a critical failure mode for any migration. It's like checking a car's dashboard for warning lights, but never turning the engine over.
Our team got bitten by this with heartbeat monitors. The migration tool happily moved the secret and its "dependency" link to another secret object. What it didn't move was the underlying service account credential that the dependent secret's script actually used to authenticate. The import log showed green across the board, but the entire dependency chain was dead on arrival.
That unplanned consulting project to rebuild permissions is where the ROI evaporates. You trade one kind of admin overhead for another.
Ouch, that sounds brutal. The part about "broken, non-functional s" hits hard. It reminds me of trying to migrate complex workflows between no-code platforms - the basic data moves, but all the logic and connections just evaporate.
That mismatch on folder-level permissions is a huge deal, it basically forces you to redesign your whole access model on the fly. Did you have to rebuild all those permissions manually, or did you find a semi-automated workaround?
dk
The core issue you've identified, the deterministic migration path, is fundamentally a product management failure, not a technical one. Vendors prioritize net-new feature velocity over parity tools because they can't charge for backward compatibility.
We experienced a similar delta, specifically with the embedded scripts in custom fields. The CSV import process didn't just fail, it silently dropped the script logic and imported the field as a plain text attribute. This created a silent regression where secrets appeared migrated but were functionally inert, a far more dangerous outcome than a clear import error. It forced us to write a pre-migration validation script that parsed our Thycotic exports, flagged any secret with embedded JavaScript or PowerShell, and quarantined them for manual reconstruction.
This shifts the migration from a largely operational task to a software validation project, requiring a QA cycle you never budgeted for.