How To Migrate WordPress To New Hosting Without Losing Data or Downtime

You’re paying for terrible hosting. Your site loads slowly. Support tickets go unanswered. Downtime happens monthly. But you can’t migrate because you’re terrified of breaking your site, losing emails, or experiencing hours of downtime while customers try to access your business. Every day you delay migration, you lose money through poor performance and frustrated visitors.

According to hosting migration research, 67% of website owners avoid migrating hosts due to fear of data loss, downtime, or technical complexity. This hesitation costs businesses real money – slow hosting impacts SEO rankings, conversion rates, and customer satisfaction. Yet migration, done correctly, involves zero downtime and zero data loss.

This comprehensive guide walks through every migration step using battle-tested zero-downtime methodology. You’ll learn the exact process that ensures your live site continues serving customers while you build and test your new environment behind the scenes. No technical expertise required – just careful following of steps in correct order.

Whether migrating a simple WordPress blog, complex WooCommerce store, or custom web application, this guide covers complete process including files, databases, emails, DNS configuration, and testing. By the end, you’ll understand not just how to migrate, but why each step matters and how they fit together.

Most importantly, you’ll discover why the staging-first approach eliminates migration anxiety. Your old site stays live and functional throughout the entire process. You test everything thoroughly before switching. If something goes wrong during testing, your live site remains unaffected. This methodology transforms migration from terrifying gamble into controlled, predictable process.

Why Migrate WordPress Hosting Feels Scary (And Why It Shouldn’t)

The fear is reasonable. Horror stories circulate about botched migrations destroying businesses:

Common migration disasters:

• Site goes down during migration, losing sales for hours or days
• Database import fails, losing customer orders and content
• Email stops working, missing critical business communications
• DNS misconfiguration makes site unreachable for days
• Backup plan fails, losing years of content permanently

These disasters share common cause: rushing migration without testing, or switching DNS before verifying everything works.

The zero-downtime migration difference:

Traditional migration approach (causes disasters):

1. Backup old site

2. Change DNS to new hosting

3. Upload files and database

4. Hope everything works

5. Panic when it doesn’t

Zero-downtime staging approach (this guide):

1. Backup old site (stays live)

2. Setup DNS zone on new hosting

3. Change nameservers BUT set A record to old IP (old site stays live)

4. Create staging subdomain on new hosting

5. Upload files and import database to staging

6. Test everything thoroughly on staging.yourdomain.com

7. Migrate emails in background

8. Once staging tests perfectly, switch A record to new hosting

9. Old site → New site seamlessly (visitors don’t notice)

Key insight: Your old site continues serving visitors throughout steps 1-7. Testing happens on staging subdomain invisible to public. Only in step 8 do you switch traffic to new hosting – and by then, you’ve verified everything works perfectly.

This methodology eliminates anxiety because it eliminates risk. You’re not gambling with your live site. You’re building perfect replica, testing extensively, then switching when ready.

Prerequisites: What You Need Before Starting

Before beginning migration, gather these credentials and access:

Current Hosting Access

• File access: FTP/SFTP credentials or control panel access
• Database access: phpMyAdmin or database management tool
• Control panel: cPanel, Plesk, DirectAdmin, or hosting dashboard login

Domain Registrar Access

• DNS management: Ability to change nameservers or A records
• Domain lock status: Know if domain is locked (affects transfers)
• Authorization code: If planning domain transfer (optional)

Email Configuration

• Email accounts list: All addresses like [email protected]
• Email passwords: Or ability to reset them
• IMAP settings: Old hosting’s mail server information

WebHostMost Account

• Active hosting plan: Purchase before migrating (view plans here)
• Web Control Panel credentials: Received via email after purchase
• Server information: Server number and IP address from welcome email

Pro tip: Purchase WebHostMost hosting 2-3 weeks before old hosting expires. This overlap period provides comfortable time for migration, testing, and fixing issues without rushing or losing access to backups.

Free Professional Migration Service

If you purchased Micro, Pro, or Ultra plan (1 or 3 years), WebHostMost includes free professional migration service. Simply open support ticket requesting migration assistance – technical team handles entire process for you.

Why you might still want to self-migrate:

• Learn hosting management skills
• Migrate immediately without waiting
• Control exact timing of DNS switches
• Understand your site’s technical configuration

This guide enables confident self-migration while professional service provides backup option if needed.

The Complete Migration Timeline: What to Expect

Understanding the complete migration timeline helps plan around business requirements.

Day 1-2: Preparation Phase

• Backup current site (files + database)
• Purchase WebHostMost hosting
• Receive credentials and access Web Control Panel
• Review migration guide and plan approach

Day 3-5: Setup Phase

• Upload files to WebHostMost
• Create database and import data
• Update configuration files
• Setup DNS zone (A record to old hosting IP)
• Change nameservers to WebHostMost

Day 6-7: Testing Phase

• Wait for nameserver propagation (4-24 hours)
• Create staging subdomain
• Test all site functionality on staging
• Fix any issues discovered during testing
• Verify SSL certificates installed

Day 8-10: Email Migration

