Migration Types

• Quick comparison
• 1. Automatic Migrations
  • Import Methods
  • Automatic Migration Features
  • Key Differences from Manual Migrations
• 2. Manual Migrations
  • When to Use Manual Migration
  • Starting a Manual Migration
  • File Upload Requirements
  • Important Notes
• Method Comparison
• Related Documentation

PanelAlpha supports two types of migrations, each designed for different scenarios and levels of control.

Quick comparison

• Automatic (client-initiated) — fastest path with plugin or FTP; supports stop/retry; minimal admin effort.
• Manual (admin-initiated) — best for failed imports, large sites, or when you want to verify uploads before continuing.

1. Automatic migrations — initiated by clients; fully handled via plugin or FTP with stop/retry and live logs.
2. Manual migrations — initiated by admins; rely on uploaded files and give full control for edge cases and failed retries.

1. Automatic Migrations

Automatic migrations are initiated by clients through the Client Area when they choose to import an existing WordPress instance.

Import Methods

Note: When to choose the plugin method Use when WP Admin access is available or client can install a plugin quickly. Best reliability and least friction.

Simple Method (Plugin)

The plugin-based method offers two approaches:

With login credentials:

• PanelAlpha logs into WordPress admin automatically
• Installs the migration plugin
• Runs the migration automatically
• Fully automated file and database transfer
• Real-time progress updates
• Recommended for most scenarios

Manual plugin installation:

• Client downloads and installs the plugin manually

• Client activates the plugin in WordPress admin

• Plugin connects to PanelAlpha

• Initiates migration process

• Fully automated after plugin activation

Advanced Method (FTP/SFTP)

The FTP/SFTP method provides direct access:

• Direct FTP/SFTP connection to source server

• Downloads WordPress files and database

• Useful when plugin method is not feasible

• Requires FTP credentials and path to WordPress installation

Automatic Migration Features

• Real-time progress tracking: See which step is currently executing
• Stop capability: Ability to stop an automatic migration at any time
• Source details: View FTP/plugin connection details used for import
• Live logs: Real-time log updates as migration progresses
• Retry on failure: Can retry failed automatic migrations

Key Differences from Manual Migrations

Area	Automatic	Manual
Initiated by	Client (self-serve)	Admin (after failure or by choice)
Stop mid-process	✅ Yes (Stop button)	❌ No once processing starts
Source credentials shown	✅ Yes (plugin/FTP)	❌ No (files uploaded)
Cleanup	Auto-removes plugin/temp credentials	Removes temp FTP after finish
Best when	Standard sites, client-led imports	Large sites, recover failed imports, more control

Note: Manual vs Automatic Manual migrations give admins control after uploads are in place; once processing starts, they must run to completion (no Stop button).

2. Manual Migrations

Manual migrations are initiated by administrators when automatic imports fail or when more control over the migration process is needed. This type allows administrators to:

• Handle failed client migrations
• Manually upload files and database backups
• Verify data before proceeding with migration steps
• Retry specific steps independently

When to Use Manual Migration

Choose manual migration when:

• The Client Area import failed and you want an admin to continue the migration
• You want the admin team to handle the file/database upload steps
• You need more control over the process (verify files before continuing, review logs, retry/mark successful)
• Working with large sites that may timeout during automatic transfer
• Source server has restrictions that prevent automatic methods

Starting a Manual Migration

To initiate a manual migration of a WordPress website, follow these steps:

1. Click the Manual Migration button at the top of the Migrations page.

2. Fill out the form:
   • Select User: Choose the user who will own the imported instance
   • Select Service: Choose the service (plan and hosting server) where the instance will be created
   • Click Create Instance and Initiate Import

3. After creating the migration, you'll see the Migration Details screen showing FTP credentials and upload instructions.

4. Upload required files:

   • Connect to the provided FTP account using an FTP client
   • Upload two files to the temporary directory:
     • wordpress-files.zip - ZIP archive of all WordPress files
     • database.sql, database.sql.zip or database.sql.tar.gz - Database dump file

5. Verify uploads:

   • Click the Verify button to confirm files are present and valid
   • PanelAlpha will check file existence and basic integrity
   • Expected result: Verification status changes to Verified, and Continue Import becomes enabled

6. Continue migration:

   • Once verification succeeds, click Continue Import
   • The migration will proceed automatically through all remaining steps
   • Expected result: Steps advance through Run Migration and finish with status Completed

File Upload Requirements

When uploading files for a manual migration, you need to provide:

1. WordPress Files: A ZIP archive containing all WordPress files

• Include all files from the WordPress root directory
• Preserve the directory structure (wp-content, wp-includes, etc.)
• File must be named: wordpress-files.zip
• Maximum recommended size: depends on your hosting server limits

2. Database Backup: An SQL dump of the WordPress database

• Export using phpMyAdmin, WP-CLI, mysqldump, or your preferred tool
• File must be named: database.sql (or database.sql.gz if compressed)
• Ensure export includes all WordPress tables
• Gzip compression is supported and recommended for large databases

Important Notes

• Large file uploads may take significant time depending on connection speed
• Ensure your ZIP archive is not corrupted before uploading (test extraction locally)
• The temporary FTP account will be automatically removed after migration completes
• All uploaded files in the temporary directory will be cleaned up automatically

Method Comparison

Feature	Automatic (Plugin)	Automatic (FTP)	Manual
Initiated by	Client	Client	Administrator
Source access	WP Admin or Plugin	FTP/SFTP	Admin uploads files
Can be stopped	✅ Yes	✅ Yes	❌ No (after upload stage)
File transfer	Automatic	Automatic	Manual upload
Best for	Most migrations	No WP admin access	Failed migrations, large sites
Skill level	Beginner	Intermediate	Advanced
Control level	Low	Medium	High

Related Documentation

• Import Process - Understand the import steps
• Managing Migrations - Monitor and manage migrations
• Client Area: Importing Existing Instance - Client-side import guide