How to Move Your Weebly Site, Step by Step

You can rebuild Weebly's static pages in a Figma Design file and publish them with Figment. This is not a full site migration: forms, login, stores, checkout, and bookings do not transfer with the design. Keep any working services and DNS unchanged until replacements pass your checks. The steps below separate the page rebuild from the service checks and domain switch.

If your site is in one of the 67 countries Weebly is winding down, you're on a clock: sites were unpublished on September 27, 2026, and account access ends December 26, 2026. If it isn't, you can still move on your own schedule instead of Weebly's, which is the nicer way to do it. Since Square bought Weebly, the product has been in maintenance mode: no real feature work, an aging editor, and Square's attention on Square Online instead.

What do I need to export before I start?

Everything you can't recreate from memory: your copy, your images, and (if you run a store or take form submissions) your store and form data. Miss this step and the rest of the move doesn't matter.

Weebly's site archive (Settings → General → Archive in the site editor) gives you a zip of your regular pages as static HTML. It does not include blog or store pages — Weebly says so directly on its Back Up Your Site help page, since those are served from its database, not static files. So: download the archive for reference, then separately open each page and blog post and paste the copy into a doc, and save your images (originals where you have them, straight off the live site where you don't). If you sell through Weebly, export your item CSV from Items → Site Items → "…" → Export, documented here. The full export walkthrough, including blog posts and form entries, is here if you want the long version.

Note where your domain is registered too. If you bought it through Weebly and your site is in one of the 67 affected countries, transfer it to another registrar before December 26, 2026 — after that date Weebly's notice says you lose login access to the account you'd renew it from. The steps are in the domain guide.

How do I rebuild the design in Figma?

Your new static pages start in a Figma Design file in Figma. This does not recreate Weebly's backend services. Two routes from here.

Keep your current look. Screenshot every page (desktop and mobile) and recreate the layout in Figma. Most Weebly sites are a handful of straightforward sections, so this goes fast — the screenshots are your reference, not something you trace pixel-for-pixel.

Or take the upgrade. Grab a modern free template — the Figma Community has plenty, or see templates worth actually using — drop your saved copy and images in, and come out ahead of anything Weebly's theme library ever let you build.

Either way, make a desktop frame and a mobile frame for each page. Figment reads both when you publish.

How do I publish and switch over?

Before you publish, run your file past the Figma-to-website checklist — frame naming and mobile frames are the two things Weebly rebuilds skip most. Then install the Figment plugin in Figma, select your frames, publish. You get a live URL immediately on a free .figment.so address, so you can check every page before you touch anything at your registrar.

Before you change DNS, list every form, login area, store, checkout, and booking flow on the old site. A page that looks correct does not prove these functions work. Choose and configure a replacement service for each required function. Link to its working hosted page where appropriate; a copied form or button alone is not a replacement. Use the forms, bookings, and checkout compatibility checklist to record what stays with another provider.

Test each replacement from the new preview: send a test form and check delivery, check login and access controls, test a booking in the provider's test mode, and use the store provider's test checkout to check orders and confirmations. Confirm that saved customer, product, and submission data is available where needed. If a required function fails, do not switch DNS. Keep the existing service available if it still works; an already unpublished Weebly site is not a working fallback.

Connecting your own domain requires a paid plugin plan. Before the switch, save the current DNS records and a rollback plan with a working destination. Preserve email MX and TXT records. Change only the website records required by the new host after the replacement checks pass. Then check the domain, HTTPS, page links, email, and each replacement service again through the public domain.

Do not cancel Weebly just because the new pages load. First confirm that no required service, data access, domain renewal, or rollback step still depends on that account. Keep the account or dependent service until you have removed those dependencies, subject to Weebly's shutdown deadlines. Keep your archive and exports in storage you control.

The move, as a checklist

Run through this before you repoint DNS:

• Site archive downloaded (Settings → General → Archive)
• Copy saved from every page and blog post
• Images saved (including blog and store images, which the archive skips)
• Store CSV exported, if applicable
• Form entries exported, if applicable
• Domain registrar and renewal date confirmed
• Forms, login, store, checkout, and booking dependencies recorded
• Required replacement services configured and tested, including delivery and confirmations
• Desktop and mobile Figma frames built for every page
• Figment plugin installed, site published to a .figment.so URL, every page checked
• Paid plugin plan confirmed if connecting your own domain
• Current DNS saved, email MX/TXT records preserved, working rollback destination checked

After all required checks pass, change the website DNS records. Then complete these checks:

• Public domain and HTTPS work after DNS propagation
• Page links, forms, login, store, checkout, bookings, and email rechecked on the public domain
• No required service, data access, domain renewal, or rollback step depends on Weebly before cancellation

Why Figment and not another builder?

Figment can publish a static page design from a Figma Design file. Choose it when that fits your site and you have separate services for any functions that need a backend. It is not a replacement for Weebly's complete store or account system.

The AI editor offers a different starting point: preview a separate static copy of a public page you own or have permission to copy. It does not edit the original Weebly site or use a Figma file as its foundation. Import and private preview are free to start. You can use your own AI with manual file return or optional paid Figment AI; the migration limits above still apply.

Questions mid-move? We're on Discord.

If your country is in the shutdown, read the deadline post first — it's time sensitive. Need a hand before the deadline? Book a demo.