• Create email accounts on WebHostMost
• Use IMAPSync to copy email messages
• Verify email sending/receiving works
• Test email client configurations

Day 11-12: Go Live

• Final verification of staging site
• Switch A record to WebHostMost IP
• Monitor DNS propagation (1-4 hours)
• Verify live site working correctly
• Test all critical functions

Day 13-28: Monitoring Period

• Monitor site performance and functionality
• Watch for any delayed email delivery
• Verify backups running correctly
• Keep old hosting active as safety backup
• After 2 weeks, safe to cancel old hosting

Total estimated time: 2-4 weeks for cautious, thorough migration with comfortable overlap period. Rushing possible in 2-3 days if time-pressured, but not recommended for business-critical sites.

Step-by-Step Migration Process: Zero Downtime Guaranteed

Let’s walk through complete migration process with detailed explanations of why each step matters.

Phase 1: Backup and Prepare (Old Hosting)

Critical first step: Create complete backup before touching anything. This provides restore point if anything goes wrong.

Backup Website Files

Your website files live in specific directory on old hosting, typically public_html/, www/, or httpdocs/.

Method 1: Control Panel File Manager

1. Log into old hosting control panel
2. Navigate to File Manager
3. Locate website directory
4. Select entire folder
5. Right-click → Compress → Choose .zip format
6. Download compressed archive to local computer

Method 2: FTP/SFTP Download

1. Connect using FileZilla or similar FTP client
2. Navigate to website folder on remote server
3. Download entire directory to local computer
4. Compress locally using WinZip, 7-Zip, or built-in compression

File size considerations:

• Small sites (<500MB): Either method works fine
• Large sites (500MB-5GB): SFTP more reliable for downloads
• Very large sites (5GB+): Consider incremental backup or compression on server first

What to verify: After backup, confirm archive contains:

• All website files (HTML, PHP, images, CSS, JavaScript)
• .htaccess file (may be hidden – ensure hidden files visible)
• Configuration files (wp-config.php for WordPress, etc.)
• Upload directories with all images and media

Backup Database

WordPress and most CMSs store content in MySQL/MariaDB database. Backing up database captures posts, pages, products, comments, user data.

Export database via phpMyAdmin:

1. Log into phpMyAdmin on old hosting
2. Select database from left sidebar (may be only one database, or multiple)
3. Click “Export” tab at top
4. Export method: Choose “Quick” (sufficient for most sites)
5. Format: SQL
6. Click “Go” to download .sql file
7. Save to same location as file backup

For large databases (>100MB):

1. Choose “Custom” export method instead of Quick
2. Enable “gzip compression” checkbox
3. This creates compressed .sql.gz file (much smaller)
4. Download compressed version

Multiple databases: If site uses multiple databases (some advanced setups), export each database separately. Note which database connects to which application.

Verify backup: Open .sql file in text editor (Notepad++, VS Code). You should see SQL commands starting with CREATE TABLE, INSERT INTO, etc. If file shows binary data or errors, re-export.

Document Current Configuration

Before migrating, document technical details needed later:

Database credentials (from config file):

• Database name
• Database username
• Database password
• Database host (usually “localhost”)

PHP version: Check old hosting control panel for PHP version. Verify new hosting supports same version to avoid compatibility issues.

Email accounts: List all email addresses, noting which are actively used. You’ll recreate these on WebHostMost.

DNS records: If using any custom DNS records (subdomains, third-party services, SPF/DKIM records), document these. You’ll add them to WebHostMost DNS zone.

SSL certificate type: Note if using free Let’s Encrypt or custom SSL certificate. WebHostMost provides free auto-SSL for standard setups.

Phase 2: Upload to WebHostMost

Once backups are secure, upload content to WebHostMost. Your old site remains live and serving visitors during this phase.

Access WebHostMost Web Control Panel

After purchasing WebHostMost hosting, you receive email with credentials:

Web Control Panel access:

• URL: https://serverX.webhostmost.com:2222/evo/login (replace X with your server number)
• Alternative: Login to Client Area → Click “Login to Control Panel” button
• Username: Provided in welcome email
• Password: Set during signup or in welcome email

First login tasks:

1. Familiarize with control panel layout
2. Locate File Manager (for uploading files)
3. Locate Database Manager (for creating database)
4. Locate DNS Management (for configuring DNS)

Upload Files to WebHostMost

Upload location: Files must go in correct directory structure:

domains/yourdomain.com/public_html/

Correct structure:

public_html/

  ├── index.php (or index.html)

  ├── wp-admin/ (if WordPress)

  ├── wp-content/

  ├── wp-includes/

  ├── .htaccess

  └── other files

Incorrect structure to avoid:

public_html/

  └── mysite-backup/ ❌ Wrong!

      └── index.php

Upload method 1: File Manager (recommended for beginners):

1. Navigate to File Management → File Manager
2. Browse to domains/yourdomain.com/public_html/
3. Click “Upload” button in toolbar
4. Select your backup archive (.zip, .tar.gz, .rar)
5. Wait for upload completion (shows progress bar)
6. After upload completes, right-click archive → “Extract”
7. Extraction creates folders/files in public_html
8. Verify structure is correct (index.php directly in public_html, not in subfolder)

