Choose the Migration Route
| Route | Best for | Important consideration |
|---|---|---|
| Kinsta migration team | Standard WordPress sites and buyers who want assistance | Prepare credentials and review follow-up questions |
| Scheduled migration | Sites that change continuously | Coordinate maintenance mode and final sync |
| Expedited migration | Time-sensitive moves | Confirm current fee, target and eligibility |
| DIY migration | Experienced WordPress administrators | You own file, database, URL and cutover accuracy |
Kinsta's official migration documentation is the primary source for current procedures.
Before Submitting the Migration
Confirm plan capacity
Make sure the destination account has a site slot and enough storage and traffic capacity.
Collect source access
Prepare the current host, SFTP or SSH, database and control-panel details requested by the migration process.
Record DNS and email dependencies
Export current DNS records and identify services that must not be changed during the hosting move.
Plan dynamic-content handling
For stores, memberships and communities, define maintenance mode and the final content freeze.
Review the Migrated Site Before DNS
Test the migrated copy before changing production DNS. Review public pages, login, forms, checkout, scheduled tasks, redirects, media, SSL behavior, caching and analytics.
Do not judge success from the homepage alone. Use a written checklist and compare critical transactions against the current production site.
DNS Cutover and Post-Launch Checks
Lower DNS risk
Review TTL values before the migration window and keep the old host available during propagation.
Change only required records
Avoid overwriting unrelated email, verification or third-party service records.
Monitor the live site
Check errors, forms, transactions, cron jobs, search visibility and analytics after cutover.
Keep rollback material
Retain source backups and access until the migrated site has completed a stable observation period.
Migration FAQ
Kinsta documentation states that standard WordPress migrations are free. Eligibility and timing should be confirmed in MyKinsta or with Kinsta support.
The migration team may request hosting panel and SFTP or SSH details, plus access needed to copy files and the database. Use a secure credential-sharing process.
Kinsta documentation recommends planning maintenance mode for continuously changing sites such as ecommerce, membership and community projects to reduce data-loss risk during cutover.
Yes, but the destination must be prepared and managed by you. That includes the OS, web stack, database, TLS, backups, monitoring and security.