Migrations - Kinsta Migration - Kinsta® Docs (original) (raw)

When migrating your site to Kinsta, you have a few options to choose from, starting with migrating the site yourself or having our team do the migration for you.

Kinsta migrations are free. You can choose to migrate your site straight away, schedule the migration if your site is continuously updated or has special requirements, or purchase an expedited migration.

If you’d like to migrate your site yourself, we have several resources to help guide you:

If you’d like us to migrate your site for you, we’ve outlined some important notes and the steps to follow below. If you have a large number of WordPress sites you’d like us to migrate, you can contact our support team to perform a bulk migration.

Expedited migrations

If you’re concerned about downtime or need to get your site live on Kinsta quickly, we offer expedited migrations for just $49 per site. Agency plans come with free expedited migration credits, with the number of credits depending on the number of sites in your plan. To check your available credits, navigate to MyKinsta > your username > Company settings > My Plan > Expedited migrations.

With expedited migrations, our goal is to complete the process within 8 hours, between 9 AM and 11 PM, Monday to Friday (UTC). If we don’t meet this 8-hour target, we’ll refund your migration fee. While we strive to work as quickly as possible, certain factors, such as complex site requirements, slow transfer speeds from your current provider, or sites larger than 10GB may extend the migration time. If we anticipate that the migration will take longer than 8 hours, we will keep you updated throughout the process.

You can choose the expedited migration option when you request the migration in MyKinsta.

Migration process and checklist

Make sure you have an open spot for the new site we’ll create for your migration.
If you’re requesting a migration from a backup:
1. Make sure the backup contains both your website files and database.
2. Have the backup ready to upload or have the link to the files.
Only Company Owners or Company Administrators can submit a migration request in MyKinsta.
You can check the status of your migration(s) by going to the Migrations tab in MyKinsta. Our Migrations team will also keep you updated on the status of your migration.
Once your migration is complete, we’ll let you know and send more information on how to test your new site at Kinsta before making it live.

Important notes

If your site uses WP Engine’s LargeFS feature, a reverse proxy, or other complex requirements, please let us know in the Special instructions when you request the migration.
Sites that change continuously (ecommerce sites, membership sites, etc.) often require placing them into maintenance mode and careful scheduling to avoid data loss.
For some hosts, if two-factor authentication (2FA) is enabled, we recommend adding us to your account at your current host with this email address: [email protected] and giving us the necessary access (as noted in the request form). This currently applies to migrations from Cloudways, GoDaddy, SiteGround, or WP Engine.
Once the migration is complete, we’ll send you details for testing the site and how to point your website to Kinsta if everything looks good. Please always wait until we have confirmed that the migration is complete and that you’ve fully tested the migrated site before updating the DNS.
Please refrain from making any changes to your site during the migration to ensure any updates aren’t left behind on your previous host. If there’s a delay between the migration and taking the site live, a second migration may be needed for any updates.
Setting up DNS and configuring third-party services is not included in our migration service, and you will need to handle these tasks. A few common examples of tasks that you will need to take care of include: updating your domain’s A records or other DNS, pointing name servers to Kinsta’s DNS, setting up a third-party CDN (like Cloudflare or Sucuri), or setting up an email service.
If you want to migrate a WordPress multisite network, you must migrate the multisite network as a whole. The Kinsta migrations team cannot migrate a single sub-site of a multisite network into a standalone site; to do this, we recommend working with a developer.

Migrating WordPress.com sites

For WordPress.com migrations, we cannot do a traditional migration because WordPress.com does not allow access to the site files or the database. We can only export your WordPress content, such as posts, pages, comments, meta tags, etc., and import the content into a new WordPress installation here at Kinsta.

Because we cannot access the site files, we cannot bring over your WordPress theme, plugins, or any other customizations that may have been made to the site. This means your site will not look the same as it does at WordPress.com, and any functionality dependent on a plugin will not work until you re-install your site’s plugins.

After the migration, you or your web developer will need to re-install the theme and plugins and recreate any customizations that you made at WordPress.com (if applicable).

Saving and continuing your migration request

While working on your migration request, if you need to stop and come back to it later, we’ve got you covered. Your request is automatically saved as a Draft if you leave the form and go to another part of MyKinsta in the same tab, if you close the tab in your browser, or even if you close the browser.

You can view all of your migration requests on the WordPress Sites page in the Migration requests table. If the migration request hasn’t been submitted, it will have a status of draft. You can click on the name to continue filling in the necessary information and submit the request.

If a migration request is pending, you can click on the name to view the migration details page, where you can track the migration’s progress.

Click on a migration request name to continue editing or view the migration details page.

Request a migration

