Employee-to-Dependent Conversion Causing Historic Name Mismatch and Duplicate Person Risk in Oracle

We've run into a data conversion issue involving an employee who was later added as a dependent of another employee.

Scenario:
In our legacy PeopleSoft system, Employee A and Employee B were both separate employees. Employee A later resigned, and a few years after that, Employee A was added as a dependent under Employee B's record in PeopleSoft -- but under a different last name than the one on Employee A's original employee record.

During conversion to Oracle HCM Cloud, Employee A was converted as part of the Employee/Worker load (using the original employee record). However, Employee A's dependent record was not converted as a separate Contact -- instead, Oracle tied Employee A's existing Worker/Person record directly to Employee B as the dependent.