Migrating to Figma

How to set up a workflow in Figma for small and large design teams

Being an intuitive and user-friendly tool and having the possibility of real-time collaboration are some of the main reasons people choose to use Figma. But the migration process to Figma may sometimes be painful or time-consuming. That’s probably why many design teams decide not to do it or postpone the migration to Figma.

In the past 2 years, I have had the opportunity to lead two migration processes from Sketch/Abstract/Zeplin to Figma. I have faced two different setups: the first one was at C6 Bank with more than 30 designers and the second one has been at Chama App, where currently our design team has 9 people.

In both cases, we have faced problems. Some were quite similar, but others were unexpected. Based on that, I would like to share with you some tips I learned in both cases that will definitely help your team in this migration process.

1. Make a Plan

You need to set a date to start and finish this process, create steps, and define your team’s priorities. There’s no use creating cover pages for projects in Figma if no one will ever understand how things are organized.

It’s about having a goal, not a cover page.