To start a migration in MyKinsta, log in and go to WordPress Sites > Request migration. If you haven’t yet added any sites, you’ll see two buttons instead of a list of sites on the WordPress Sites page instead of a list of sites. Click Request a migration to start your migration request.

Select Request migration on the WordPress Sites page in MyKinsta.

You must choose when you would like Kinsta to perform the migration from the following options:

As soon as possible: Migrations are usually completed within one business day. If you select this option, our Migrations team will check all of the information you’ve provided and notify you before the migration starts.
On a specific date: Our Migrations team will start the migration on the date and time you have requested. The timings depend upon receiving the correct information to complete the migration. If we’re unable to access the site or backup for the migration, that may delay the migration, depending on how long it takes to get the necessary information.
Expedited migration: You can purchase an expedited migration for $49. The migrations team aims to complete the migration within 8 hours, between 9 AM and 11 PM Monday to Friday UTC. For example, if you submit the request at 10 PM on Thursday, we aim to complete the migration by 4 PM on Friday. If we miss the 8-hour goal, we will refund the migration fee. We try to do our best to be as fast as we can, but sites with complex requirements, slow transfer speeds from your existing provider, or sites above 10GB may increase the time it takes to complete the migration.

Once you have selected your timeframe, read through the introduction, and click Next to acknowledge you’ve read and understood the information presented and that you’re ready to continue with the migration request.

Choose your timeframe and read through the migration request introduction and conditions.

There are then two types of migrations to choose from:

Request a Migration From Another Host: Share information about your current hosting provider so the Migration team can access the site to perform the transfer.
Request a Migration From a Backup: Provide a link to files using cloud storage services such as Drive, Dropbox, etc., or upload a backup file (whether it’s created with Duplicator, ManageWP, or cPanel) to an existing Kinsta website.

Request a migration from another host

Choose Migrate from another host and click Next to continue.

Request a migration from another host in MyKinsta.

There’s some information you’ll need to have ready to complete the migration request:

Details of your current host
Details of your site setup
Connection details

1. Source details

On the next page, we’ll ask for your current hosting details. For some managed hosts, this includes your host’s name, username, password, and SFTP connection details.

Depending on your current host, we may request additional details like hosting panel credentials. Typically, you can find these details on your current hosting provider’s control panel. If you’re unsure of these details, reach out to your current host or ask a member of the Kinsta Support team for help.

If you’re using cPanel, for example, your username and server details are listed in your User Area > My Accounts > Information & Settings page. FTP information can be found under Files > FTP Accounts.

Add your source details to your migration request.

After entering your host information, click Next to proceed to the next step in the request.

2. Site details

Next, we’ll ask for your domain, WordPress credentials, and WordPress admin URL, as well as whether your site is a Bedrock/Trellis site, e-commerce, community, or membership site, if it’s a multisite, and if it uses HTTPS.

Complete the site details in your migration request.

Domain name of site to transfer: This is the domain you want to use to access your site.
Add domain with wildcard: A wildcard domain ensures that any requests to a subdomain of *.domain.com resolve to the same IP address as your main domain. For example, if you have a wildcard DNS record for *.example.com pointing to 123.123.123.123, any requests to sub.example.com or blog.example.com will be resolved to 123.123.123.123.
WordPress username: Your WordPress username.
WordPress password: Your WordPress password.
WordPress admin URL: The URL you use to access WP Admin.
Bedrock, Trellis: Select this option if your site uses the Bedrock or Trellis configuration and enter the Root path where the WordPress application is installed.
Is it an e-commerce, community, or membership site?: These sites usually change continuously; therefore, we recommend putting them into maintenance mode to prevent data loss when migrating. If you select this option, you can select the option to Use maintenance mode. Placing a site in maintenance mode means that the site content cannot be updated. While the site is in maintenance mode, a maintenance message is displayed, orders cannot be placed, users cannot register or edit their profiles, and new content cannot be published on the site. For more information about this process, refer to How Kinsta Migrates Dynamic WordPress Sites.
Is it a multisite installation?: If you have a multisite, select this option and choose if your site is a subdirectory or subdomain. You must migrate the multisite network as a whole. The Kinsta migrations team cannot migrate a single sub-site of a multisite network into a standalone site.
Does your site use HTTPS?: If you select this option, you can choose to generate a new SSL certificate in MyKinsta (using our free Cloudflare integration) or upload an existing certificate (if you have the key and certificate file).

After entering your site details, click Next to continue.

3. Kinsta settings

You now need to complete the details for your site’s new home at Kinsta. Enter a unique name and choose your site’s data center from the 37 data center locations available.

Let us know if there’s any special information or instructions we should know about for your site, such as forcing HTTPS or any special .htaccess or Nginx rules that you may need. You should also let us know if your site is a WordPress.com site, if it uses WP Engine’s Large FS feature, if it requires a reverse proxy, or if it has any other complex requirements.

