Preserve policy-correct historical records during migration
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.
“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 pulls against what
- fixed deadline vs. deletion certainty
- migration throughput vs. workspace-level proof
- automated mapping vs. verified policy application
- data minimization vs. legal-hold preservation
What is at stake
A fixed migration deadline collides with irreversible deletion and conflicting record attributes. Success requires proof that each workspace’s history was handled correctly
Why Figma
At Figma, enterprise trust can often depend on whether durable collaboration records are handled with the right evidence and boundaries.
Written for
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.