Upload method 2: SFTP (recommended for large sites 500MB+):

SFTP (Secure File Transfer Protocol) provides faster, more reliable transfers for large sites.

1. Download FileZilla FTP client (free)
2. Open FileZilla → File → Site Manager → New Site
3. Enter connection details:
   • Host: serverX.webhostmost.com (your server)
   • Port: 2323
   • Protocol: SFTP
   • Logon Type: Key file
   • User: Your Web Control Panel username
   • Key file: Browse to .ppk file from welcome email
4. Click “Connect”
5. Navigate to domains/yourdomain.com/public_html/ on remote side (right panel)
6. Drag and drop your website folder from local (left panel) to remote (right panel)
7. Transfer begins automatically
8. For large sites, this may take hours – FileZilla shows progress

File permissions: After upload, verify correct permissions:

• Files: 644 (readable by all, writable by owner)
• Folders: 755 (executable/searchable by all, writable by owner)
• Most uploads set these automatically, but check if permission errors occur

Create and Import Database

Your website files are uploaded. Now import database so dynamic content works.

Create database:

1. Navigate to Databases → SQL Database Manager
2. Click “Create Database” button
3. Enter database name: Type desired name (e.g., “wordpress”, “mystore”)
4. System adds prefix automatically: Your username becomes prefix
5. Final database name: ijodghbk_wordpress (your prefix + your name)
6. Click “Create”
7. Database created successfully

Understanding database prefixes: WebHostMost adds your username as prefix to all database names. This ensures uniqueness on shared server and prevents conflicts. Your database name will be something like:

• You enter: wordpress
• System creates: ijodghbk_wordpress
• You’ll use the full name (ijodghbk_wordpress) in configuration files

Create database user:

1. In database list, find your new database
2. Click “Manage” button next to database
3. Scroll to “User Access” section
4. Click “Manage Users” button (top right)
5. Click “Create User” button
6. Enter username and strong password
7. Save credentials securely (you’ll need these!)
8. Return to database management page
9. In “User Access” section, grant this user “Full access”

Import SQL file:

1. In database list, click “Manage” next to your database
2. In “Database Operations” section, click “Import” button
3. Click “Choose File” and select your .sql backup
4. Click “Import” button
5. Wait for import to complete (progress indicator shows status)
6. Large databases (100MB+) may take 5-15 minutes
7. Success message confirms completion

Import troubleshooting:

• Timeout error: For very large databases (500MB+), contact support for assisted import
• Compressed files: .sql.gz or .sql.zip files import automatically (decompresses during import)
• Multiple SQL files: Import each file separately if backup created multiple files

Update Configuration Files

After importing database, update website configuration to use new database credentials.

For WordPress (edit wp-config.php):

define(‘DB_NAME’, ‘ijodghbk_wordpress’);     // New database name WITH prefix

define(‘DB_USER’, ‘ijodghbk_dbuser’);        // New database user WITH prefix  

define(‘DB_PASSWORD’, ‘your_new_password’);  // Password you created

define(‘DB_HOST’, ‘localhost’);              // Always localhost on WebHostMost

For Joomla (edit configuration.php):

public $db = ‘ijodghbk_joomla’;

public $user = ‘ijodghbk_dbuser’;

public $password = ‘your_new_password’;

public $host = ‘localhost’;

For Drupal (edit settings.php):

$databases[‘default’][‘default’] = [

  ‘database’ => ‘ijodghbk_drupal’,

  ‘username’ => ‘ijodghbk_dbuser’,

  ‘password’ => ‘your_new_password’,

  ‘host’ => ‘localhost’,

  ‘driver’ => ‘mysql’,

];

For Laravel (edit .env file):

DB_CONNECTION=mysql

DB_HOST=localhost

DB_DATABASE=ijodghbk_laravel

DB_USERNAME=ijodghbk_dbuser

DB_PASSWORD=your_new_password

Common mistake: Forgetting to update database credentials causes “Error establishing database connection” when site loads. Double-check credentials match exactly what you created in Database Manager.

Phase 3: DNS Configuration (Critical Zero-Downtime Step)

This phase is most important for achieving zero downtime. Follow steps in exact order.

Critical: Remove DNSSEC First!

BEFORE changing nameservers, you MUST disable DNSSEC at domain registrar. DNSSEC will completely break your site if not removed before switching to WebHostMost.

1. Log into domain registrar
2. Find “DNSSEC” in DNS settings
3. Click “Disable” or “Remove DNSSEC”
4. Save changes

If no DNSSEC option exists, you don’t have it enabled – proceed safely.

Setup DNS Zone on WebHostMost (Before Changing Nameservers)

Configure DNS zone FIRST, then change nameservers. This ensures zero downtime.

1. Log into Web Control Panel → Domain Management → DNS Management
2. Find your domain → Click “Manage”
3. Set A record to OLD hosting IP:
   • Find A record for main domain (@ or yourdomain.com)
   • Change IP to your old hosting IP address
   • Contact old hosting support: “What is my server IP address?”
   • Save changes
