New hosting provider
WordPress, uploads and database moved to another provider.
WORDPRESS → VERIFIED TRANSFER → NEW SERVER
WordPress Migration to a New Server and Domain
I will move your live WordPress website to a new server or hosting provider and, when required, to a new domain. Files, database and settings are retained; HTTPS and critical journeys are checked; a domain change includes correct redirects.
Backup before workFiles and databaseDowntime minimisedSSL and DNS301s for domain changesRollback plan
MIGRATION SCENARIOS
Move an existing site, not build a new one
The approach depends on the source condition, access, data volume and cutover requirements.
Move to VPS/VDS
A managed environment with PHP-FPM, database and HTTPS.
Domain change
URL replacement, SSL, redirect mapping and permanent 301s.
WooCommerce
A separate plan for orders, payments and final synchronisation.
MySQL / MariaDB
Database transfer with import, encoding and write checks.
Failing server
Available files, database and backups assessed before commitments.
WHAT THE WORK INCLUDES
Seven stages of a controlled migration
01
Audit
WordPress, PHP, plugins, database, files, cron, DNS and access.
02
Verified backup
Files and database copied with a recovery check.
03
Target server
Web server, PHP-FPM, database, HTTPS and baseline hardening.
04
Files and database
Uploads, configuration and database; URLs changed safely.
05
Preview
The copy is tested before public traffic moves.
06
Cutover
DNS, SSL, forms, media, login, permalinks, email and cron.
07
SEO checks
For a domain change: 301s, canonical, sitemap, 404s and Search Console by agreement.
Important: zero downtime is not promised before an audit. An active WooCommerce store needs a synchronisation strategy or controlled write window. Moving a domain registration is a separate operation.
DOMAIN CHANGE WITHOUT FALSE GUARANTEES
URLs, 301 redirects and reindexing
Old and new pages are mapped. Absolute WordPress URLs are updated with a serialisation-aware tool; canonical links and sitemap move to the new domain; page-level 301 redirects remain in place.
After launch, 404s, redirect chains and loops, mixed content, indexing and Search Console are monitored. Rankings and traffic cannot be guaranteed: search-engine reindexing can cause temporary movement.
DOMAIN CHANGE CHECKAfter cutover
✓ old URL returns one correct 301
✓ canonical targets the new URL
✓ sitemap contains only new URLs
✓ HTTPS resources avoid mixed content
✓ 404s and indexing are monitored
TWO DIFFERENT SCENARIOS
A new server is not the same as a new domain
A hosting move keeps public URLs. A domain change adds a separate SEO workstream.
| Area | New server only | New server + domain |
|---|---|---|
| DNS | Points to the new server | New domain configured; old one retained for redirects |
| WordPress URL | Usually unchanged | home/siteurl and absolute links change |
| SSL | Certificate for the existing domain | Certificates for both old and new domains |
| 301 redirects | Usually unnecessary | Permanent page-level redirects required |
| Sitemap and canonical | URLs remain the same | Move to the new domain |
| Indexing | Page addresses remain | Search engines must reindex URLs |
TECHNICAL SAFETY
Serialised data and one write source
WordPress stores some URLs and plugin settings in serialised values. A naive SQL replacement can corrupt string lengths and plugin data.
Safe URL replacementWP-CLI search-replace or an equivalent serialisation-aware tool is used.
One active databaseWriting to old and new databases without replication or sync creates divergent records.
Final write windowWrites are controlled before the last sync and traffic cutover.
No redirect loopsRules are tested with proxy, HTTPS and WordPress settings together.
No mixed contentMedia, CSS, JS, iframes and plugin data are checked for old HTTP links.
Rollback pathThe source, criteria and person responsible for reverting traffic are agreed first.
POST-MIGRATION CHECKLIST
More than the homepage is tested
The exact acceptance plan follows the site, but the baseline is explicit.
Content and mediaPages, images, uploads, permalinks and search.
UsersLogin, roles, admin, creating and editing content.
CommunicationForms, email, notifications, webhooks and external APIs.
WooCommerceCart, checkout, payments, statuses and new orders.
Background workWP-Cron, system cron, queues, imports and backups.
SEO and errorsHTTPS, canonical, robots, sitemap, redirects, 404s and logs.
Delivered by Andrey Zubar / iFreeWork. Related WordPress work: WordPress, amoCRM and Telegram lead automation.
CLIENT FEEDBACK
Website migration review
Mark Antony — 14 October 2026
Project: “Website and database migration to a new server without data loss.”
Translated from Russian.
“We urgently needed to move the website to another server because of problems with the current hosting. Andrey quickly assessed the infrastructure, prepared the new server and transferred the website together with the database. No information was lost; after the migration he checked the main functions and configured backups. He was always available and explained his actions in detail. We are fully satisfied with the result and recommend working with him.”
The review confirms a website and database migration. It does not identify WordPress or a domain change.
View reviews on the source page →PRICING
Quote after assessment
Individual quote
A fixed price for an unknown production site would be misleading.
- Website and database size
- WooCommerce and order activity
- Domain change and redirect-map scope
- Source-server access and condition
- Acceptable downtime
FAQ
WordPress migration questions
How can WordPress be moved without losing data?⌄
Audit access and dependencies, create a recoverable files-and-database backup, prepare and test the target, then perform the final synchronisation and cutover.
Can WordPress move to a new server and domain together?⌄
Yes. The plan also needs safe URL replacement, HTTPS, page-level 301 redirects, canonical links and a new sitemap.
Will pages, images and users be retained?⌄
They move with the database and uploads directory. The result is checked in preview and again after cutover.
Must DNS change, and how long does it take?⌄
DNS usually changes to direct the domain to the target server. Propagation depends on TTL and the DNS provider; preparation happens in advance.
What happens to SEO after a domain change?⌄
Search engines must reindex the URLs. Correct 301s, canonical, sitemap and error monitoring reduce risk, but temporary ranking changes cannot be excluded.
Are 301 redirects required?⌄
For a domain change, yes. Each important old URL should lead directly to its matching new URL, without chains or loops.
Can WooCommerce be moved without losing orders?⌄
Yes, but an active store needs a defined write window, final sync or appropriate replication strategy. A one-off copy is not enough.
Will the website be unavailable during migration?⌄
Most work can happen in advance and downtime can often be limited to final cutover. Zero downtime depends on an audit.
What is needed to start?⌄
Describe the site, current and target hosting, approximate data size, WooCommerce use, domain-change requirement and acceptable downtime. Do not submit secrets through the form.
Related case studies and reading
Recovering Infected Websites: Cleanup, Security and Search EnginesExplore the project problem, solution and limitations.
VPS, Docker and infrastructure security auditDiscuss the scope and approach for a similar task.
MIGRATION ASSESSMENT
Describe the site and target scenario
Include site size, WooCommerce, source and target hosting, domain-change requirement and acceptable downtime. Do not send passwords or keys.
@ifwcomMessage on TelegramDiscuss WordPress Migration
Secure access is arranged separately.