Security migrations can be necessary long before every exceptional path is easy to prove safe.
The pressure to retire aging protection can conflict with the need to preserve recoverability for every important artifact.
Who you’d be doing this for
“Those old files still answer production questions. We can’t discover they’re unreadable after the switch.”
Renato Moreno · Head of Design Systems
Maintains business-critical libraries and historical design records in a security-sensitive enterprise workspace.
What is at stake
Rehearsal left 0.6% of objects with legacy key references, expired recovery envelopes, or paths reviewers couldn't confirm. With no practical rollback, you have to judge when the evidence is strong enough to move customer data.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- cryptographic retirement vs. content recoverability
- fixed cutover vs. verified exception handling
- automated coverage vs. human-confirmed evidence
- security urgency vs. irreversible migration risk
Why Figma
At Figma, this can matter because collaborative files and shared assets often remain valuable long after their original creation.
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.