Add your Kinsta site details to your migration request.

Once you’ve completed your Kinsta settings, click Next to review your migration details.

4. Review and submit

Carefully review the details of your request for any typos or errors. If you have requested an expedited migration, ensure the correct payment method is selected. If you need to change anything in the request, click the Back button to return to the previous page and update the information.

Review and submit your migration from another host.

When you’re ready, click Finish to submit your request.

Your pending migrations will show up under WordPress Sites in MyKinsta, and you can check the status anytime. Our Migrations team will also keep you updated on the status.

View migration requests on your WordPress Sites page in MyKinsta.

If you have any additional migrations to submit, click Request migration to begin a new migration request.

Request a migration from a backup

Choose Migrate from backup and click Next to continue.

Request a migration from a backup.

1. Source details

On the next page, we’ll ask for your backup details, including the backup type and how you’ll be sharing the backup with us from the following options:

Upload to an Existing Site at Kinsta: If you have an existing site at Kinsta to upload and temporarily store the backup in, you can select it in the field provided. Your existing site on Kinsta will not be altered and will continue to function normally. We will perform the migration to a new site. Once you choose the site to upload to, we’ll show you the SFTP credentials for uploading the file. Be sure to upload your backup file to the /private folder to make sure it remains private.
Link to Files: Choose this option if your backup is stored in a location you can provide a link to. Make sure the link is accessible to anyone who has the URL, or share the backup file with our Migrations team’s email address at [email protected] so they can access the file.

Choose your backup type and how you want to share the backup with the Kinsta migrations team.

Once you’ve chosen how you’ll be sharing the backup and entered the details, click Next to continue.

2. Site details

Complete the site details in your migration request.

Domain name of site to transfer: This is the domain you want to use to access your site.
Add domain with wildcard: A wildcard domain ensures that any requests to a subdomain of *.domain.com resolve to the same IP address as your main domain. For example, if you have a wildcard DNS record for *.example.com pointing to 123.123.123.123, any requests to sub.example.com or blog.example.com will be resolved to 123.123.123.123.
WordPress username: Your WordPress username.
WordPress password: Your WordPress password.
WordPress admin URL: The URL you use to access WP Admin.
Bedrock, Trellis: Select this option if your site uses the Bedrock or Trellis configuration and enter the Root path where the WordPress application is installed.
Is it an e-commerce, community, or membership site?: These sites usually change continuously; therefore, we recommend putting them into maintenance mode to prevent data loss when migrating. If you select this option, you can select the option to Use maintenance mode. Placing a site in maintenance mode means that the site content cannot be updated. While the site is in maintenance mode, a maintenance message is displayed, orders cannot be placed, users cannot register or edit their profiles, and new content cannot be published on the site. For more information about this process, refer to How Kinsta Migrates Dynamic WordPress Sites.
Is it a multisite installation?: If you have a multisite, select this option and choose if your site is a subdirectory or subdomain. You must migrate the multisite network as a whole. The Kinsta migrations team cannot migrate a single sub-site of a multisite network into a standalone site.
Does your site use HTTPS?: If you select this option, you can choose to generate a new SSL certificate in MyKinsta (using our free Cloudflare integration) or upload an existing certificate (if you have the key and certificate file).

After entering your site details, click Next to continue.

3. Kinsta settings

You now need to complete the details for your site’s new home at Kinsta. Enter a unique name and choose your site’s data center from the 37 data center locations available.

Add your Kinsta site details to your migration request.

Once you’ve completed your Kinsta settings, click Next to review your migration details.

4. Review and submit

Review and submit your migration from a backup.

When you’re ready, click Finish to submit your request.

Your pending migrations will show up under WordPress Sites in MyKinsta, and you can check the status anytime. Our Migrations team will also keep you updated on the status.

View migration requests on your WordPress Sites page in MyKinsta.

If you have any additional migrations to submit, click Request migration to begin a new migration request.

Perform a second migration

In some cases, you may have us migrate a site but not be able to go live in a timely manner. When the site is ready to go live, its content may need to be updated to reflect changes made while it’s been live and hosted elsewhere. If this happens, you have the following options:

Migrate the changes manually

The first option is to manually migrate the changes yourself. This can be done in at least three different ways:

Use the content export and import features built into WordPress to export content from your prior host and import it here at Kinsta. Then, install any necessary new plugins and themes and apply updates or settings to themes, plugins, and the WordPress core.
There are many backup and migration plugins that can be used to migrate a WordPress site. While we don’t allow backup plugins for ongoing backups on our platform, if there’s a backup or migration plugin you’re familiar with and comfortable with, you’re welcome to use it to migrate a fresh copy of your site.
Copy changed files to our servers using SFTP or SSH. Then, use a fresh dump of the live site database and import it using either phpMyAdmin or WP-CLI. This process is described in our article How to Do a WordPress Migration on Your Own.