4. Configure MX records (optional – keeps email working):
   • Option A: Add old hosting MX records (email stays on old server temporarily)
   • Option B: Use WebHostMost MX records (email migrates now)
5. Add any other DNS records (TXT, CNAME, etc.) if needed

Why A record points to old hosting: After nameserver change, visitors still see old site. No downtime. You control when to switch.

Change Nameservers to WebHostMost

1. Log into domain registrar
2. Find “Nameservers” section
3. Change to WebHostMost nameservers:
   • ns1.server1.webhostmost.com
   • ns2.server2.webhostmost.com
   • ns3.server3.webhostmost.com
   • ns4.server4.webhostmost.com
4. Save changes

All 4 nameservers required! If registrar only allows 2, contact their support.

Result: Nameservers point to WebHostMost (you control DNS), A record points to old hosting IP (old site stays LIVE).

Wait for Nameserver Propagation (30 mins – 4 hours)

Before creating staging subdomain, wait for nameserver changes to propagate.

Check propagation:

• Visit dnschecker.org
• Enter your domain, select “NS” record type
• Verify multiple locations show WebHostMost nameservers

Typical wait: 2-4 hours

Once propagation completes: Proceed to Phase 4 (staging subdomain creation).

Phase 4: Create Staging Environment and Test

Nameservers point to WebHostMost. A record points to old hosting. Old site is live. Now create staging subdomain for testing.

Why Staging Subdomain is Essential

Staging provides:

• Safe testing environment: Fix issues without affecting live site
• Preview URL: Show clients/stakeholders migrated site before launch
• Zero pressure: Take time testing thoroughly
• Easy rollback: If testing reveals problems, old site remains unaffected

Staging workflow:

Old site (live): yourdomain.com → old hosting IP

Staging (testing): staging.yourdomain.com → WebHostMost server

Visitors accessing yourdomain.com see old site. You access staging.yourdomain.com to test new site. When staging tests perfectly, switch A record to go live.

Create Staging Subdomain

1. Navigate to Domain Management → Subdomain Setup
2. Click “Add Subdomain” button
3. Enter subdomain name: staging (creates staging.yourdomain.com)
4. Document root: Point to public_html/ (where you uploaded files)
5. Click “Create”
6. Wait 5-10 minutes for DNS propagation

DNS automatic configuration: WebHostMost automatically creates DNS A record for staging subdomain pointing to server IP. No manual DNS configuration needed for subdomains.

Test Everything on Staging

Visit https://staging.yourdomain.com and thoroughly test all functionality:

Core functionality:

• Homepage loads correctly with proper styling
• Navigation menu works (all links functional)
• Internal page links work correctly
• Forms submit properly (contact forms, search, newsletter signup)
• Login functionality (admin area, user accounts)

Content verification:

• All pages display correct content
• Images and media load properly
• Blog posts or products appear correctly
• Comments/reviews display (if applicable)

Database connectivity:

• Dynamic content loads (posts, products, user data)
• Search functionality returns results
• User registration/login works
• Shopping cart functionality (if WooCommerce/e-commerce)

Technical checks:

• SSL certificate installed (padlock icon in browser)
• No mixed content warnings (HTTP resources on HTTPS page)
• No 404 errors in browser console (F12 → Console tab)
• Mobile responsive (test on phone or use browser mobile emulation)

Common issues and fixes:

Issue: Staging shows “Error establishing database connection”

• Fix: Verify wp-config.php (or equivalent) has correct database credentials
• Confirm database name includes prefix: ijodghbk_wordpress

Issue: Images/CSS not loading, site looks broken

• Fix: Hard-coded URLs in database pointing to old domain
• For WordPress: Install “Better Search Replace” plugin
• Search for: https://oldsite.com
• Replace with: https://staging.yourdomain.com
• Run on all database tables

Issue: SSL certificate missing or browser shows “Not Secure”

• Fix: Wait 10-15 minutes after subdomain creation
• WebHostMost auto-installs Let’s Encrypt SSL certificates
• If still missing after 30 minutes, manually request SSL in Control Panel → Security Management → SSL Certificates

When staging tests pass: All functionality works, no errors, content displays correctly. You’re ready to proceed to email migration (Phase 5) and prepare for going live.

Phase 5: Migrate Email Accounts and Messages

With staging site tested and working, migrate email without rushing. Old email continues functioning during migration.

Create Email Accounts on WebHostMost

Recreate all email addresses from old hosting:

1. Navigate to Email Manager → Email Accounts
2. Click “Create Email Account” button
3. Enter email details:
   • Email address: [email protected]
   • Password: Use same password or create new one
   • Quota: Mailbox size limit (1GB typical, adjust as needed)
4. Click “Create”
5. Repeat for all email accounts

Email account considerations:

• Password policy: Use strong passwords, different from hosting account
• Quota limits: Set realistic mailbox sizes (1-5GB typical for business email)
• Catch-all: Optionally configure catch-all address receiving email to non-existent addresses

Migrate Email Messages Using IMAPSync

IMAPSync copies existing emails from old hosting to WebHostMost without deleting originals. Safe, reliable migration method.

