We used “Move Style definition” to this file in the end which worked!
I think it is worth noting for people moving master components or merging libraries that moving the styles over first may be an important step if the components you are using don’t have styles supported in the new library and you want all your styles in one place, ie if you are deprecated the first library.
This has been a very insightful topic to follow! We are in the same position as Timothy above in that as an org, plugins are not allowed. Our DS also has the added concern of being mutli-brand, so the moving of our set of components has from their original library to a new one has to work the same across five different brands, all which then need to be able to swap three separate libraries with each other and retain the nested instance overrides.
We’ve tested with two brands to make sure the swap library function still works after migrating components, and it’s all fine aside from any instance swaps that have been made. Very frustrating, and would love to hear of anyone having any joy with this feature!
I don’t know if the way Figma handles this has changed but the way it was described in this thread and by Figma on Twitter didn’t work as described with our files. The other way around worked fine.
If you have an existing master file with components and designs:
- Publish the original master file as a library without changing anything
- Create a new file and connect the master file as a library.
- Cut the designs from anywhere in the original master file/library
- Paste in the new file - check that the component links work.
- Rename the old file as component library
- Continue working with the designs in the new file.
Worked for me after dabbling unsuccessfully with the original method.