Skip to content

Migration

WordPress migration services: how to choose the help your site needs

Compare provider transfers, paid migration work, and ongoing support. Build a clear scope before handing over your WordPress site.

By Besthostlab Sources checked
A hand moves a website and database between server platforms beside a migration toolkit.

A WordPress migration service is worth paying for when it takes responsibility for work you cannot confidently finish yourself. That could mean copying a large site, coordinating a live store’s final data transfer, moving business email, or checking integrations after the domain points to the new server. A file copy on its own may already be included in your destination hosting plan.

Start with the result you need: the same website working on the new host, with the right data, working forms, and a clear point at which the old account can be cancelled. This guide is for an existing self-hosted WordPress site. Moving from a closed website builder, rebuilding the design, or changing the domain adds a different set of tasks.

  1. Define the move Name the site, data, mailboxes, and integrations that must survive.
  2. Assign the work Agree who copies, checks, switches DNS, and resolves problems.
  3. Accept the result Verify real business tasks before ending the old service.
A useful migration service has a beginning, an owner, and an acceptance condition.

Choose the kind of help before comparing prices

Three offers can all be called “migration,” even though you receive very different help. A host-operated transfer moves you into that provider’s environment. An independent specialist can coordinate work across several providers. A migration plugin gives you a tool; you remain responsible for using it and checking the result.

OptionUseful whenClarify before starting
Destination host’s teamYou are moving a supported WordPress site into its hosting.Whether DNS, email, final synchronization, and follow-up fixes are included.
Independent specialistThe move involves multiple systems or needs one coordinator.Deliverables, access permissions, availability, and the limits of the quoted fee.
Plugin-assisted DIYYou can manage backups, compatibility checks, and the switch yourself.Archive size, destination capacity, licenses, and how you would recover a failed import.

A small brochure site with no recent changes may fit the first or third option. A store with orders arriving throughout the day needs a more explicit synchronization plan. Site size matters, but the cost of losing a new order or breaking a booking integration can matter more than the number of gigabytes.

What do actual provider services include?

Kinsta documents free standard WordPress migrations from other hosts. DreamHost lists $99 USD per site for an external move to a standard hosting plan and no migration fee for a move to DreamPress. These are migration offers attached to hosting subscriptions, not the full price of operating the site.

The provider’s eligibility rules are part of the product. For example, Hostinger separates website files and databases from email, DNS records, scheduled jobs, and custom SSL configuration. Do not assume that accepting a website transfer request means every service attached to the domain is being moved.

Ask about your actual installation rather than sending only its URL. Mention Multisite, unusual folder layouts, paid themes, custom PHP requirements, membership systems, scheduled imports, and external storage. A standard migration offer may not cover every one of those circumstances.

Write a scope that can be checked

Your quote should identify the source, destination, and exact site. Include any staging or development copy separately. State whether the existing URLs will remain unchanged and whether the person doing the move is also responsible for domain registration or DNS management. These are different services, even when one company currently provides all of them.

Then turn “make sure it works” into a short acceptance list. For a small business site, that might be: important landing pages load over HTTPS; WordPress login works; a new form submission reaches the business inbox; downloadable files open; scheduled tasks run; and any payments are checked using the payment provider’s permitted testing process.

  • Backup: who takes an independent copy, where it is held, and what it contains.
  • Compatibility: who checks the destination’s PHP version, database requirements, and required extensions.
  • Data: what happens to orders, comments, users, or submissions created after the first copy.
  • Cutover: who changes the necessary DNS records and checks the certificate.
  • Aftercare: which migration-related faults will be fixed and for how long.

Ask whether follow-up support means correcting a copying mistake or debugging any pre-existing plugin problem. Both can be valuable, but an unlimited interpretation is unlikely to match a fixed-price service.

For active sites, ask about the last copy

The first successful copy does not settle the live-data problem. Your old site may continue taking orders while someone reviews the new one. Replacing the destination database later can overwrite changes made there; switching traffic early can send visitors to two different versions.

Kinsta’s migration documentation explains that changes after a migration copy starts are not automatically carried into that copy. Use that distinction when discussing any service: ask when the authoritative data is captured, whether a final synchronization is available, and whether a maintenance window is needed.

A rollback also needs a data plan. Pointing DNS back is only part of recovery if customers have already created records on the new host. For a store or membership business, ask the operator to explain how those records would be reconciled before agreeing to the move.

Keep access limited and temporary

Give the operator the access required by the agreed method, through the provider’s secure process. Where supported, create a separate account instead of sharing your personal owner login. Record who has access to the hosting account, WordPress, DNS, and backup location. Do not send a bundle of unrelated credentials simply because the service is called “fully managed.”

At handover, remove temporary access, rotate credentials that were shared, and confirm who now controls billing and renewal notices. If your developer bought the destination account, make sure the business has the agreed ownership and recovery access before treating the handover as finished.

Compare the whole move, then choose

A hypothetical $150 coordination service might be worthwhile if it covers mailbox migration and a carefully scheduled cutover. A hypothetical $50 file copy could be poor value if your new host already includes it. Those figures are examples of scope differences, not market averages or vendor quotes.

Price the destination subscription, the extra old-host period, replacement email, required licenses, and your own time separately. Our website migration cost guide shows how those items can change the first-year total and the time needed to recover the cost of switching.

Choose the service that closes an identified gap. Before booking, you should be able to finish this sentence: “The provider will move these items, I will handle these remaining checks, and we will consider the job complete when these business functions work.” If that sentence is still vague, the next step is a clearer scope.