Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Product facts · Guide

How to Migrate a WordPress Site to Kinsta

Short answer

To migrate a WordPress site to Kinsta, request a free migration in MyKinsta under Sites, then Add site, then Request migration. The Kinsta team copies your site while the old one stays live, and most migrations finish within one business day. Test the copy with Site Preview, then point your domain at Kinsta.

Key takeaways

  • Kinsta migrations are free, and the team handles the move for you.
  • Migrations run Monday to Friday only; Kinsta does not migrate sites on weekends.
  • Most migrations take 1 to 3 hours, plus 1 to 3 hours of review.
  • An expedited migration costs $49 per site, with an 8-hour goal.
  • Lower your DNS TTL to 300 seconds 12 to 24 hours before the move.

What is the fastest way to migrate a WordPress site to Kinsta?

The fastest way is to ask Kinsta to do it, since the team migration is free and runs while your old site stays live.

Kinsta's docs state that migrations are free, and you can choose to migrate the site straight away, schedule it, or buy an expedited migration. Migrations take place Monday through Friday, and Kinsta does not migrate sites on weekends.

If you would rather move the site yourself, Kinsta's docs list two routes: a plugin such as Duplicator or Migrate Guru, or a manual move with SFTP and MySQL. Both are covered below.

RouteCostBest for
Kinsta team migrationFreeMost sites, the team does the work
Expedited migration$49 per siteTight deadlines, 8-hour goal
DIY with plugin or SFTPFreeFull control over the move

What do you need before you start?

You need a Kinsta plan with an open site slot, your current host login details, and a source site the team can reach.

Only a Company Owner or Company Administrator can request a migration, and Kinsta creates a new site for the move, so check that your plan has an open spot first. Gather your current host SFTP or SSH details, username, and password before you start.

If your old host uses two-factor authentication, add the Kinsta migrations email to your account before you submit the request. Kinsta names Cloudways, GoDaddy, SiteGround, and WP Engine as hosts where 2FA can block the team.

Pick a data center near your visitors when the new site is created. Our guide to Kinsta data center locations lists the regions on offer.

Back up the site at your old host and keep a copy on your own computer. Learn WordPress advises the same first step in its migration lesson, and a backup is your way back if the move stalls.

If you have not picked a plan yet, see how much Kinsta costs first.

How do you request a free migration from Kinsta?

Request the migration in MyKinsta, pick a timeframe, then give the team access to your old host.

  1. Log in to MyKinsta and go to Sites, then Add site, then Request migration.
  2. Choose a timeframe: as soon as possible, on a specific date, or expedited.
  3. Choose Migrate from another host or Migrate from a backup.
  4. Enter the source details: host, username, password, and SFTP connection details.
  5. Add your domain, WordPress credentials, and site details, then review and submit.

Most migrations take 1 to 3 hours, with another 1 to 3 hours for review, and the as-soon-as-possible option is usually completed within one business day. You can track the request on the Migrations tab in MyKinsta, and the team sends a message when it is done.

An expedited migration costs $49 per site, with a goal of finishing within 8 hours between 9 AM and 11 PM, Monday to Friday (UTC). Kinsta refunds the fee if the 8-hour target is missed, and agency plans include free expedited credits.

If you migrate from a backup, it must hold both your files and database. You can upload it to an existing Kinsta site in the /private folder, or share a link from cloud storage such as Dropbox, which Kinsta prefers.

Do not make changes to your site once the migration starts. Kinsta's docs state that updates made after that point will not carry over, and a second migration may be needed for them.

How do you migrate a site yourself with a plugin or SFTP?

A plugin packages the site on the old host and unpacks it on the new one, while the manual route moves files and database by hand.

  1. In MyKinsta, go to Sites, click Add site, then Create new site, and select Empty environment.
  2. Download all WordPress files from the old host over SFTP.
  3. Export the database from the old host with phpMyAdmin.
  4. Upload the files to the new site over SFTP, into the /public/ folder.
  5. Open phpMyAdmin in MyKinsta, drop the existing tables, and import the SQL file.
  6. Edit wp-config.php with the new database credentials from the site Info page.
  7. Test the site with Site Preview before you touch DNS.

Kinsta only supports SFTP connections, so set the connection type to SFTP in your client. The SFTP credentials sit under Sites, then your site name, then Info, then Primary SFTP/SSH user.

Duplicator is one free plugin option for the DIY route: it packages files and database into one archive, as its WordPress.org page explains.

