Changing hosts can improve support, capacity or cost, but the move involves more than copying a folder. A WordPress site depends on files, a database, PHP and server settings, email and DNS records, SSL, scheduled tasks and sometimes external services. A careful migration plans those dependencies before the live switch. Code Papa moves WordPress websites between hosting providers, verifies the destination and helps coordinate the cutover. The exact process depends on the old host, site size, domain setup and whether the website handles orders or member activity while the transfer takes place.
Looking for WordPress website migration? The package choices below explain the starting scope and the details needed to prepare a useful quote.
Plan the move before copying
We first review the current host, the destination plan, the website size, domain registrar, DNS setup, email service, SSL status and any staging or multisite configuration. For a store or membership site, we discuss how to handle activity during the move so new orders or user changes are not lost. The destination must meet the site’s technical requirements and have enough storage and resources. If the new host is not ready, the migration should wait. A short plan names the backup point, staging checks, DNS change window, rollback option and the person who controls each account.
What transfers and what may not
A standard move covers WordPress files and the database, plus the configuration needed for the site to run at the new location. Themes, plugins, uploads and content travel with those files, but licenses, mailboxes, cron jobs, CDN settings, firewall rules and host-specific features may need separate attention. Email service is often separate from website hosting; changing web DNS without preserving mail records can interrupt email. Domain registration does not automatically move with hosting. We identify these boundaries before work starts and document any part that remains with the old provider or needs your administrator to approve.
Staging, validation and launch window
The site is copied to the new environment and checked before public DNS points there. I review representative pages, forms, media, administrator access and key integrations. For WooCommerce, we plan a content freeze or a final synchronization so orders made during the move are accounted for. SSL and redirects are checked after the destination is ready. DNS propagation varies by resolver and may take time; no migration can control every visitor’s cache. We agree when the switch happens and how to reverse it if a critical issue appears. Do not cancel the old hosting account until the new version has been verified.
What you need to provide
You provide active access to both hosting accounts, domain or DNS control, WordPress administrator access and any relevant CDN or firewall account. Use temporary users or a secure sharing tool; do not paste credentials into a public form. Tell me whether email is hosted with the old provider and identify mailboxes or DNS records that must remain. For a store, share the quietest practical maintenance window and explain how orders are managed. If your host restricts backups or external access, we may need the provider’s help. Account ownership and billing remain with you.
Backups and rollback planning
Before moving, we confirm a backup of files and database and establish how to restore it. A backup is only useful if it is complete and accessible. I avoid deleting the old environment during the transfer. If the new location does not behave as expected, we can pause the DNS change, correct the destination or return traffic to the original host when the DNS setup permits. Changes made after cutover can complicate a rollback, so the plan explains when to pause editing or ordering. A high-traffic store may require a more deliberate synchronization process than a simple informational website.
Migration boundaries and risks
A routine transfer does not include rebuilding a broken site, cleaning malware, redesigning pages, repairing unsupported custom code, setting up mailboxes or negotiating with a hosting company unless those items are quoted. Some old plugins depend on server versions or licensing that differ at the destination. A site may reveal problems only when served under the new PHP version or security rules. In that case I report the finding and estimate a fix instead of hiding it inside the migration. A domain move, email migration and DNS redesign are separate workstreams and should be scheduled with the relevant providers.
Packages for different site sizes
Single Site Move is intended for one standard WordPress installation with straightforward hosting and DNS. Business Move allows more time for a larger website, additional checks and coordinated cutover. Store or Complex Move is for WooCommerce, memberships or other sites where new activity must be preserved and the move needs a planned window. Timing begins once account access and destination readiness are confirmed. DNS propagation and provider response times are outside the developer’s control, so the estimate covers the work window rather than promising a universal moment when every visitor sees the new server.
Questions about changing hosts
Will my domain move too? Hosting transfer and domain registration transfer are separate; DNS can often be updated while the registrar remains unchanged. Will email stop working? It should continue if records are preserved, but we confirm how email is hosted. Can you guarantee zero downtime? I plan to minimize interruption, but DNS and provider behavior cannot be guaranteed everywhere. Do you cancel the old plan? No, you keep it until the new site is verified. Will SEO be affected? Correct URLs and redirects should be preserved; changes to structure need separate mapping and review.
Start with the hosting details
Send the current website URL, old and new host names, approximate site size, domain registrar, whether email is hosted with the old provider, and whether the site takes orders or member updates. I will confirm what access is needed and recommend a suitable migration window. Code Papa works remotely from the UAE with US and UK clients, so the cutover time is chosen together. A 50% deposit books the move; you can request a video call any time before handover, and the final 50% follows your review and approval of the completed transfer.
Coordinate every account involved
A transfer may involve you, the current host, destination host, domain registrar and email provider. I can manage WordPress migration and explain DNS changes, but only the account owner or authorized contact can approve certain actions. Share support contacts and any provider ticket already open. If a host must generate a backup or allow an address, request it early. Confirm who can make the go-live decision and who will test the site afterward. Clear responsibility reduces the risk that a prepared migration waits because nobody knows which account controls the next step.
Verify the destination after launch
Once the new server is live, review the public site and administrator, then test the main form or shopping journey. Check SSL, images, important redirects, the sitemap and any mail records that use the domain. Keep the old hosting active through the agreed verification window. DNS resolvers can update at different times, so some visitors may temporarily see the previous destination. The handover notes should say which server is current and where the backup is stored. Do not cancel the previous plan until the new environment has been checked and you are comfortable with the result.
Protect the domain and email ownership
Keep the domain registrar and mail provider accounts under your control even when a developer helps with the move. Before changing DNS, export or record the existing zone and confirm which records support website, email verification and other services. Never assume that a nameserver change is equivalent to changing only the website address. Ask the mail provider to confirm the current records if there is any uncertainty. When the migration is finished, document the host, DNS provider, SSL method and backup location. This makes the next renewal, incident or move easier to handle.
What I need from you
Old and new host access, DNS/domain access, site URL and size, email/DNS details, backup status, integrations and a suitable cutover window.
Choose a package
These scopes are starting points. The final quote confirms the agreed page or product count, timing, revision scope and any exclusions before work begins.
Single Site Move — 2–4 working days
One standard WordPress site, backup, transfer, DNS guidance and essential checks.
Business Move — 4–7 working days
Larger site or extra integrations, staging validation, SSL and redirect checks.
Store / Complex Move — 6–10 working days
WooCommerce or membership planning, coordinated cutover and activity-aware checks.
Payment, review and handover
A 50% upfront payment books and starts the agreed work. You can request a video call at any point before handover to review progress or discuss the finished project. Once you have reviewed the completed scope and confirmed you are satisfied, the remaining 50% is due before final handover. The written proposal sets the deliverables, timing, revision rounds and any third-party costs. This process gives both sides a clear record of what was agreed.
If you are comparing options for WordPress website migration, send the website, scope and timing details listed above. I will recommend the package that best fits the work.