"empty nester" parents and lingering data

Hi, am I right in assuming that you are referring to members in the entity dimension?

If so, is what you are describing for planning, management reporting, statutory reporting, or another process?

My first thought is, why removing those parents in the first place? Yes, sometimes it happens that members get moved and parents may get obsolete in the entity dimension, but for the most part, they remain as is at least for historical comparisons and base entities get duplicated into the new hierarchy rather than literally cut out of the old one and transferred to the next parent. Not preserving the historical structures makes time based reporting impossible, unless there is a central hierarchy that does not get changed which serves that purpose.

There are two posts on IdeaStream that you might like to give kudos to if you agree with what they are suggesting:

JIRA Ticket: PF-1825 (onestreamsoftware.com)

JIRA Ticket: PF-7988 (onestreamsoftware.com)

To answer you question directly:

To "find" entities that were a parent previously and that your business no longer requires is more of a process management item to me in which the reorganization of the structure needs to follow a defined process in which those former-parents are clearly documented as well and marked for removal or archiving. This can be assisted technically by driving and documenting this process within OneStream. But the process and requirements need to be defined first and the technical aspect of it (workspace) will be built based on that.

There are two other posts with ideas how to delete entities, but I assume that is not new to you (sharing, just in case it helps):

Unable to delete Entity member - OneStream Community (onestreamsoftware.com)

Unable to delete Entity member v2 - OneStream Community (onestreamsoftware.com)