Unfortunately the major pain point is the needing of open each project file, individually, and manually link the old components with the new ones by using Master.
My company has more than 30 Figma files for different features and its individual different versions. So, open each file to update the components with the new library is insanely painful.
How to transfer old figma projects and their components to a new design library.
- On your old project file, make sure the designs and their components are together on the same page
- Select all and Copy
- Paste them in the new design library you wish the components to live. The design and components must still be linked.
- Publish your new design library
- Select and Cut the designs (without the main components)
- Open a new figma file
- Go to Assets > Team Library and connect the new design library (or update it if you have already done it)
- Paste the designs.
- The components and overrides must still be linked to the new design library.
Thanks @Konstantinos_Partheniadis, this sounds like a much easier method, however, I’m having a hard time following what the needed steps are here. Any chance you can revisit the steps here and provide a bit more detail? For one, I’m not sure what “The design and components must still be linked” means. Or similarly, what “The components and overrides must still be linked to the new design library.” means.
Figma just released a way to move components between files natively!
Hey everyone, has anyone encountered overrides’ reset after moving components? https://help.figma.com/hc/en-us/articles/4404848314647
Unlike Gleb’s Master components (which I used quite often before), this Figma’s new feature doesn’t seem to retain the overrides and ended up breaking a lot of screens in my case.
Yeah, I’m also having the same issue!
Yep, me too, lots of overrides lost which means lost information and broken layouts. Have you tried moving back the components and then restoring the previous version? If you restore it without moving them back it won’t undo the moving.
This feature seems to bring unwanted issues:
When I copy-paste a component from one file to another, the component behaves as a library component in the destination file — I can’t just edit it without detaching, but can “Go to main component in library” — even though none of the files are published as a library.
I would understand this “feature” to act as a lite version of a full-scale library, but if I change the “master” component in the first file, it doesn’t get updated in the destination file. So, unless it’s a bug, what’s the point of this behaviour?
It’s buggy on my side too