Source and destination servers or mailbox providers transfer files, databases, and messages directly while Migration Monkey records progress, warnings, hashes, consent, and credit usage.
New migration
Create an account, confirm data ownership, connect both endpoints, and run a migration for websites, apps, or mailboxes.
- 1Account
- 2App profile
- 3Source
- 4Destination
- 5Review and migrate
Account creation and data authorization
Users must create an accountable workspace and confirm they own or are authorized to migrate the data before any script runs.
App profile
Choose the stack you are moving.
Waiting for install folder scan.
Source endpoint
Where the current site lives.
Standard host
Clean path
Normal direct transfer. The source and destination agents can reach each other without a proxy-specific bypass.
Hard-host and mailbox modes add scoped checks for WAFs, origin locks, export-only plans, OAuth/app-password access, IMAP throttling, cache purge, and assisted cleanup when the source cannot expose full access.
We can remember label, host, port, username, app path, and preferred method. Passwords, private keys, and one-time tokens are encrypted for this migration only.
Folder ready for scan
Destination endpoint
Where the app will be migrated.
Saved destination profiles can be reused later, but migration secrets are entered again for each job and encrypted before the agent handshake.
Secrets ready for per-job encryption
Direct endpoint-to-endpoint
We only orchestrate. Your servers or mailbox providers talk directly.
Source endpoint
Not set
Source to destination channel
TLS 1.3 + signed job token
Destination endpoint
Not set
No custody
Control plane never touches payloads.
Captures site chunks locally or reads mailbox folders through the approved provider auth path, then sends directly to the destination.
Creates or validates the destination, receives direct transfer data, restores app paths or writes messages into the target mailbox.
Stores progress, consent, hashes, and error telemetry. Website payloads do not land here; mailbox relay storage is opt-in only for assisted email jobs.
Passwords and tokens are never saved in endpoint profiles; they are encrypted for the active migration handshake only.
Domain and rewrite plan
Apply same-domain moves, temp domains, cutovers, and serialized-safe WordPress URL replacement to the migration job.
This is billed as a route add-on when the base-install trial qualifies as free.
Enter the real source and destination route before creating the job.
Endpoint details required
Recent migrations
| ID | Application | Source | Destination | Status | Progress | Credits | Action |
|---|---|---|---|---|---|---|---|
| No jobs | Create a migration job to generate its source and destination agents. | ||||||
Migration troubleshooting
Common blockers get actionable fix popups so operators can recover without guessing.
Start is blocked until the account owner confirms authorization to move the data.
Filesystem permissions, disabled plugin editor, or ModSecurity can block the helper plugin.
Wrong owner/group or jailed path prevents the destination agent from writing restored files.
Large dumps need chunked import, extended packet size, or a direct database socket path.
The destination runtime does not match the detected app requirements.
Strict WAF rules can challenge the signed endpoint handshake or callback telemetry.
Cloudflare can challenge agent paths, cache restore checks, or block origin-only endpoints.
Sucuri can mask the hosting IP and block temporary restore routes without an allowlist.
Use signed bypass, origin lock awareness, and cache purge for Help4-hosted migrations.
Export-only plans need XML, media reconciliation, and assisted cleanup instead of full DB capture.
Locked hosts need admin/plugin capture, host backups, or owner-assisted migration review.
Gmail, Microsoft 365, Yahoo, Zoho, cPanel, and free mailbox moves need the right OAuth, app-password, quota, and IMAP limits.