If you've been using Visily to design websites, prototype applications, or collaborate on interface concepts, there's an important deadline approaching.
Visily will shut down on October 31, 2026. The company has also announced that stored user data will be permanently deleted on November 30, 2026.
That gives existing users a limited window to preserve their work.
The good news is that Visily provides several export options, including images, PDFs, code, Figma transfers, and access to assets through its MCP server.
But where should those designs go next?
The answer depends on whether you want to keep designing, hand your work to developers, or turn a website concept into something customers can actually visit.
Why is Visily shutting down?
In its October 3, 2026 announcement, Visily explained that the design-tool market had changed substantially and that the company had decided to discontinue the service.
The company confirmed two important dates:
October 31, 2026: Visily becomes unavailable.
November 30, 2026: Stored Visily user data is scheduled for permanent deletion.
Don't depend on the later deletion date as extra time to export. Save your work while Visily remains accessible.
Step 1: Identify the designs you need to preserve
Start by reviewing your Visily workspaces, boards, and projects.
For each project, consider preserving the following:
- Complete screens and wireframes
- Design assets, icons, and images
- Important colors, typography, and component specifications
- Page navigation and user-flow diagrams
- Interactive behavior that a static export may not capture
- Designs for client projects or ongoing development work
If a project belongs to a client or team, confirm ownership and access before exporting.
Where possible, save both an editable representation and a static visual reference.
Step 2: Export your Visily designs
Visily supports multiple export formats, each intended for a different purpose.
Option A: Export images or PDFs
This is the most straightforward way to preserve how a design looks.
Open your Visily board, select Export, and choose the image/PDF option.
You can export individual screens, sections, or the entire board.
Image formats include PNG, JPG, and WebP.
These files are useful for documentation, sharing with clients, and providing visual references while rebuilding a website.
However, exported images do not preserve an editable website or working application.
See the official image export guide and PDF export guide. Free-plan exports are limited to 1× scale; paid plans offer higher resolution and exports without watermarks.
Option B: Move designs to Figma
If your priority is to continue interface design and team collaboration, Figma is a logical destination.
Visily provides a Figma integration supporting the transfer of designs into editable Figma elements.
According to Visily's documentation, this functionality requires an eligible paid workspace.
Review the official Visily-to-Figma instructions before the shutdown.
Option C: Export your designs as code
Visily also supports exporting screens as HTML, React, or Vue development files.
This can be valuable if you intend to turn your interface designs into an actual website or application.
The code export feature requires a Pro or Business workspace. Visily documents that only screens, not every arbitrary design-board element, can be exported as code.
Select Export, then Export to Code, choose HTML, React, or Vue, pick your layout mode and screens, and download the ZIP. Visily supports up to ten screens per export. AI layout uses 15 AI credits per screen; static layout does not use AI credits. The ZIP includes development files and a README.
You may still need to adjust responsive behavior, fonts, styling, and application logic.
See the Visily code export guide.
Option D: Retrieve assets through the Visily MCP server
Visily's shutdown announcement also identifies its MCP server as an option for retrieving assets.
The official MCP guide requires a Pro or Business workspace and a workspace creator or editor license. Access follows your existing permissions. Use downloaded exports as your durable backup; an MCP connection is not an offline archive.
Step 3: Decide what you're trying to build next
This is where the migration paths diverge.
If your goal is to continue designing interfaces and collaborating on prototypes, choose a dedicated design tool such as Figma.
If your goal is to develop a complex interactive application, use the exported code as a starting point in an appropriate development environment.
But if your designs represent a marketing site, landing page, portfolio, or small business website, you may not need to start with another design tool.
You may be ready to build the actual website.
From Visily design to a live WordPress website
SiteKick CMS is an AI-assisted website builder based on WordPress.
It offers a different workflow from Visily.
Instead of focusing primarily on wireframes and UI prototypes, SiteKick focuses on creating, editing, publishing, and managing business websites.
For an existing Visily website concept, a practical workflow is:
1. Preserve your visual references. Export important screens and assets from Visily before the shutdown.
2. Write a website brief. Describe your business, intended visitors, desired pages, branding, and the purpose of the website.
3. Create a draft website. Start from your business brief and create suitable pages and initial copy with SiteKick CMS. Review the current plan and editor workflow before committing to a rebuild.
4. Refine the design. Use the visual editor to adjust layouts, images, copy, and styling while comparing against your Visily references.
5. Test before publishing. Verify navigation, mobile layouts, forms, content, and SEO settings.
6. Publish when ready. Connect your domain and manage future website updates through WordPress.
This is a reconstruction workflow, not a guaranteed pixel-perfect conversion.
SiteKick CMS does not currently advertise a verified one-click Visily import or direct conversion of Visily's React/Vue files into editable WordPress pages.
Should you choose Figma or SiteKick after Visily?
The tools serve different purposes.
| Your objective | Better starting point |
|---|---|
| Continue wireframing and UI design | Figma or another design tool |
| Preserve an existing visual concept | Visily image, PDF, or Figma exports |
| Develop a custom web application | A development environment supporting the exported code |
| Launch a business or marketing website | SiteKick CMS |
| Manage WordPress pages and blog content | SiteKick CMS |
You may also use both a design tool and SiteKick, depending on your workflow.
The important distinction is between designing an experience and operating a live website.
Frequently asked questions
When is Visily shutting down?
Visily has announced October 31, 2026, as the service shutdown date. Its stored user data is scheduled for deletion on November 30, 2026. Export before the service closes.
Can I export Visily designs to Figma?
Yes. Visily documents a Figma export and import workflow that transfers designs into editable elements, subject to eligible paid-plan requirements.
Can I download HTML from Visily?
Visily supports exporting screens as HTML, React, or Vue code on qualifying paid plans. Exported code is a development starting point and may require additional work before deployment.
Can SiteKick import Visily designs automatically?
Not as a currently verified, built-in integration. You can use Visily screenshots, content, and other exported assets to guide the creation of a new website in SiteKick CMS.
Is SiteKick a Visily replacement?
SiteKick is an alternative for people whose end goal is to build and publish a website. It is not a direct replacement for Visily's dedicated collaborative wireframing, interface-design, and prototyping features.
What if I want to build a custom application?
Preserve your editable designs and code exports, then evaluate a development platform that supports your intended application architecture. A WordPress website builder may not be appropriate for complex application workflows.
Don't let your website idea disappear with Visily
Losing access to a design platform doesn't mean losing the work you've invested in your project.
Export your designs, preserve the important details, and decide whether your next step is more prototyping or launching the website itself.
If you're ready to turn a business website concept into something you can publish and manage, explore SiteKick CMS.
Build with AI, adjust your design visually, and manage the result through WordPress, while retaining ownership of your website assets.
SiteKick is an independent product and is not affiliated with or endorsed by Visily. Feature support and migration compatibility depend on the original project and chosen export format.
