Skip to main content

Improving Migration: Swap Instance → Slots Workflow

  • March 23, 2026
  • 2 replies
  • 105 views

Jonathan METZ

Hi Figma team,

First, congratulations on the Slots feature. It’s a smart idea and performs very well in my tests.

Issue summary
When migrating components that previously relied on “Swap instance,” I have to add a wrapper frame around the existing instance to use a Slot. Then, every time I place that component, I end up deleting or replacing the inner instance to populate the slot. This breaks my expected workflow: I want to continue using the original instance as the default slot content so that when I instantiate the component I don’t need to manually remove the inner instance each time. Also, if I delete the instance that served as the swap source, the child components lose their contents (the previously swapped instances).

What would be your recommendations for managing the migration from the old system to this new feature?

2 replies

Natasha_Skov-Ludvigsen

+1 on better migration from old “swap instance” to new slots feature.

In our design system, several components depend on slots, and we previously created a placeholder component called "slot" that utilizes the "swap instance" feature. When we "Wrap in new slot" with the old component, the "swap instance" feature becomes unnecessary.


However, removing the "swap instance" feature will reset the old slot and result in lost swapped custom content. This change would result in breaking changes in design files for teams in our organisation. 
 


​​​​​​​Figma needs to improve the migration process to the new slots feature to prevent breaking design files.


claus.stadel
  • New Participant
  • March 26, 2026

Same issue here. Don’t see a good way to convert instance swap property to a slot, without either loosing all content in my current instances - or having to carry instance-swappable nested component around forever in my components.