Migration Guide - Webinoly

Overview

This guide covers various migration scenarios when moving to Webinoly or between Webinoly servers.

To Webinoly

Migrate from other control panels

Between Servers

Move between Webinoly servers

WordPress

WordPress-specific migration

Databases

Database migration strategies

Migrating to Webinoly

From cPanel/Plesk

Migrating from traditional control panels to Webinoly:

Prerequisites

Prepare New Server

Fresh Ubuntu 24.04 or 22.04 installation
Minimum 512 MB RAM (1GB+ recommended)
Root access via SSH

Install Webinoly

wget -qO weby qrok.es/wy && sudo bash weby

Create Site Structure

# For each site, create matching structure
sudo site example.com -wp  # or -php, -html

Migration Process

1. Export from cPanel/Plesk

# In cPanel, create full backup
# Download backup files via:
# - Backup Wizard
# - File Manager
# - FTP/SFTP

2. Transfer Files

# From old server to new
rsync -avz -e ssh user@old-server:/home/username/public_html/ \
  /var/www/example.com/htdocs/

# Or use SCP
scp -r user@old-server:/home/username/public_html/* \
  /var/www/example.com/htdocs/

# Set correct permissions
sudo chown -R www-data:www-data /var/www/example.com/
sudo find /var/www/example.com/htdocs/ -type d -exec chmod 755 {} \;
sudo find /var/www/example.com/htdocs/ -type f -exec chmod 644 {} \;

3. Export Databases

# On old server (via phpMyAdmin or command line)
mysqldump -u username -p database_name > database_backup.sql

# Transfer to new server
scp database_backup.sql user@new-server:/tmp/

4. Import to Webinoly

# Import database
sudo db -import=database_name,/tmp/database_backup.sql

# Update WordPress wp-config.php if needed
sudo nano /var/www/example.com/wp-config.php

5. Update DNS

# After testing, update DNS records
# Point A record to new server IP
# Wait for propagation (24-48 hours)

Keep your old server running until DNS propagation completes and you’ve verified everything works correctly.

From Apache Servers

Migrating from an Apache-based setup:

Key Differences

Configuration Files

Apache: .htaccess files
NGINX: Server block configurations in /etc/nginx/sites-available/

NGINX doesn’t use .htaccess. URL rewrites need converting to NGINX syntax.

Rewrite Rules

Apache .htaccess rules need conversion:Apache:

RewriteEngine On
RewriteRule ^old-page$ /new-page [R=301,L]

NGINX:

rewrite ^/old-page$ /new-page permanent;

Migration Steps

1. Analyze Apache Configuration

# On old server, identify special configurations
cat /etc/apache2/sites-available/example.com.conf
cat /var/www/html/.htaccess

2. Convert Rewrite Rules Use online converters or manual conversion:

winginx.com/en/htaccess - Apache to NGINX converter
nginx.viraptor.info - Rewrite rule converter

3. Create Custom NGINX Configuration

# Create custom config for site
sudo nano /etc/nginx/apps.d/example.com-custom.conf

# Add converted rules
# Example:
location /old-path {
    return 301 /new-path;
}

# Include in site config is automatic
# Test configuration
sudo nginx -t

# Reload NGINX
sudo service nginx reload

From Other LEMP Stacks

Migrating from manual LEMP or other automated stacks:

File Migration

# Copy files
sudo rsync -avz /old/path/to/site/ /var/www/example.com/htdocs/

# Fix permissions
sudo chown -R www-data:www-data /var/www/example.com/

Database Migration

# Export from old
sudo mysqldump -u root -p database_name > db_backup.sql

# Import to Webinoly
sudo mysql -u root -p < db_backup.sql

# Or use Webinoly command
sudo db -import=database_name,db_backup.sql

PHP Version Matching

# If old site uses specific PHP version
sudo stack -php=8.2  # Install needed version

# Create site with that version
sudo site example.com -php=8.2

Server to Server Migration

Between Webinoly Servers

Migrating between two Webinoly installations is straightforward:

Full Server Migration

1. Backup Old Server

# On old server
sudo backup -all

# This creates:
# - All site files
# - All databases
# - All configurations

2. Transfer Backups

# Direct transfer
sudo rsync -avz -e ssh /var/webinoly/backups/ \
  user@new-server:/tmp/backups/

# Or compress and transfer
sudo tar -czf webinoly-full-backup.tar.gz /var/webinoly/backups/
scp webinoly-full-backup.tar.gz user@new-server:/tmp/

3. Prepare New Server

# On new server
# Install Webinoly with same components
wget -qO weby qrok.es/wy && sudo bash weby

# Install same PHP versions
sudo stack -php=8.4
sudo stack -php=8.2

# Install same optional components
sudo stack -redis

4. Restore All Sites

# On new server
sudo restore -all

# Or restore individual sites
sudo restore example.com
sudo restore site2.com

5. Verify and Update DNS

# Test sites work
curl -H "Host: example.com" http://localhost

# Update DNS records
# Point domains to new server IP

Single Site Migration

Backup Specific Site

# Old server
sudo backup example.com

# Backup includes:
# - Site files
# - Database
# - NGINX configuration
# - SSL certificates

Transfer and Restore

# Transfer
scp /var/webinoly/backups/example.com-*.tar.gz \
  user@new-server:/tmp/

# New server - restore
sudo site example.com -wp  # Create site structure first
sudo restore example.com -backup=/tmp/example.com-*.tar.gz

Version Compatibility

Current Webinoly version: 1.20.0 (from /home/daytona/workspace/source/lib/general:7)Server version: 1.12

Upgrading During Migration

# On old server (before backup)
sudo webinoly -update

# Verify version
sudo webinoly -info

# Then proceed with backup
sudo backup -all

WordPress Migration

WordPress-Specific Steps

Standard WordPress Site

1. Backup Current Site

# Using WordPress plugins (on old server)
# - UpdraftPlus
# - All-in-One WP Migration
# - Duplicator

# Or command line
sudo wp db export backup.sql --path=/var/www/html
tar -czf wordpress-files.tar.gz /var/www/html/

2. Create Site on Webinoly

# New server
sudo site example.com -wp

3. Transfer and Restore

# Transfer files
scp wordpress-files.tar.gz backup.sql user@new-server:/tmp/

# New server - extract
cd /var/www/example.com/htdocs/
sudo tar -xzf /tmp/wordpress-files.tar.gz --strip-components=1

# Import database
sudo db -import=wordpress_db,/tmp/backup.sql

# Update wp-config.php
sudo nano wp-config.php

4. Update URLs

# If domain stays same, no changes needed

# If domain changes
sudo wp search-replace 'old-domain.com' 'new-domain.com' \
  --path=/var/www/example.com/htdocs/

# Or use SQL
sudo mysql -u admin -p wordpress_db
UPDATE wp_options SET option_value = 
  REPLACE(option_value, 'http://old-domain.com', 'http://new-domain.com');

WordPress Multisite

Migration Considerations

Subdomain Multisite

# Create multisite structure
sudo site example.com -wp -multisite=subdomain

# Transfer files and database
# Update wp-config.php and .htaccess

# Update network URLs
sudo wp search-replace 'old-domain.com' 'new-domain.com' \
  --network --path=/var/www/example.com/htdocs/

Domain Mapping

If using domain mapping plugin:

# Update domain mapping tables
UPDATE wp_domain_mapping SET domain = 'new-domain.com' 
  WHERE domain = 'old-domain.com';

# Update site URLs
UPDATE wp_blogs SET domain = 'new-domain.com' 
  WHERE domain = 'old-domain.com';

WooCommerce Sites

Additional Steps

# 1. Put site in maintenance mode
sudo wp maintenance-mode activate \
  --path=/var/www/example.com/htdocs/

# 2. Clear all caches before backup
sudo site example.com -cache=clear

# 3. Migrate as normal

# 4. After migration, regenerate thumbnails
sudo wp media regenerate --yes \
  --path=/var/www/example.com/htdocs/

# 5. Clear all caches
sudo wp cache flush --path=/var/www/example.com/htdocs/
sudo site example.com -cache=clear

# 6. Disable maintenance mode
sudo wp maintenance-mode deactivate \
  --path=/var/www/example.com/htdocs/

Database Migration

MySQL/MariaDB Migration

Same Database Engine

# Export all databases
sudo mysqldump -u root -p --all-databases > all-databases.sql

# Or specific database
sudo mysqldump -u root -p database_name > database.sql

# Transfer
scp all-databases.sql user@new-server:/tmp/

# Import
sudo mysql -u root -p < /tmp/all-databases.sql

Between MySQL and MariaDB

# Export from MySQL
mysqldump -u root -p --compatible=mariadb database_name > db.sql

# Transfer and import to MariaDB
sudo mariadb -u root -p database_name < db.sql

# Or use Webinoly
sudo db -import=database_name,db.sql

Large Database Migration

For databases over 1GB:

# Compress during export
sudo mysqldump -u root -p database_name | gzip > db.sql.gz

# Transfer compressed
scp db.sql.gz user@new-server:/tmp/

# Decompress and import
gunzip < /tmp/db.sql.gz | sudo mysql -u root -p database_name

External Database

Migrating to external database service (AWS RDS, etc.):

# Create site with external DB
sudo site example.com -wp \
  -external-db=[admin,password,rds-host.amazonaws.com:3306]

# Import data
sudo mysql -h rds-host.amazonaws.com -P 3306 \
  -u admin -p database_name < backup.sql

SSL Certificate Migration

Let’s Encrypt Certificates

Between Webinoly Servers

# Old server - backup certificates
sudo tar -czf letsencrypt-backup.tar.gz /etc/letsencrypt/

# Transfer
scp letsencrypt-backup.tar.gz user@new-server:/tmp/

# New server - restore
sudo tar -xzf /tmp/letsencrypt-backup.tar.gz -C /

# Renew to ensure they work
sudo certbot renew

Fresh Certificates

# Let Webinoly generate new certificates
sudo site example.com -ssl=on

# Automatic and recommended approach

Custom SSL Certificates

# Install custom certificate
sudo site example.com -ssl=custom \
  -ssl-crt=/path/to/certificate.crt \
  -ssl-key=/path/to/private.key

Post-Migration Checklist

Verify All Sites

# Check site accessibility
curl -I https://example.com

# Test SSL
openssl s_client -connect example.com:443

# Check all pages work

Test Functionality

Forms submission
Login/authentication
Database connectivity
Email sending
API endpoints
Media uploads

Performance Checks

# Enable caching
sudo site example.com -cache=on

# Monitor logs
sudo log example.com -watch

# Check resource usage
htop

Enable Backups

# Setup automated backups
sudo backup -auto=on

# Configure remote backup
sudo backup -remote=s3

Update DNS

Update A records
Update AAAA records (if IPv6)
Update MX records (if mail server)
Verify propagation

Monitoring

# Configure email alerts
sudo webinoly [email protected]

# Monitor logs
sudo log example.com -watch

Rollback Plan

Always have a rollback plan before migration.

Quick Rollback Steps

If Issues Occur

Keep Old Server Running

# Don't delete old server until fully verified
# Keep it running for at least 7 days

DNS Rollback

# Point DNS back to old server IP
# Update A records immediately
# TTL should be low (300s) during migration

Communicate Downtime

# If issues persist, communicate with users
# Set up maintenance page

Migration Tools & Scripts

Useful Scripts

Pre-Migration Check Script

#!/bin/bash
# pre-migration-check.sh

echo "=== Pre-Migration Checklist ==="
echo "1. Disk Space:"
df -h
echo ""
echo "2. Database Size:"
mysql -u root -p -e "SELECT table_schema AS 'Database', 
  ROUND(SUM(data_length + index_length) / 1024 / 1024, 2) AS 'Size (MB)' 
  FROM information_schema.TABLES GROUP BY table_schema;"
echo ""
echo "3. PHP Version:"
php -v
echo ""
echo "4. Sites:"
ls -la /var/www/

Post-Migration Verification

#!/bin/bash
# verify-migration.sh

echo "=== Post-Migration Verification ==="
for site in $(ls /var/www/); do
    echo "Checking $site..."
    curl -I https://$site
    echo ""
done

Common Migration Issues

File Permissions Issues

Problem: Files not accessible or uploadableSolution:

sudo chown -R www-data:www-data /var/www/example.com/
sudo find /var/www/example.com/htdocs/ -type d -exec chmod 755 {} \;
sudo find /var/www/example.com/htdocs/ -type f -exec chmod 644 {} \;

Database Connection Errors

Problem: WordPress can’t connect to databaseSolution:

# Verify database exists
sudo mysql -u root -p -e "SHOW DATABASES;"

# Check wp-config.php credentials
sudo nano /var/www/example.com/wp-config.php

# Test connection
sudo mysql -u dbuser -p database_name

Mixed Content Warnings

Problem: HTTPS site loading HTTP resourcesSolution:

# Update URLs in database
sudo wp search-replace 'http://example.com' 'https://example.com' \
  --path=/var/www/example.com/htdocs/

# Or use Really Simple SSL plugin

Permalink Issues

Problem: 404 errors on WordPress pagesSolution:

# Flush permalinks
sudo wp rewrite flush --path=/var/www/example.com/htdocs/

# Or reset in WordPress admin:
# Settings → Permalinks → Save Changes

Support During Migration

Documentation

Detailed command reference

Community

Get migration help from community

Premium Support

Professional migration assistance

GitHub Issues

Report migration problems

Additional Resources

​Overview

To Webinoly

Between Servers

WordPress

Databases

​Migrating to Webinoly

​From cPanel/Plesk

​Prerequisites

​Migration Process

​From Apache Servers

​Key Differences

​Migration Steps

​From Other LEMP Stacks

​File Migration

​Database Migration

​PHP Version Matching

​Server to Server Migration

​Between Webinoly Servers

​Full Server Migration

​Single Site Migration

​Version Compatibility

​WordPress Migration

​WordPress-Specific Steps

​Standard WordPress Site

​WordPress Multisite

​WooCommerce Sites

​Database Migration

​MySQL/MariaDB Migration

​Same Database Engine

​Between MySQL and MariaDB

​Large Database Migration

​External Database

​SSL Certificate Migration

​Let’s Encrypt Certificates

​Custom SSL Certificates

​Post-Migration Checklist

​Rollback Plan

​Quick Rollback Steps

​Migration Tools & Scripts

​Useful Scripts

​Common Migration Issues

​Support During Migration

Documentation

Community

Premium Support

GitHub Issues

Build docs developers (and LLMs) love

Overview

Migrating to Webinoly

From cPanel/Plesk

Prerequisites

Migration Process

From Apache Servers

Key Differences

Migration Steps

From Other LEMP Stacks

File Migration

Database Migration

PHP Version Matching

Server to Server Migration

Between Webinoly Servers

Full Server Migration

Single Site Migration

Version Compatibility

WordPress Migration

WordPress-Specific Steps

Standard WordPress Site

WordPress Multisite

WooCommerce Sites

Database Migration

MySQL/MariaDB Migration

Same Database Engine

Between MySQL and MariaDB

Large Database Migration

External Database

SSL Certificate Migration

Let’s Encrypt Certificates

Custom SSL Certificates

Post-Migration Checklist

Rollback Plan

Quick Rollback Steps

Migration Tools & Scripts

Useful Scripts

Common Migration Issues

Support During Migration