Transitioning from aaPanel Infrastructure

The aaPanel migration tool is designed to handle the complex port-based webserver configurations often found in aaPanel environments. Follow this manual for a successful transition.

Step 1: Environment Audit

Check the source aaPanel server to identify which webserver engine is active. Note the ports: 8080 (Apache) or 8081 (OpenLiteSpeed). BoostonCP will attempt to auto-detect this, but knowing it helps in verification.

Step 2: Establishing the aaPanel Sync

  1. Go to Migration Center > aaPanel Importer.
  2. Provide the Remote IP and SSH Credentials.
  3. Click "SCAN ENVIRONMENT". BoostonCP will read the /www/server/panel data to index your websites and databases.
[IMAGE_PLACEHOLDER: aaPanel Scan - Screenshot showing the "Scanning remote environment" progress.]

Step 3: Executing the Smart Mapper

  1. Select the websites you want to migrate from the detected list.
  2. Click "EXECUTE MIGRATION".

The Smart Mapper will now begin:

  • Detecting PHP versions and falling back to the closest local match if necessary.
  • Extracting assets and removing aaPanel-specific path locks (like .user.ini).
  • Automatically recovering the MySQL root password from db_root_pwd.pl.

Step 4: WordPress Compatibility Fix

If you are migrating WordPress sites, BoostonCP executes an automated config re-sync. It updates the DB_HOST in your wp-config.php to "localhost," ensuring your site connects to the database instantly after the move.

Step 5: Final Stability Check

Wait for the 20-second "Cool-down" period after each account migration. This ensures that the system services have successfully reloaded and the neural link is stable.