Explain the business
Give Frontpage your services or products, location, hours and the action visitors should take.
Use case · Alternatives
Keep the menu, the services and the details customers need. Build and revise by conversation, with a clear plan for the Wix features you use today.
Start with one real task. Check the result before switching.
What Frontpage does
A bakery needs a clear menu, current hours and a way to order. A service business needs the offer, the service area and a way to get in touch. Frontpage builds those pages from your brief, then helps you keep the details current.
Wix also offers conversational AI editing and a broad set of business tools. If you are considering a move, compare the workflow and the features you actually use. The goal is a site you can maintain, with the important parts still working.
Give Frontpage your services or products, location, hours and the action visitors should take.
Bring approved descriptions, photos and page paths. Name anything that must not change.
List ordering, bookings, forms and apps separately. A rebuilt page does not migrate the data inside them.
Ask for a menu update or a clearer service page. Review the preview before publishing.
Side by side
The problem
Before you switch, separate the website from the business systems attached to it. A menu page is content. A live ordering system also has products, payments and order history. They need different checks. Keep the current site working while you review the replacement.
List every Wix app and the job it does. Mark the ones customers use to pay, book or contact you.
Copying a page does not transfer orders, bookings or subscribers. Make a separate plan for records and ongoing activity.
Keep descriptions and URLs that already answer customer questions. A new builder is not a reason to discard them.
Wix documents free native forms. Compare the limits and features you need rather than assuming every form requires a paid app.
How to switch
Write down the pages to keep, the apps behind them, and the records you need to retain or export.
Ask for the new site using your approved content. Check navigation, form destinations, payment or ordering paths and phone layouts.
Publish the ready site, check old paths and add redirects where needed. Keep access to the old records. See the moving guide.
Before you switch
For each item, decide whether it moves as content, needs setup or stays in an existing service.
Home, menu or services, about and contact. Include any article or product page people already link to.
Fields, destination, confirmation message and the records you need to keep.
Products, checkout, fulfillment and order history. Check each part of a replacement workflow.
Decide whether to keep the current scheduler or set up a different appointment path.
Keep existing records and consent information. A visual rebuild does not transfer subscriber permission.
Check the website destination and existing email DNS records before making changes.
The working process
Give every page and business tool a clear place in the plan.
Start with your menu or services, location, hours, photos and preferred next step. Supply prices you want kept exact.
For a bakery, try menu → product detail → ordering link. For a service business, try service → quote request.
Keep an existing external booking or ordering destination when that is the right choice. Verify any built-in replacement before launch.
Review the pages, links and forms while the current site stays online. Switch only when the new version is ready.
Score the Wix URL
Use a website audit to identify issues worth addressing in the rebuild. Keep it alongside your own app and customer-journey checklist.
After launch
After launch, analytics can show where visitors stop. On every plan, Growth Advisor suggests changes for review. Automatic testing through Autopilot is a separate choice.
How Growth Advisor works →
Search basics
Keep the pages that answer real customer questions. Review their titles and descriptions, preserve useful paths and check redirects after the move. SEO tools help with those details.
See it in action
An illustrative conversation for a fictional bakery, not a migration record.
The example keeps an external ordering service. It does not imply that Wix apps, orders or customer data transferred.
Why switch
The right move should make the site easier for your team to run.
Content
New hours or a new service should be a clear request. Supply the exact details and check the finished preview.
Design
Wix allows design edits. Its classic template replacement process can involve a new site. Frontpage lets you request a restyle in conversation, with a draft to review.
The fit
If the team is happy in Wix and relies on its apps, there may be little reason to move. If maintaining the site is the hard part, try the conversation workflow against one real task.
Questions
No. Plan a website rebuild and review each app, integration and data set separately. Do not assume orders, bookings, subscribers or permissions moved because the new pages look right.
No. Wix documents free native forms, with limits and paid features. Check its current form limits when comparing your requirements.
You can ask Frontpage to link to an existing external service. Check the actual link and customer flow. A link is not a data integration.
Review page paths, navigation, forms, phone links, payment or booking destinations and mobile layouts. Keep a record of existing DNS settings, including email.
A move alone does not establish an improvement. Preserve useful content and URLs, set redirects for moved pages and measure the result after launch.
Yes. Describe the change and review the new draft. Growth Advisor suggestions and automatic Autopilot tests have separate controls; see current plans.
Bring your content, page list and the business tools you need to keep. Frontpage builds the draft for you to review.
Review the preview. Check customer actions. Publish when ready.