IMAPSync migration process:

1. Navigate to Email Manager → IMAPSync Migrations
2. Click “Import Emails” button (importing TO WebHostMost)
3. Fill in migration form:

Source (old hosting):

• IMAP Server (Host): Old hosting’s IMAP server hostname
  • Contact old hosting support: “What is my IMAP server hostname?”
  • Common formats: mail.oldhostingdomain.com, imap.oldhost.com, mail.yourdomain.com
• Email (User): Full email address on old hosting
• Password: Email password on old hosting
• Port: Usually 993 (IMAP SSL) or 143 (IMAP)
• Security: SSL/TLS (if port 993)

Destination (WebHostMost):

• Email: Select WebHostMost email from dropdown (emails you created in previous step)
• Authentication: Internal sign-in (pre-selected)

4. Click “Start Migration” button
5. Migration runs in background (can close browser)
6. Check back periodically for completion status

Migration duration:

• Small mailbox (<1GB): 15-30 minutes
• Medium mailbox (1-5GB): 1-3 hours
• Large mailbox (5-10GB): 3-6 hours
• Very large mailbox (10GB+): Overnight or longer

Multiple email accounts: Run separate IMAPSync for each email account. Migrations run concurrently (multiple can run simultaneously).

Verification: After migration completes:

1. Login to WebHostMost webmail: https://yourdomain.com/webmail
2. Verify emails appeared correctly
3. Check folder structure intact
4. Verify attachments present

Update Email Client Settings

After migrating messages, update email client settings (Outlook, Thunderbird, phone) to use WebHostMost servers.

IMAP settings (recommended):

• Incoming Server (IMAP): mail.yourdomain.com or server hostname
• Port: 993
• Security: SSL/TLS
• Username: Full email address
• Password: Email password set during account creation

SMTP settings (outgoing mail):

• Outgoing Server (SMTP): mail.yourdomain.com or server hostname
• Port: 587 (recommended) or 465
• Security: STARTTLS (port 587) or SSL/TLS (port 465)
• Authentication: Yes (use same username/password as incoming)

Note: Email clients can continue accessing old hosting during testing. After verifying WebHostMost email works, switch email client settings. Both old and new email servers work simultaneously during transition.

Phase 6: Switch to WebHostMost and Go Live

Staging tested perfectly. Emails migrated successfully. Time to switch live traffic to WebHostMost.

Final Pre-Launch Checklist

Before switching A record, verify:

Website verification:

• ✅ Staging site loads correctly at https://staging.yourdomain.com
• ✅ All pages accessible and content displays properly
• ✅ Forms submit without errors
• ✅ No broken images or missing resources
• ✅ SSL certificate installed and working (padlock icon)
• ✅ Mobile version displays correctly

Email verification:

• ✅ All email accounts created on WebHostMost
• ✅ IMAPSync migrations completed successfully
• ✅ Test email sent and received via webmail
• ✅ Email client settings updated (Outlook, phone, etc.)

Technical verification:

• ✅ Database credentials updated in config file
• ✅ No hardcoded old URLs in database (for WordPress/CMS)
• ✅ File permissions correct (644 files, 755 folders)
• ✅ Backups exist (still have files and database from old hosting)

DNS verification:

• ✅ Nameservers point to WebHostMost (confirmed via dnschecker.org)
• ✅ MX records configured (email continues working)
• ✅ Any custom DNS records added (TXT, CNAME, etc.)

Switch A Record to WebHostMost

The moment of truth: Switching A record from old hosting IP to WebHostMost IP directs all traffic to your migrated site.

1. Log into Web Control Panel → Domain Management → DNS Management
2. Find A record for main domain (@ or yourdomain.com)
3. Current IP: Shows old hosting IP address
4. Change IP to: Your WebHostMost server IP
   • Find WebHostMost server IP: Check welcome email or visit https://www.webhostmost.com/server-info
5. Click “Save” or “Update Record”
6. A record now points to WebHostMost server

What happens immediately:

• DNS change saves to WebHostMost DNS servers
• New DNS queries return WebHostMost IP
• Visitors start accessing site on WebHostMost

What happens during propagation (1-4 hours):

• Some visitors see site from old hosting (cached DNS)
• Some visitors see site from WebHostMost (updated DNS)
• Both versions identical (you tested thoroughly on staging)
• No errors, no downtime

What happens after propagation:

• All visitors see WebHostMost version
• Old hosting serves no traffic
• Migration complete!

Monitor DNS Propagation and Verify

After switching A record, monitor propagation and verify everything works.

Check DNS propagation:

Visit dnschecker.org

1. Enter your domain
2. Select “A” record type
3. Click “Search”
4. Verify global locations show WebHostMost IP address

Command line verification:

dig A yourdomain.com @8.8.8.8

Output should show WebHostMost server IP address.

Browser testing:

1. Clear browser cache (important!)
2. Visit yourdomain.com
3. Verify site loads correctly
4. Check SSL certificate (should show valid certificate)
5. Test forms, logins, all critical functions

Mobile testing:

1. Open yourdomain.com on mobile phone
2. Verify mobile version displays correctly
3. Test mobile-specific features

