If pages pulled from Figma keep landing in the wrong Frontitude project, and there's no way to move them once they're there, this is usually caused by how the Figma file was created rather than anything wrong with your workspace or account.
Why this happens
A Frontitude project is directly connected to a specific Figma file. That connection can break in one common scenario: when a Figma file is duplicated from another file.
When a file is duplicated, the new file can remain connected to the original file's Frontitude project. As a result, frames synced from the duplicated file continue syncing into the original project, even though you're working in what looks like a separate file. There's currently no option in the plugin to manually choose which project a file syncs to, which is why this can be confusing to spot.
How to fix it
To break the incorrect connection and let Frontitude create a fresh project for the duplicated file:
- Open the duplicated Figma file.
- Launch the Frontitude plugin.
- Go to Settings.
- Click Disconnect. This removes the link between the duplicated file and the original Frontitude project.
A new Frontitude project will be created automatically the next time you sync the file.
Removing the orphan project
Once the file is disconnected, the original Frontitude project it was mistakenly syncing into is no longer linked to any Figma file. If you don't need to keep it, you can delete it directly from the web app: open the project, go to Settings, and select Delete project.
Moving content that already synced to the wrong project
Disconnecting only prevents new syncs from going to the wrong project going forward. It doesn't move pages that have already synced there, since there's no built-in way to move pages between projects. If you need existing content relocated, reach out to support@frontitude.com and our team can help.
