Migration Agent Troubleshooting Guide

Migration Monkey agents are intentionally small: a source agent analyzes and sends, while a destination agent receives and imports. Most failures come from token mismatch, WAF rules, PHP limits, filesystem permissions, or database privileges.

Invalid token

Use the key= value from the agent download URL. Do not use your account password, cPanel password, or database password. Tokens are per-job and should not be reused across migrations.

Destination agent unreachable

Check that the destination URL is public to the source server, not only your browser. If Cloudflare, Sucuri, or a strict proxy is active, allow the temporary agent path for the migration window and avoid caching the agent response.

Chunk upload errors

Chunk errors usually mean a WAF blocked a POST, the destination folder is not writable, or PHP request/body limits are too low. Place the generated .user.ini, confirm permissions, then rerun the transfer. Matching files can be skipped by size and SHA-256.

Database import errors

Confirm the destination database exists, the user can create/drop/alter/insert tables, and the character set supports the source data. For WordPress, verify the source wp-config.php table prefix before import.