During propagation period (24-48 hours):

• Some users may still see old site (DNS cache)
• This is normal and temporary
• Both versions functional (no user impact)

Phase 7: Post-Migration Optimization

Migration complete and site live on WebHostMost. Now optimize and verify ongoing operations.

Verify Backups Running

WebHostMost provides automatic backups on Micro, Pro, and Ultra plans via JetBackup system.

Verify JetBackup:

1. Navigate to File Management → Create/Restore Backups
2. Check if JetBackup available (shows backup schedule)
3. Verify automatic backups configured
4. Review backup retention (how many days backups kept)

Manual backup test:

1. Create manual backup (files + databases)
2. Download backup file to local computer
3. Store securely for extra safety

Backup best practices:

• Keep local copies of critical backups
• Test backup restoration periodically (verify backups actually work)
• Document backup schedule and retention policy

Optimize Site Performance

Fresh start on new hosting provides opportunity for optimization.

Enable LiteSpeed Cache (if using WordPress):

1. Install LiteSpeed Cache plugin from WordPress repository
2. Run optimization wizard
3. Enable Object Cache (Redis) if available
4. Configure image optimization (WebP, lazy loading)
5. Enable CSS/JS minification

Configure CDN (optional):

• Cloudflare (free tier adequate)
• BunnyCDN (pay-as-you-go)
• KeyCDN (affordable rates)

CDN improves global performance by caching content near users worldwide.

Enable HTTP/3: WebHostMost automatically enables HTTP/3 protocol on LiteSpeed Enterprise servers. No configuration needed – provides performance improvements automatically.

Monitor Site for 2 Weeks

Don’t cancel old hosting immediately. Monitor new hosting for 2 weeks first.

Daily monitoring tasks:

• Check site loads correctly
• Verify email sending/receiving works
• Monitor traffic analytics (no unusual drops)
• Review error logs (Control Panel → Error Logs)

Weekly monitoring tasks:

• Test all critical site functions
• Verify backups running successfully
• Check SSL certificate status
• Review performance metrics

After 2-week monitoring period: If everything runs smoothly with no issues, safe to cancel old hosting. Download final backup from old hosting before cancellation as extra safety precaution.

WordPress-Specific Migration: Faster Method

For WordPress sites, plugin-based migration often provides faster, easier process than manual file/database transfer.

WordPress Migration Using Backup Plugins

Popular WordPress backup plugins handle migration automatically:

Recommended plugins:

• All-in-One WP Migration – Easiest, handles everything automatically
• UpdraftPlus – Comprehensive backup features
• Duplicator – Creates installer package

Migration Process with All-in-One WP Migration

Phase 1: Create backup on old hosting

1. Install “All-in-One WP Migration” plugin on old site
2. Activate plugin
3. Go to WordPress admin → All-in-One WP Migration → Export
4. Choose export destination: File
5. Click “Export” button
6. Plugin creates complete backup (.wpress file)
7. Download backup to computer (may be large file)

Phase 2: Install fresh WordPress on staging

Prerequisites: Before WordPress migration, complete DNS configuration from main guide (setup DNS zone, change nameservers to WebHostMost, create staging subdomain).

1. Create staging subdomain: staging.yourdomain.com
2. Install fresh WordPress on staging:
   • Control Panel → Website Management → Advanced Installer Hub
   • Choose WordPress → Custom Install
   • Select staging.yourdomain.com as domain
   • Directory: Leave empty (installs in subdomain root)
   • Complete installation
3. Wait for installation to complete (2-3 minutes)

Phase 3: Restore backup to staging

1. Login to staging WordPress admin: https://staging.yourdomain.com/wp-admin
2. Install “All-in-One WP Migration” plugin on staging site
3. Activate plugin
4. Go to WordPress admin → All-in-One WP Migration → Import
5. Click “Import From” → File
6. Select your .wpress backup file
7. Upload begins (may take 10-30 minutes for large sites)
8. Plugin restores entire site automatically
9. You’ll be logged out – login with original site credentials
10. WordPress automatically updates URLs from old domain to staging.yourdomain.com

Phase 4: Test on staging

Thoroughly test staging.yourdomain.com:

• All pages load correctly
• Plugins active and functional
• Theme displays properly
• Media library intact
• Forms work (contact forms, etc.)
• E-commerce functions (if WooCommerce)

Phase 5: Clone staging to main domain

Once staging tests perfectly:

1. Control Panel → Website Management → Advanced Installer Hub
2. Find WordPress installation (shows staging.yourdomain.com)
3. Click WP icon (WordPress Manager)
4. Click “Clone” button
5. Clone settings:
   • Target domain: Select yourdomain.com
   • Target directory: Leave empty
   • Clone database: ✅ Yes
   • Clone files: ✅ Yes
6. Click “Clone Installation”
7. Wait 3-5 minutes
8. WordPress cloned with URLs automatically updated

Phase 6: Switch A record

Once tested, complete the migration by switching A record to WebHostMost IP (covered in “Switch to WebHostMost and Go Live” section above).

Advantages of plugin method:

