# Migration Types

Quick Comparison
1. Automatic Migrations
2. Manual Migrations
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.

Automatic migrations — initiated by clients; fully handled via plugin or FTP with stop/retry and live logs.
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: Use the plugin method when WP Admin access is available. It offers the 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 the source server
Downloads WordPress files and database
Useful when the plugin method is not feasible
Requires FTP credentials and path to the 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 plugin or FTP 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 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 is needed.

# When to Use Manual Migration

Choose manual migration when:

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

# Starting a Manual Migration

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

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

After creating the migration, the Migration Details screen shows FTP credentials and upload instructions.

Upload required files:
- Connect to the provided FTP account
- 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
Verify uploads:
- Click the Verify button to confirm files are present and valid
- Expected result: Verification status changes to Verified, and Continue Import becomes enabled
Continue migration:
- Once verification succeeds, click Continue Import
- The migration proceeds automatically through all remaining steps
- Expected result: Steps advance and finish with status Completed

# File Upload Requirements

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

Include all files from the WordPress root directory
Preserve directory structure (wp-content, wp-includes, etc.)
File must be named: wordpress-files.zip

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 is automatically removed after migration completes
All uploaded files in the temporary directory are 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

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

Migration Types