From the lab

UX Review: Improving the Quote Journey for a Website Migration Service

A website migration is not a casual purchase. The visitor is thinking about pages, search rankings, forms, store content and the risk of disrupting a live site.

This short UX review looks at the route from the homepage to the quote form on Weebly-to-Wix.com. The service explains that it reviews the existing site, rebuilds it manually in Wix and gives a fixed quote before work starts. The question here is whether a visitor gets the information needed to send a useful request.

  1. 01 / LANDING PAGE
    Is this the right service?
  2. 02 / SERVICE EXPLANATION
    What is being moved?
  3. 03 / QUOTE EXPECTATIONS
    What affects price and timing?
  4. 04 / QUOTE REQUEST
    What should I send?

The review follows five places where a visitor may pause before contacting the service.

1. Make the scope easy to check

A website migration scope check covering content, ecommerce, forms and SEO

The page states that pages, images, blog content, SEO and launch support can be part of a migration. That is useful, but a site owner with a store, booking tool or custom form may still wonder whether their own setup is covered.

What to change: Put a short scope checklist near the main quote button. Include common items such as pages, blog, store, forms, menus and redirects. Add one plain note: unusual or complex features are reviewed before they are quoted. This answers the practical question without making promises before the site has been reviewed.

2. Explain how the quote is worked out

A website review turning pages, design, features and redirects into a tailored quote

The pricing section already names the main variables: number of pages, design complexity, content, functionality, redesign work, SEO and redirects. A list of variables is not quite the same as an expectation. A visitor may still have no idea whether their project is straightforward or involved.

What to change: Add a short explanation next to the list: small brochure sites, content-heavy sites and stores usually require different amounts of review and rebuild work. There is no need to publish a fake instant price. The point is to show how the site review leads to a fixed quote.

3. Tell people what helps before the form

Useful details to prepare before requesting a website migration quote

The form asks for the essentials, but some visitors will stop because they are unsure how much they need to prepare. They may not know whether a URL is enough, whether they should count pages, or whether they need to provide logins before asking a question.

What to change: Add a small panel above the form. Make the essentials clear: a website URL and a short migration goal. Then list optional details that help with the first reply: store or blog content, important functions, desired changes and a target launch date. Do not ask for credentials at this point.

4. Keep the quote form short

A short website migration quote request form and confirmation

A quote request needs enough context for a useful response, but it should not become a project questionnaire. Name, email, URL and a short description are a reasonable starting point.

What to change: Add no more than two optional choices: site type (business site, blog, store or other) and main priority (preserve the current design, refresh it, improve mobile or move quickly). Label them as optional. After submission, say exactly what happens next: the site is reviewed and the visitor receives a reply within the stated timeframe.

5. Put proof next to the action

Trust information beside a website migration quote request

Experience, client reviews and a documented process are already present on the site. They are most useful when a visitor is about to submit the form, not only when they are reading the top of the page.

What to change: Beside the quote button or form, repeat four specific facts: the existing site stays live during the rebuild; the quote is fixed after review; the visitor can review the completed site before handover; and the client speaks directly with the migration specialist. These are details a site owner can act on.

What we would improve first

  • Show a quick migration-scope checklist near the first quote call to action.
  • Explain, in one short paragraph, how project complexity affects the quote.
  • Tell visitors which details are required and which are optional before the form.
  • Keep qualification to a few optional fields.
  • Move the most relevant proof points closer to the form.

None of these changes require a new design. They make the existing quote journey easier to understand and give the service better information to respond to.