These questions often arise in legal operations discussions, offboarding meetings, and those awkward hallway chats after a partner gives notice. Typically, someone in IT wants to close an account, someone in Information Governance (IG) wants to keep it, and nobody is sure who gets to decide. The answers below separate account closure from data governance, which is where most of the confusion lies.
Q1: IT wants to close the former attorney's account on day 30. Records says we can't. Who's right?
Both are right because you're discussing two different issues. Account closure is an infrastructure event, while reviewing the information inside that account is a governance event. They operate on different timelines, and treating them as one creates the standoff.
The solution is a controlled transition process that keeps a defined set of data available after the original account is closed. Authorized personnel can then review client and matter information at their own pace, rather than being rushed by the IT ticket queue. Closing the account stops being a risk once the data you need to manage is accessible and defensible.
Q2: Why can't we just keep every former-user account forever? Storage is cheap.
Storage cost isn't the real issue. The problem is decision cost. Keeping former-user accounts indefinitely means managing large volumes of information without a clear purpose. You also maintain dependencies on source accounts, systems, or infrastructure that you'd otherwise retire.
Under the Generally Accepted Recordkeeping Principles, retention and disposition are paired obligations. If you can't justify why you're keeping something, you're not meeting the retention principle; you're avoiding the disposition decision. Retention is justified where legal, client, contractual, or governance requirements apply. The test is whether you can separate that information from the rest of the account. If you can't, you're treating every item as though it carries the same retention requirement, which it doesn't.
Q3: Doesn't everything tied to a client belong in the DMS?
No, and assuming it does creates its own problem. A departing attorney's data is spread across email, cloud storage, collaboration workspaces, and other sources. Some of it is already in the Document Management System (DMS). Some exists only in the attorney's own data. Plenty of it is personal, administrative, duplicative, or transitory.
The firm must decide which information requires continued governance without assuming everything associated with a client belongs in the permanent client record. Think of it as a Record Declaration decision applied at the content level. Authorized reviewers determine what qualifies as a record for the client file, what stays subject to other obligations, and what has no continuing value. The DMS remains the governed destination for what the firm decides belongs there. The transition process helps you find what hasn't reached it yet.
Q4: Who actually makes the call on what gets transferred?
Authorized firm personnel, not the departing attorney and not IT by default. They decide using client requirements, matter knowledge, firm policies, legal holds, and other obligations. Define that group before the first departure, not during it.
A workable decision structure names who can authorize transfer to the DMS, who can confirm continuing obligations, and who can sign off on Records Disposition Authority for what's left. Active matters, closed matters, partner transitions, retirements, and historical departed-user populations will each need slightly different handling. Write those distinctions into the process now. Improvising them per departure is how inconsistency creeps in.
Q5: How do we know it's safe to dispose of anything after the transfer?
You need evidence that selected information reached its approved destination before any further disposition action. That means validating the transfer, not assuming it. Information can proceed toward disposition once the applicable requirements have been addressed, the necessary transfers are confirmed, and the firm has authorized disposition under its approved process.
Check for an active Legal Hold before anything else. A hold overrides the normal disposition path regardless of how clean the transfer looked. Then confirm the transfer, record the authorization, and keep that documentation. If anyone later asks why data was disposed of, the answer should be a record, not a recollection.
Q6: Where does a platform like Expireon fit, and does it replace our DMS?
It doesn't replace the DMS. A transition platform should complement your existing records and document management systems rather than take over their governance responsibilities. Cloudficient's Expireon supports preservation, search, review, and controlled export. It can retain a defined population of supported data independently of the original account and make it available for authorized search and review.
In practice, that gives Information Governance personnel a place to investigate client and matter information, validate selected content, and export it for ingestion into the DMS or another approved repository. The firm still decides what belongs in the governed client record, what's subject to continuing obligations, and what can move toward approved disposition. The tool supports the process; it doesn't make the judgment calls. Where it helps most is in reducing reliance on indefinite account retention, where permitted, and in giving you one consistent approach across departures instead of a different improvisation each time.
Where to go for more
Start with the Generally Accepted Recordkeeping Principles to frame retention and disposition as linked duties. ISO 30300 is useful if you want to anchor the transition process in a records management system rather than a one-off project. For detailed operational questions, including source mapping and destination decisions, see Cloudficient's practical guide on departing-attorney data.
Then write down your answers to Q4 and Q5. If your firm can't say who decides and how disposition gets authorized, no tool will fix that for you.
