Our graphic designer left. Design files, accounts, project passwords are all on their device. How will we take these over? Will our data be lost?
How to securely take over the email, files, and accounts of a resigning employee, risk of data loss
Offboarding procedure: All files must be moved to the company cloud before departure. An exit form must be filled out (stating which accesses will be closed). Devices must be returned.
- Job title
- Co-founder
- Sector
- IT services
- Organization type
- family business
- Joined
- Aug 2023
- Message
- 3
Doki · Server maintenance contract · 2024
we suffered too... the project ended because we couldn't access the files on the departing employee's device. never repeat the same mistake
Offboarding checklist: 1. Flag email and cloud accounts 2. Transfer all files to the company server 3. Written release form 4. Return devices 5. Perform access key deletion
Use Google Workspace or Microsoft 365 Administrator Takeover — transfer the departing employee's email to the admin.
- Job title
- Field sales representative
- Sector
- Automotive aftermarket
- Organization type
- medium-sized business
- Joined
- Aug 2024
- Message
- 341
you should immediately freeze the departing employee's cloud account... the offboarding process must be detailed
If I understood correctly, you're saying: Most incidents start with a leaked password, not a vulnerability.
Of course, it varies if your situation is different.
- Job title
- Production planning
- Sector
- Leather
- Organization type
- early-stage startup
- Joined
- Dec 2025
- Message
- 385
The discussion got scattered, let me summarize... The real issue isn't the number, but what it's based on.
An untested backup is not a backup. This is my opinion, I'm not claiming it's absolute truth.
- Job title
- Clinic manager
- Sector
- Real estate
- Organization type
- two-branch business
- Joined
- Jun 2023
- Message
- 176
- Job title
- Product Manager
- Sector
- Tourism
- Organization type
- medium-sized business
- Joined
- Oct 2023
- Message
- 15
I think differently. tbh the biggest time-waster for us was not knowing who had the final say.
I'm also curious if anyone does it differently.
- Job title
- Accounting clerk
- Sector
- Agriculture
- Organization type
- medium-sized business
- Joined
- Nov 2023
- Message
- 176
- Job title
- IT manager
- Sector
- Energy
- Organization type
- 40-person manufacturing company
- Joined
- Jun 2025
- Message
- 354
You're right. Mistakes made on the departing employee's data side are usually reversible but expensive.
i've been down this road, let me tell you then start with a small trial; don't commit to everything at once.
most incidents start with a leaked password, not a vulnerability but i'm also curious if anoyne does it differently.
- Job title
- Field sales representative
- Sector
- Glass
- Organization type
- two-branch business
- Joined
- Jan 2024
- Message
- 155
My question might sound amateurish, sorry about that. An untested backup is not a backup.
Proven by experience.
Thanks for writing this, that's the right way. If 2FA is on, a stolen password alone is useless.
That's all, sorry if I went on too long.
- Job title
- Customer Relations Manager
- Sector
- Furniture manufacturing
- Organization type
- two-branch business
- Joined
- Oct 2023
- Message
- 12
This approach has a cost, which isn't discussed. Trying to do this alone is the most expensive way.
we got stuck at the same point for a while... i mean the harder it is to revese a decision the slower you should make it.
forgotten test environments are more often the entry point than live systems.. then thats all, sorry if I went on too long.
Yes, that's exactly how it is with departing employee's data. Your time to detect an issue directly determines its cost.
Processes without records never improve, because you don't know what to fix. I'm also curious if anyone does it differently.