A workload name is not a migration boundary
A server or application list tells a team what exists, but not what must keep working together. A dependency register connects a proposed move to the systems, permissions and people that can make the move unsafe. Its purpose is to support a decision, not to produce a complete-looking diagram.
Keep observations separate from assumptions. A dependency seen in configuration is not necessarily active, while a quiet interface may run only at month end. Record how an entry was discovered, when it was checked and who can explain its use. Unknown ownership is an open question, not an empty cell to fill with a convenient team name.
Record six dimensions for each dependency
Start with the source workload and its caller or destination. Add the connection or data path, the runtime artifact or configuration that uses it, the identity permitted to act, the owner able to approve a change, and the evidence needed to verify the relationship. Use references to authorized records rather than placing credentials, personal data or complete production payloads in the register.
For a scheduled reporting job, the dependency might include an input location, a shared library, a scheduler parameter and permission to write the output. Moving the input objects without the matching configuration or permission does not demonstrate that the reporting process works. This is a technical example, not a description of an XIVTech client project.
Use evidence states instead of a false complete flag
A useful record distinguishes observed, owner-confirmed, tested and unresolved relationships. Those states answer different questions: whether a reference exists, whether it is intended, whether a representative execution succeeded, and what remains unknown. Do not treat a successful connectivity check as validation of data meaning or recovery behavior.
Review long-tail execution paths with their owners. Infrequent jobs, external integrations, manual recovery steps and cross-account access may not appear in a short observation window. State that limitation explicitly and agree what evidence is needed before the dependency can be considered for a move.