Penpot's Figma migration guide gets a practical refresh

Penpot published a step-by-step guide for actually moving projects and team habits from Figma over — account setup, file migration, customisation. It's aimed at teams doing this for real, not just kicking the tyres.

Penpot's blog walks through the practical mechanics of switching: creating an account, migrating projects, and customising the workspace. The pitch is enhanced dev handoff, open-source flexibility and no licensing fees — but the post is honest that change is still work, even when the tool is browser-based and OS-agnostic. For a junior designer on Figma and Penpot already, this matters less as "which tool wins" and more as a chance to build fluency in both. Recruiters increasingly like seeing you're not locked into one ecosystem, especially with open-source tooling gaining ground in some UK studios and agencies watching licensing costs. Adoption, not hype: this is a practical migration guide for teams already committed, not a speculative pitch.

Related in Design tools

Adoption

Figma's AI features are now core product, not a beta toy

Figma's product pages now list AI workflows, Figma Make, and Motion as standard parts of the toolkit rather than side experiments. That's a shift from 'try this AI thing' to 'this is how Figma works now'.

figma.com7 May

Adoption

Penpot's open-source pitch is maturing, not just noise

Penpot keeps getting pitched as the open-source Figma alternative — built on SVG/CSS, self-hostable, no vendor lock-in. It's real and improving, but it's adoption-stage, not a mass switch yet.

medium.com12 Aug

Adoption

Penpot hype cooled — most teams are still on Figma

A r/web_design thread notes the Penpot-vs-Figma buzz spiked when the Adobe acquisition talks were live, then faded once the deal collapsed. Real migrations are still rare, even among people curious enough to try it.

reddit.com15 Aug