Articles on: Getting started

Request a managed WordPress migration

FlyingHost offers free managed WordPress migrations. You can request a move from your current host, test the copy on FlyingHost, and coordinate when your domain starts sending visitors to the new site.


Submit a migration request


  1. In FlyingHost Cockpit, select the organization that should own the site. Choose Migrate a site, or Request migration if the organization has no sites yet. Ask an organization admin to submit the request if you lack access.
  2. Enter the site name, select a destination region, and provide the requested WordPress access in the migration form.
  3. Choose how DNS will be handled. To have FlyingHost make the switch, you can invite migrations@flyinghost.com with DNS edit access at your provider. To manage the switch yourself, select Connect domain myself later.
  4. Pick a preferred date and time window, check the time zone shown, and submit the request. Use the notes field to flag stores, memberships, busy periods, or other requirements that affect the timing.


Request migration form showing the site name and destination region


Migration form showing the available DNS access options


Keep your existing hosting active until the new site has been tested and the domain switch is complete. Use the migration support ticket to coordinate access, timing, or changes to the plan.


Test the migrated copy


Open the temporary FlyingHost address when it’s ready. Check the homepage, key pages, images, WordPress admin, and any flows customers rely on, such as forms, logins, cart, and checkout. Use test settings where available. Tell the migration team if anything needs attention before DNS changes.


Switch the domain


If FlyingHost is handling DNS, coordinate the switch with the team in your migration ticket. If you’re managing DNS, open your live site in Cockpit, select Domains → Connect domain, and follow the DNS instructions. Keep existing email records in place.


If your site receives orders, registrations, or other submissions, agree on a plan for changes made after the initial copy. Ask the migration team whether a final sync or a short pause on new orders or submissions is needed, and verify recent records after the switch.


After DNS takes effect, check the live site over HTTPS and confirm the main customer flows work before closing your old hosting account.

Updated on: 12/11/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!