There is currently no way to reassign an existing Slot property to a new or incorrectly assigned frame without fully destroying the component and losing all slot content in published instances.
**Steps to reproduce the issue**
1. Create a component set with a Slot property (e.g., "Slot ID3") assigned to a specific frame.
2. Publish the library and use the component in multiple files, populating the slot with content.
3. Later, need to reassign "Slot ID3" to a different frame within the same component (e.g., after restructuring the component layout).
4. There is no "reassign" option. The only available path is:
a. Select all affected frames → right-click → convert back to plain frames
b. Assign a new Slot property
c. Delete the old conflicting "Slot ID3" property
5. Result: all instances that previously had content in "Slot ID3" lose that content permanently.
**Expected behavior**
Figma should allow designers to reassign an existing Slot property to a different frame within a component — similar to how variables or other properties can be rebound — without breaking published instances or losing overrides.
**Impact**
This is a critical issue for teams working with published design systems. Any structural refactoring of a component with slots currently requires treating it as a full rebuild, causing irreversible data loss in consumer files. This severely undermines the value proposition of Slots as a scalable, maintainable system.
**Proposed solution**
Add a "Reassign slot to…" option in the right-click context menu or the Properties panel, allowing designers to remap a Slot property to a new target frame. Figma should then attempt to migrate existing instance overrides to the new frame, similar to how it handles layer rename matching for override preservation.
**Related community threads**
- "Cannot link a slot property across existing variants — must rebuild from scratch" (Figma Forum)
- "Allow slots to replace redundant instance swaps without breaking changes" (Figma Forum)
- "Wrapping/converting to slots breaks overrides" (Figma Forum)