Best Practices for Updating Figma Projects with Relume Kit

·Sep 04, 2025 09:36 PM·

Share

Hey there, I have a quick question about the Figma Kit. Is there a recommended procedure for updating an existing project in Figma to use the latest version of the Relume Figma Kit? I have an old project that uses an outdated version of the kit, and I would like to update it to access the new components. I know I can simply copy and paste everything, but that won't sync with my existing design library. Another option would be to migrate the project to the newest version of the kit and recreating my design library on this Figma file, but that seems like an awkward solution since updates are somewhat frequent.

1 comment

· Sorted by Oldest

Matt J.
·
·
Mathieu B. totally understand the pain point you are speaking about here. This message is actually really timely because I would really love to resurface this idea back up to the team to see if we can't prioritize it - but unfortunately the answer I have for you is the one you mentioned in the second part of your message - recreating your style guide in a newer version. Now it depends on how old your current version is. If its before variables, then yeah copying/pasting components in will not have variables attached - but if its after we've added variables - you'd still need to apply some of your custom colors to your wireframes when you bring it in, but it would actually have all the "vanilla" variables assigned so it wouldn't be much of a stretch to do. From my experience, there are some big version jumps where I'll convert an existing long-term project over and it sucks to have to redo this work just to stay up-to-date, but even with our frequent component releases - you may only end up using 3-5 of the new components, so you'd just copy/paste those in, they'd have the variables necessary, and then you'd design them out in your project and you are good to go. Hope that makes sense for now. The bigger project is having the Figma plugin actually just say "Hey grab all of the newly released components that I do not have yet, and dump them into my file please" - with a click of a button - that sure would be nice huh!

Matt J.
·
·
Mathieu B. totally understand the pain point you are speaking about here. This message is actually really timely because I would really love to resurface this idea back up to the team to see if we can't prioritize it - but unfortunately the answer I have for you is the one you mentioned in the second part of your message - recreating your style guide in a newer version. Now it depends on how old your current version is. If its before variables, then yeah copying/pasting components in will not have variables attached - but if its after we've added variables - you'd still need to apply some of your custom colors to your wireframes when you bring it in, but it would actually have all the "vanilla" variables assigned so it wouldn't be much of a stretch to do. From my experience, there are some big version jumps where I'll convert an existing long-term project over and it sucks to have to redo this work just to stay up-to-date, but even with our frequent component releases - you may only end up using 3-5 of the new components, so you'd just copy/paste those in, they'd have the variables necessary, and then you'd design them out in your project and you are good to go. Hope that makes sense for now. The bigger project is having the Figma plugin actually just say "Hey grab all of the newly released components that I do not have yet, and dump them into my file please" - with a click of a button - that sure would be nice huh!