When rebuilding or refactoring a component set, there's currently no straightforward way to seamlessly migrate existing instances to the new version if the original component set needs to be deleted.
I'd love a feature that allows designers to map a replacement component (or component set) before deleting the original. When the updated library is published, Figma would automatically replace all instances of the old component with the new one.
To make migration more reliable, Figma could:
- Match and transfer properties with the same names.
- Preserve nested content by matching layer names (e.g. icons, labels, badges).
- Use AI/Figma Make capabilities to intelligently recreate the visual state of the old instance using the new component structure.
- Provide a migration preview showing any instances that couldn't be mapped automatically.
Example:
I rebuild an entire Button component set to improve the structure and variants. Rather than manually updating hundreds of instances or maintaining the old component indefinitely, I could designate the new Button set as the replacement for the old one. When designers update the library in their files, all existing button instances would be migrated automatically while preserving their labels, icons, and relevant properties.
This would make large-scale design system refactors significantly easier and reduce the need to carry legacy components solely for backwards compatibility.