Skip to main content

What migration copies

Wigoh works from what a visitor can see. It captures the page, its images and its structure, then rebuilds it in WordPress with Elementor.

What is recreated​

  • The layout and design of the page: sections, columns, spacing, colours, typography and imagery, rebuilt as Elementor elements.
  • The text content of the page.
  • The images the page uses. They are copied into your WordPress media library.
  • The header and footer, including the navigation menu. Wigoh leaves one menu on the site.
  • Forms. Any form on the page is replaced with a CRM form connected to your account, so enquiries reach you. See Forms and leads for what changes in the process.

What is done differently on purpose​

  • Platform apps and widgets from the old platform (booking apps, store apps, chat bubbles that only exist on that platform) cannot be copied as they are. Their purpose is usually recreated with a WordPress equivalent, or the section is rebuilt without the third-party element.
  • Third-party form embeds whose fields cannot be read are replaced with a standard contact form (name, email, phone, message). The site's build report says so.
  • Scripts and tracking codes from the old site are not carried over. Add your analytics to the WordPress site afterwards.

What the build report tells you​

If a form had to be simplified, the limitations are recorded and shown in the build progress and in the editor's form tools. Each limitation is a plain sentence, for example "The original form had several steps. The CRM form shows every field on one page."

What migration does not promise​

  • A pixel-identical copy of every page on the first pass. The build runs a Quality Check step, and the editor is there for the rest.
  • Copying content that sits behind a login, in a members' area, or in an app that renders after interaction.
  • Moving your domain, email or DNS. Those happen separately, when you choose to go live.