How to Move from WordPress to Figment

To move a WordPress site to Figment, export the content, save the media, and keep a full backup where you can. Then rebuild the pages in Figma, publish a test site with Figment, check every important URL and function, and change DNS. This is a rebuild, not a one-click import or a perfect copy. WordPress's content export does not include the theme, its customizations, or the image files. Figment publishes Figma designs, so your WordPress theme and plugins do not become part of the new site.

If your main product is a large blog, a WooCommerce store, or a site that depends on member accounts or plugins, decide how those functions will work before you move the domain. Keep the live WordPress site in place while you test Figment on its preview address. If some WordPress functions must remain live after the switch, give them a separate domain or tested routing before you change DNS.

1. Save three different things

These files have different jobs. Do not treat one as a substitute for the others.

WordPress calls its XML format WordPress eXtended RSS (WXR). Its self-hosted export guide lists the content types in that file. WordPress.com explains that media appears as links in the XML, not as the uploaded files. The WordPress.org import guide also treats attachment download as a separate import step. A full self-hosted backup needs site files and a database export.

On WordPress.com: Open Tools > Export, choose All content, and download the XML file. For a large site, WordPress.com may send a ZIP with several XML files. Then use its media export guide to download the files. The media steps depend on your plan and whether plugins are installed. If your site has an eligible Business or Commerce plan, download a site backup too. Other plans have content and media exports, but not that downloadable full-backup feature.

On self-hosted WordPress: Open Tools > Export and download All content. Also copy your uploaded files, usually under wp-content/uploads, and make a current backup of the files and database through your host or backup system. WordPress's export screen and backup handbook cover these as separate tasks. Check that each archive opens before you change the live site.

Keep the original WordPress site accessible while you work. Save the site address, page list, navigation, screenshots at desktop and mobile sizes, image originals, page titles, and descriptions. Treat WXR as a content record for this project, not as a Figment import command.

2. Make a URL and redirect plan

List each important old URL next to its intended new URL. Include pages, posts, category and tag archives, downloads, and links from email campaigns. Check the actual URLs; do not guess them from page titles. On self-hosted WordPress, Settings > Permalinks shows the post URL pattern and archive bases. WordPress documents the available structures.

Keep the same path when the new site can serve it. For every path that must change, choose a relevant new page and arrange a permanent redirect at the host or proxy that will answer requests after the DNS switch. Test the redirect before you retire the old site. A redirect plugin on the old WordPress host alone is not a plan for requests that will go to a different host after DNS changes. If you cannot preserve or redirect valuable paths, do not move those pages yet.

There is one separate case for WordPress.com addresses. If readers use example.wordpress.com, WordPress.com offers a paid site redirect for that address. Its guide says that matching destination paths matter, and that the feature is not available on plugin-enabled sites. This is not the same as moving a custom domain. Check those limits before you buy it.

3. Rebuild and test the new site

Use the saved content and media to make Figma frames for each page you will move. Make desktop and mobile layouts. Add working navigation and links. Then publish with the Figment plugin to a .figment.so address and review the live result. Figment's guide documents the preview address and custom-domain publishing on its paid plan. Do not expect the XML file to recreate a WordPress theme or copy a layout without work.

Audit functions as well as pages. Make a list of every contact form, newsletter signup, search box, comment area, login, booking tool, tracking script, and plugin integration. Record who receives the data and where old submissions are stored. If you use WordPress.com forms, export the responses as CSV. For other form plugins, follow that plugin's export instructions. Replace each function with a tested service or keep that function on WordPress. Send a test submission and confirm delivery before you change DNS.

Treat commerce as a separate migration. WooCommerce has a built-in product CSV export, but a product list is not a tested checkout, order history, customer account system, or subscription workflow. Keep the live site on WordPress until you have selected and tested a replacement for payments, orders, taxes, shipping, and customer support. If you will keep the store on WordPress after the main-domain switch, test its separate address and links first. Do not direct buyers to an untested checkout.

4. Change DNS, then keep a way back

Find the registrar and the DNS provider before the switch. A domain registered with WordPress.com does not have to transfer to another registrar just to point at a new site; WordPress.com lists pointing a domain elsewhere as a separate option. Add the domain in Figment, then use the exact DNS values shown for your site. Save the old web records first. Preserve mail and verification records, such as MX and TXT. WordPress.com's DNS guide explains that DNS controls both web and email service and that changes can take up to 72 hours to reach all visitors.

Check both the root domain and www, HTTPS, key pages, images, forms, and every planned redirect from more than one network. Keep the WordPress hosting and your backup in place during this check. If the new site fails, restore the saved web DNS records and keep the WordPress site available. DNS caches can make the return gradual too. If you changed or deleted WordPress data, use the full backup to restore it; changing DNS alone will not restore data.

Do not cancel the WordPress plan, hosting, or domain while you still need it for redirects, email, or rollback. In particular, do not cancel a WordPress.com domain registration that you want to keep. Cancel only the services you no longer need after the new pages and required functions pass your checks.

Final check

• WXR export, media copy, and available full backup saved and opened.
• Old URLs mapped to new pages or tested redirects.
• Figma pages published and checked on desktop and mobile.
• Forms, integrations, and any commerce flow tested separately.
• Existing DNS records saved; email records preserved.
• Both domain forms, HTTPS, and key pages checked after the switch.
• WordPress kept available until the rollback window is over.