Historical records become difficult to manage when policy changes faster than storage assumptions.
Completeness, deletion, and proof can pull in different directions once a migration is underway.
Who you’d be doing this for
“I need to know our history is handled exactly as policy says, not just that the migration finished.”
Amanda Vega · Design Operations Director
Administers regulated workspaces where file history may be subject to legal holds and regional retention rules.
What is at stake
The rehearsal showed a clash between retention flags and legal holds on some old records, and the residency deadline will not move. You decide on the safeguards, the checks, and the rollback line before deletion starts.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- fixed deadline vs. deletion certainty
- migration throughput vs. workspace-level proof
- automated mapping vs. verified policy application
- data minimization vs. legal-hold preservation
Why Figma
At Figma, enterprise trust can often depend on whether durable collaboration records are handled with the right evidence and boundaries.
Written with these in mind
Not your kind of problem? 11 more at Figma, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.