• Handles database search/replace automatically
• Includes all files (plugins, themes, uploads)
• Creates portable backup for future migrations
• No manual database editing needed

WordPress Migration Checklist

• ✅ DNS configured (nameservers to WebHostMost, A record to old hosting initially)
• ✅ Staging subdomain created
• ✅ Fresh WordPress installed on staging
• ✅ Backup plugin installed on both old and staging
• ✅ Backup created and downloaded from old site
• ✅ Backup restored to staging subdomain
• ✅ All WordPress functionality tested on staging
• ✅ Staging cloned to main domain
• ✅ A record switched to WebHostMost IP
• ✅ Live site verified working correctly

Common Migration Problems and Solutions

Even careful migrations encounter occasional issues. Here’s how to resolve them.

Issue: “Error Establishing Database Connection”

Symptoms: Website shows database connection error instead of content.

Causes:

• Wrong database credentials in config file
• Database name doesn’t include prefix
• Database not imported correctly
• Database server unavailable

Solutions:

1. Verify database credentials:
   
   • Open wp-config.php (WordPress) or equivalent
   • Check DB_NAME includes prefix: ijodghbk_wordpress (not just wordpress)
   • Verify DB_USER matches database user created
   • Confirm DB_PASSWORD matches exactly (case-sensitive)
   • Ensure DB_HOST is localhost
2. Test database import:
   
   • Control Panel → Databases → SQL Database Manager
   • Click “Manage” next to database
   • Verify tables exist (should see table list)
   • If no tables, database import failed – re-import SQL file
3. Check database user permissions:
   
   • In database manager, verify user has “Full access” to database
   • If not, grant full permissions

Issue: Site Shows Old Content After DNS Switch

Symptoms: Visitors report seeing old site even after A record switched to WebHostMost.

Causes:

• DNS cache at visitor’s ISP or local computer
• Browser cache showing cached version
• CDN cache if using CDN

Solutions:

1. Wait for DNS propagation:
   
   • Full global propagation takes 24-48 hours
   • Check dnschecker.org – if some locations show old IP, still propagating
   • Be patient – this is normal and temporary
2. Clear browser cache:
   
   • Ctrl+Shift+Delete (Windows/Linux)
   • Cmd+Shift+Delete (Mac)
   • Select “All time” and “Cached images and files”
   • Clear cache
3. Flush DNS cache locally:
   
   • Windows: ipconfig /flushdns in Command Prompt
   • Mac: sudo dscacheutil -flushcache in Terminal
   • Linux: sudo systemd-resolve –flush-caches
4. Purge CDN cache (if using Cloudflare/CDN):
   
   • Login to CDN provider
   • Find “Purge Cache” or “Clear Cache”
   • Purge all cached content

Issue: Email Stops Working After Migration

Symptoms: Cannot send or receive email after DNS changes.

Causes:

• MX records not configured on WebHostMost
• Email accounts not created on WebHostMost
• Email client settings still pointing to old server

Solutions:

1. Verify MX records:
   
   • Control Panel → DNS Management
   • Check MX records exist and point to correct server
   • For WebHostMost email: mail.yourdomain.com with priority 10
2. Create email accounts:
   
   • Control Panel → Email Manager → Email Accounts
   • Verify all email accounts exist on WebHostMost
   • Check passwords set correctly
3. Update email client settings:
   
   • Update IMAP/SMTP server to mail.yourdomain.com
   • Verify ports: IMAP 993 (SSL), SMTP 587 (STARTTLS)
   • Test sending and receiving emails
4. Check spam folders:
   
   • New email server may initially land in spam
   • Check spam/junk folders for missing emails
   • Mark as “Not Spam” to train filters

Issue: SSL Certificate Not Installing

Symptoms: Browser shows “Not Secure” warning, no padlock icon.

Causes:

• SSL certificate not generated yet
• DNS not propagated (certificate validation requires DNS)
• Certificate request pending

Solutions:

1. Wait for automatic installation:
   
   • WebHostMost auto-installs Let’s Encrypt certificates
   • Wait 10-15 minutes after DNS propagation
   • Certificate validation requires accessible domain
2. Manual SSL request:
   
   • Control Panel → Security Management → SSL Certificates
   • Select “Get automatic certificate from ACME Provider” tab
   • Choose domain(s) for certificate
   • Click “Save”
   • Wait 5-10 minutes for certificate generation
3. Verify DNS accessibility:
   
   • Visit http://yourdomain.com/.well-known/ (note: http, not https)
   • If this loads, DNS is accessible for certificate validation
   • If error 404, that’s fine – confirms server accessible
4. Enable Force HTTPS:
   
   • After certificate installs, enable HTTPS redirect
   • Security Management → Force HTTPS Redirect: ON
   • All HTTP traffic automatically redirects to HTTPS

Issue: Website Loads Slowly After Migration

Symptoms: Site loads but takes longer than expected, feels sluggish.

Causes:

• Caching not configured
• Images not optimized
• External resources slow
• Server resources insufficient

Solutions:

1. Enable LiteSpeed Cache (WordPress):
   
   • Install LiteSpeed Cache plugin
   • Enable page cache and object cache
   • Configure image optimization
   • See PageSpeed optimization guide