Prior to beginning this process, it’s important to note any changes that were made to the site here at Kinsta after the initial migration. If you modified the WordPress configuration, changed files, or added or removed plugins or themes here at Kinsta after the initial migration, those changes may be overwritten when you migrate the site a second time, depending on the process you use.

Ask Kinsta for a second migration

If you’re unable to handle the update on your own, the Company Owner or Company Administator can contact our team within MyKinsta for assistance.

If the original migration took place within the last week, we can copy over the updated files and import a fresh copy of the database. Note: The live site may need to go into maintenance mode during this process.

If it has been more than a week since the original migration, it’s probable that we will want to migrate the entire site as if it were a brand-new migration.

How Kinsta migrates dynamic WordPress sites

Sites that are continuously updated, such as ecommerce (WooCommerce and Easy Digital Downloads), membership, and community sites, must be placed into maintenance mode during migration to prevent data loss.

What is maintenance mode?

Placing a site in maintenance mode means that the site content cannot be updated. This is usually done by installing a maintenance plugin from the WordPress.org repository. However, if you have a preferred method for placing the site into maintenance mode, that can also be accommodated.

While the site is in maintenance mode, a maintenance message is displayed, orders cannot be placed, users cannot register or edit their profiles, and new content cannot be published on the site.

What is the migration process?

Once maintenance mode has been enabled, we begin migrating a copy of the site to our infrastructure. Upon completion, we will send you instructions on how to preview the site before it goes live.

The copy of the site hosted at Kinsta will not be in maintenance mode. However, it will not be publicly accessible until you update your domain’s DNS records to point the domain at Kinsta.

This means that your site will remain in maintenance mode until you update DNS and the site goes live at Kinsta.

As soon as possible, after the migration has been completed, you will need to carefully review the site, test the site functionality, and then update your domain’s DNS records to point the domain to Kinsta.

As soon as DNS has been updated and fully propagated, your website’s visitors will arrive at the site hosted at Kinsta and be able to continue placing orders, registering users, and publishing content.

How long will my site be in maintenance mode?

It depends on the following variables:

The size of your site.
The speed of data transfer between our infrastructure and the prior host.
The time-to-live (TTL) values associated with your DNS records.
How quickly you can begin reviewing your site after the migration is complete.
How much time you need to review your site thoroughly following the migration.
Any unforeseen complications that arise during the migration process.

As a general rule of thumb, most migrations take between 1 and 3 hours. After that, most clients need between 1 and 3 hours to review the site. DNS propagation usually takes about 1 hour but may take much longer in some cases if extended TTL values are associated with your current DNS records.

You can use this information to get a sense of how long your site will need to be in maintenance mode, but please note that the factors mentioned above do mean that we are unable to accurately predict how long a specific site will need to be in maintenance mode.

How can I minimize downtime?

You can minimize downtime in a few ways:

Schedule the migration for a time when you’ll be available to start reviewing the site immediately after receiving notification that it is complete.
Watch carefully for our Engineers’ message notifying you that the migration is complete.
12 to 24 hours before your anticipated migration timeframe, reduce the TTL value associated with your domain to 5 minutes (300 seconds) to speed up DNS propagation. Note that you’ll want to increase this value, normally to one hour (3600 seconds), after the site is loading from our infrastructure. If your site uses Cloudflare, you do not need to edit the TTL values.
Review our documentation on how to preview a site on our infrastructure so that you understand how to preview the site after the migration.
Review our documentation on how to add and point your domain to Kinsta so that you are prepared to do so as soon as you confirm that the migrated site is ready to go live.

What if this process doesn’t work for me?

If this process simply doesn’t work for your website, please get in touch with our Support team by opening a new chat in MyKinsta when you’re ready to request your migration so that we can discuss other possible options.

Cancel a migration

You cannot cancel a migration once it is in progress. However, if you need to cancel a migration before it starts, you can do so from the WordPress Sites page in MyKinsta. Log in to MyKinsta, navigate to WordPress Sites > sitename, and look for the Migration Request section of the page. Click on the kebab (three-dot) menu and select Cancel migration.

Cancel a site migration in MyKinsta.

In the modal/pop-up that appears, click Cancel migration to acknowledge that canceling this migration will revert any previous steps. If you want to resume the migration after canceling, you’ll need to start a new migration request from the beginning.

Confirm canceling a site migration in MyKinsta.

A notification will appear in the upper right corner, letting you know the migration has been canceled. The canceled migration will no longer be shown in the Migration requests section of the WordPress Sites page.