What a website-to-WordPress converter can and cannot move
Understand automatic conversion limits: public pages, content editing, animations, forms, ecommerce, private data and launch checks.
By AnythingTo · Updated
A website converter can rebuild visible pages and map content into a WordPress theme. It cannot infer every hidden database record, application rule or external integration from a public page. List the content and features you need on the new site, including anything visitors cannot see without signing in.
Public pages are not the whole application
AnythingTo works from public URLs, supplied files, Figma designs or screenshots. These sources contain different kinds of information. HTML may reveal links and text, a design file may contain layer names and layout, and a screenshot shows appearance without the underlying content relationships.
None of those inputs automatically supplies private customer data, order history, account permissions or an unpublished CMS database. Inventory those separately. Never upload credentials or personal customer records as a way to explain a visual conversion.
Check that your pages and collections are included
A standard website conversion currently looks for up to 30 ordinary pages and 12 items in each collection group. It follows the links it can find, so private or unlinked pages may be missed. Compare the result with your page list, especially on larger sites.
For Figma, we use up to 12 suitable page designs on the first page of the file. Screenshots show appearance but provide less information about how content should work. For a large catalogue or design file, list the pages you need before starting.
- Check both ordinary pages and repeated item pages.
- Look for unlinked landing pages and paginated content.
- Verify optional fields and items with unusual layouts.
- Keep a list of pages or records requiring another import route.
Separate appearance, editing and behavior
Check each area separately. A matching screenshot says little about whether an editor can add a new item or a form can deliver a message. Ask for a demonstration of each critical behavior rather than one overall percentage-complete claim.
| Area | What to review |
|---|---|
| Layout | Desktop and mobile appearance, fonts and image crops |
| Editing | Changing text and images, adding items and updating menus |
| Interactions | Menus, tabs, sliders, keyboard support and motion |
| Forms | Validation, delivery, spam handling and file uploads |
| Commerce | Products, payments, stock, orders and taxes |
| Private areas | Signing in, account access and private pages |
Plan for platform-specific gaps
Some Framer animations and hover effects need rebuilding, and complex Webflow animations need review. Wix pages may allow text and image changes while requiring help for larger layout changes. Check the page for your platform before deciding how to move.
Shopify products can come across with details such as prices, product codes and images. To continue selling, you will also need to set up checkout and payments, and plan what happens to existing orders, customer accounts and apps. The same distinction applies to booking systems and member areas on other platforms.
Decide what must work before launch
Write a short checklist for your site: required page count, editable content, important URLs, mobile layouts and essential visitor journeys. Name the features that may be simplified, and the ones that must be rebuilt. This makes the review practical for both a developer and a nontechnical site owner.
AnythingTo is in beta. Share your website, approximate page count and the content and services you rely on, then leave your email so we can follow up. Already have an account? Sign in to convert. It helps us assess the work without promising that every feature can move automatically.
Planning a conversion?
We’re in beta. Share your website and what you’d like to move, then leave your email so we can follow up. Already have an account? Sign in to start a conversion.