2. Optimize images:
   
   • Enable WebP conversion in LiteSpeed Cache
   • Enable lazy loading
   • Compress large images
3. Check external resources:
   
   • Open browser Developer Tools (F12)
   • Go to Network tab
   • Reload page and identify slow-loading resources
   • Consider removing or replacing slow external scripts
4. Upgrade hosting plan if needed:
   
   • Check resource usage in Control Panel
   • If consistently hitting limits, upgrade to higher plan
   • Contact support for resource review

Why WebHostMost Migration Is Different

WebHostMost migration process emphasizes zero downtime and safety through staging-first methodology.

Architectural Advantages

LiteSpeed Enterprise infrastructure:

• Server-level caching (faster than plugin-based caching)
• HTTP/3 protocol support (automatic performance improvement)
• Native PHP optimization (faster WordPress execution)
• NVMe SSD storage (3-5x faster than traditional SSD)

DirectAdmin control panel:

• Intuitive interface (easier than cPanel for beginners)
• Integrated database management (simplified imports)
• Built-in IMAPSync (professional-grade email migration)
• Staging environment tools (one-click WordPress cloning)

Free professional migration:

• Micro, Pro, Ultra plans (1-3 year) include free migration service
• Technical team handles entire migration
• Zero downtime guarantee
• No learning curve required

Ongoing Support

24/7 technical support:

• Email support (response within hours)
• Support ticket system
• Forum and documentation
• Webbee AI assistant (instant answers to common questions)

Frequently Asked Questions About Website Migration

Will my site go down during migration?

No downtime occurs when following zero-downtime staging methodology described in this guide. Old site stays live throughout entire process because: DNS zone configures with A record pointing to old hosting IP (old site continues serving visitors), staging subdomain creates parallel testing environment invisible to public (testing happens safely without affecting live site), nameserver change happens while old site still live (DNS controls transfer to WebHostMost but traffic stays on old hosting), and A record switches only after confirming everything works perfectly on staging (controlled transition at your discretion). Only potential downtime comes from DNS propagation period (1-4 hours) when some visitors see old site and others see new site, but both versions are identical and functional. Rushed migrations without staging cause downtime – proper methodology eliminates this risk entirely.

Can I migrate email without losing messages?

Yes, IMAPSync technology copies all email messages from old hosting to WebHostMost without deleting originals or causing message loss. Process works by connecting to old email server via IMAP protocol, reading all messages and folder structure, copying messages to WebHostMost servers, preserving folder organization and read/unread status, and keeping originals on old server untouched (messages exist on both servers during migration). This means email continues functioning on old hosting during migration – no interruption to email service. After migration completes and verification confirms all messages transferred successfully, optionally delete messages from old hosting or keep as backup. Migration handles unlimited message volume and preserves attachments, folder structure, and message flags. Large mailboxes (10GB+) may require overnight migration but run in background without user intervention. WebHostMost IMAPSync tool is professional-grade solution included free with all hosting plans.

What if something goes wrong during migration?

Staging methodology provides multiple safety nets preventing catastrophic failures. If issues arise during testing on staging.yourdomain.com, your live site at yourdomain.com remains completely unaffected – old hosting continues serving visitors normally. You have time to fix staging issues without pressure or downtime. Common issues like database connection errors, broken URLs, or missing files solve through configuration adjustments on staging before going live. Backup files from old hosting remain safe and accessible throughout process – if complete restart needed, re-upload files and re-import database. A record change is reversible – if problems emerge after switching to WebHostMost, change A record back to old hosting IP immediately (propagates in 1-4 hours). WebHostMost support team available 24/7 to troubleshoot migration problems via support ticket system. For eligible plans with free professional migration service, technical team handles everything and guarantees successful migration. Worst-case scenario: Keep old hosting active, use WebHostMost for fresh start with gradual content migration instead of complete site move.

Do I need technical knowledge to migrate?

Basic computer skills sufficient for successful self-migration following this guide step-by-step. Required skills include: uploading files via web interface (similar to uploading email attachments), editing text configuration files (simple copy/paste of database credentials), following sequential instructions carefully, and accessing control panels (similar to logging into email). No programming, command line, or server administration knowledge required for standard WordPress or simple site migration. Tasks like creating databases, uploading files, and configuring DNS happen through point-and-click web interfaces designed for non-technical users. WebHostMost documentation provides screenshots and detailed explanations for every step. Webbee AI assistant answers questions and guides through confusing parts. For users uncomfortable with any technical tasks, WebHostMost offers free professional migration service on eligible plans – technical team handles everything while you focus on business. Alternative: Hire freelancer or agency for migration assistance if not covered by free migration service. Migration is learnable process, not requiring special expertise, but professional options exist for those preferring hands-off approach.

Ready to migrate with confidence? Use promo code WELCOME_WHM for 20% off any hosting plan including free professional migration service on eligible plans!

💪 Need help with migration? Open support ticket for free professional migration assistance or technical support.

👉 View WebHostMost hosting plans and start your zero-downtime migration today.

Have you seen our other articles?