How To Use Migration Monkey For Website And Email Migrations

Migration Monkey is designed for site owners, agencies, hosts, and operators who need a repeatable way to move websites and mailboxes without sending customer payload archives through the control plane. The workflow starts with authorization, detects the app or mailbox profile, estimates credits, then guides the source and destination through a direct transfer path.

1. Request Access Or Sign In

The public site is behind an account gate while the platform is in controlled preview. Users sign in, request access, or use Google identity for account access. The login screen avoids prefilled owner data and keeps the platform behind a paywall until access is approved.

Migration Monkey dark-mode access gate for controlled preview website migrations — Controlled preview access gate for Migration Monkey accounts.

2. Create A Workspace And Confirm Authorization

Every migration should start with an accountable workspace and data ownership confirmation. Migration Monkey records consent and job metadata while files, databases, and mailbox messages move directly between customer-controlled endpoints whenever possible.

Migration Monkey workspace creation and data authorization screen — Workspace creation, owner email, legal company, security role, and data-authorization consent.

3. Choose Or Detect The App

Pick WordPress, Magento, Joomla, Drupal, PrestaShop, OpenCart, Laravel, Node.js, Nextcloud, email, or another profile. For real jobs, the analyzer should inspect the install folder or mailbox route instead of pricing every migration as if it were the same stack.

Migration Monkey app detection, source endpoint, destination endpoint, and credit estimate — Application profile selection, source and destination endpoints, direct server-to-server route, and credit estimate.

4. Enter Endpoint Details Without Saving Passwords

Source and destination server profiles can be saved as labels, hosts, usernames, app paths, and preferred methods. Passwords, private keys, database passwords, OAuth tokens, and one-time secrets are entered per migration and should not be stored in reusable endpoint profiles.

Migration Monkey per-migration secret handling showing saved endpoint fields and never-saved passwords — Reusable endpoint labels are allowed; passwords and one-time secrets are not saved in the profile.

5. Review Credits, Warnings, And Logs

The credit estimate changes by app type, file size, database size, mailbox route, domain rewrite, service level, source constraints, and no-custody transfer discount. Operators should review warnings for Cloudflare, Sucuri, Help4.net proxy, WordPress.com export-only plans, email throttling, database imports, and runtime mismatches before starting the move.