To move a WordPress site to Figment, export the content, save the media, keep a full backup, rebuild the pages in Figma, publish a test site with the Figment plugin, check every important URL and function, and then 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 as a hosted website, so your WordPress theme and plugins do not become part of the new site.
Forms, logins, stores, checkout, bookings, member accounts, comments and blog or CMS content do not move with the design. 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. Figment has no CMS. Keep the live WordPress site in place while you test the new site on its preview address. If some WordPress functions must stay live after the switch, give them a separate domain or tested routing before you change DNS.
What three things should I save first?
Save a content export, a media copy and a full backup. They have different jobs, so do not treat one as a substitute for the others.
| Keep | What it gives you | What it does not give you |
|---|---|---|
| WXR content export | An XML record of selected posts, pages, comments, categories, tags and other WordPress content. | Your theme, plugin code and the image files themselves. |
| Media copy | The uploaded images and other files you need to place in the new design. | The text, layout or working site. |
| Full backup | A recovery copy of the WordPress files and database. | A Figment site. It is for restoring WordPress if you need to go back. |
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.
How do I plan URLs and redirects?
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, and 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 is not a plan for requests that go to a different host after DNS changes. If you cannot preserve or redirect valuable paths, do not move those pages yet.
WordPress.com addresses are a separate case. If readers use example.wordpress.com, WordPress.com offers a paid site redirect for that address. Its guide says 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, so check those limits before you buy it.
How do I rebuild and test the new site?
Use the saved content and media to make one top-level Figma frame for each page you will move, homepage first, with working navigation and links. Do not make a desktop and a phone frame of the same page: each selected frame becomes a separate page, so check phone and desktop widths on the published site. Then publish with the Figment plugin to a figment.so address and review the live result. Do not expect the XML file to recreate a WordPress theme or copy a layout without work.
Audit functions as well as pages. List 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 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.
How do I change DNS and 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 to point at a new site; WordPress.com lists pointing a domain elsewhere as a separate option.
Connecting your own domain to Figment needs a paid plan: Pro is $49/month ($39/month billed yearly) with up to 10 custom domains, and Studio is $199/month ($159/month billed yearly) with up to 50. Pro and Studio start with a 30-day trial. See pricing.
- 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, because changing DNS alone will not restore data.
When can I cancel WordPress?
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.
What is the final checklist?
- 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.