-
How switching actually goes.
Worse than from most tools, and it is Wix’s architecture rather than anyone’s policy. There is nothing to import, so the route runs through Figma and you are rebuilding the pages.
Open the Figma file the design came from, or rebuild the pages there.
Send each frame across with the plugin.
Set the three breakpoints and the SEO fields.
Move the domain, then publish.
-
Read this before you cancel anything
There is no HTML or CSS export from Wix. Its own documentation states a site must run on Wix’s servers, so there is no file to bring across — not to Siter.io and not to anywhere else. Get whatever you can out first: CMS collections export as CSV, and take your own copies of images and copy while the site is still live.
Blog posts are the sharp edge. Wix states they cannot be exported to another platform at all. If the site has years of posts on it, that is an argument for staying, or for accepting that the archive ends where the move begins.
If the domain came free with the Wix plan, it is registered somewhere and needs moving or repointing before the subscription lapses. Check Wix’s own transfer documentation first, then point it at Siter.io. Keep the Wix plan alive until the new site is published and the domain resolves.
What comes across from Figma is text, images, vectors, groups and auto-layout structure, as editable elements rather than a flattened picture. Prototype animations and interactions do not import, and there is no re-sync, so later Figma edits do not flow through.