Our guide to migrating WordPress with Duplicator walks through that plugin step by step.

Export the database with phpMyAdmin, the MySQL administration tool, by selecting all tables and clicking Export.

How do you test the migrated site before going live?

Test the copy with Site Preview before you change any DNS records.

Kinsta's docs recommend Site Preview for testing, since it shows the new site without changing the database, files, or DNS records. Compare the old and new sites page by page to confirm the move is complete.

Click through pages, submit a form, and log in to wp-admin on the copy. If a link still points at the old host, that is expected before the domain switch, and the URLs update once the domain moves.

Backups are covered too: see whether Kinsta includes backups for the details by plan.

How do you point your domain to Kinsta?

Point your domain at Kinsta only after the copy passes your checks.

Add your domain in MyKinsta, then update your DNS records so the domain points at Kinsta. The manual migration guide notes that this can mean updating nameservers, an A record, or a CNAME record with your registrar.

If the domain also handles email, do not change the nameservers. Kinsta's docs warn that changing nameservers can affect all DNS records, so update only the A or CNAME record in that case.

DNS propagation typically takes around 1 hour, but can vary with TTL settings. Our guide to how long DNS propagation takes explains the wait in more detail.

Once the domain points at Kinsta, update the WordPress Address and Site Address in Settings > General to the primary domain, then click Save Changes.

Lower your DNS TTL to 300 seconds 12 to 24 hours before the move to speed up the switch, then raise it back to around 3600 seconds afterward. Kinsta's docs note that Cloudflare users can skip this step.

What if your site is a multisite network or a store?

Stores, membership sites, and multisite networks need extra care, since their content keeps changing during a move.

For e-commerce, membership, or community sites, Kinsta strongly recommends maintenance mode during the migration to prevent data loss. Visitors see a notice and cannot place orders or register while the move runs.

A multisite network must move as a whole. Kinsta's docs state that the team cannot migrate a single subsite into a standalone site, and the manual route moves each subsite one by one with matching site IDs.

WordPress.com sites are a special case: Kinsta cannot reach the files or database there. The team can only export posts, pages, comments, and other content into a fresh WordPress install, so themes and plugins must be set up again.

What mistakes should you avoid?

The most common mistakes are changing the site mid-move and pointing the domain at the wrong time.

  • Editing the old site after the migration starts.
  • Requesting a migration without an open site slot on the plan.
  • Forgetting to add the Kinsta migrations email on a 2FA host.
  • Changing nameservers when the domain also handles email.
  • Cancelling the old host before DNS has spread.

Plan the move for a weekday, since Kinsta migrates Monday to Friday only. A Friday request that slips can wait until Monday, so leave room in the schedule.

Frequently asked questions

Is Kinsta migration free?

Yes. Kinsta's docs state that Kinsta migrations are free, whether you migrate straight away or schedule the move. An expedited migration costs $49 per site, with a goal of finishing within 8 hours, and agency plans include free expedited migration credits.

How long does a Kinsta migration take?

Most migrations take 1 to 3 hours, with another 1 to 3 hours for review, and the as-soon-as-possible option is usually completed within one business day. Migrations run Monday to Friday only, and Kinsta does not migrate sites on weekends, so plan the move for a weekday.

Can Kinsta migrate my site from a backup?

Yes. The backup must hold both your site files and database. You can upload it to an existing Kinsta site in the /private folder, or share a link from cloud storage such as Dropbox, which Kinsta prefers. Backups made with Duplicator, ManageWP, or cPanel are all accepted.

Does Kinsta migrate WordPress.com sites?

Only the content. Kinsta's docs state that WordPress.com does not allow access to the site files or the database, so the team can only export posts, pages, comments, and other content into a fresh WordPress install. Themes, plugins, and custom work must be set up again afterward.

What does Kinsta not do in a migration?

Pointing your domain to Kinsta, setting up third-party services, and setting up email are not part of the migration service. Kinsta's docs state that you handle those yourself after the move, including updating A records, pointing nameservers to Kinsta DNS, and configuring your email service.

Sources

  1. Migrations - Kinsta Migration Kinsta Docs
  2. Migrations - Manual Migration Kinsta Docs
  3. Duplicator – Backups & Migration Plugin WordPress.org
  4. Migrating your site Part 1: Changing to a new host and domain Learn WordPress
  5. phpMyAdmin phpMyAdmin

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test