Terms Of Service
These terms govern access to Migration Monkey, including website migrations, mailbox migrations, application detection, credit estimates, paid credit packs, coupons, endpoint agents, and support workflows.
Data ownership and authority
You confirm that you own the website, mailbox, email messages, application files, databases, media, customer records, logs, and configuration data being migrated, or that the owner, controller, or authorized administrator has given you written authority to perform the migration.
Each job requires a separate confirmation that you control or are authorized to use both endpoints and that you approve reads from the source and writes or replacements inside the destination folder where you install the job's destination agent.
No payload custody by default
Migration Monkey coordinates direct server-to-server and mailbox-to-mailbox transfers by default. The source endpoint sends files, database chunks, or email messages directly to the destination endpoint or provider. Migration Monkey does not receive, store, proxy, or back up customer payloads unless you explicitly choose an assisted encrypted relay path for a specific job.
Endpoint scripts and provider access
You authorize temporary source and destination scripts, plugins, OAuth grants, or agents to inspect application versions, mailbox metadata, folder and message counts, package chunks locally, restore to the destination, and report progress or errors back to the control plane.
Generated website agents are scoped to the directory where each agent is installed. Before a website payload moves, the source agent challenges the destination agent and verifies the exact job, destination role, write scope, and job-secret proof. Agent credentials expire after seven days unless you rotate them, which invalidates prior agents and endpoint proofs.
You are responsible for removing temporary access, plugins, agents, test accounts, allowlists, app passwords, and OAuth grants when a job is complete unless the product workflow removes them automatically.
Credentials and saved endpoints
Saved source and destination server profiles are optional. Saved profiles should store hostnames, ports, labels, non-secret settings, and fingerprints. Passwords, private keys, OAuth tokens, app passwords, and database credentials should be entered per migration, encrypted for the active job, and removed when no longer required.
Credits, trials, and digital purchases
Migration Monkey uses credits to quote and run migrations. Free trials may cover base software installs and small mailbox moves when the detected payload stays within the clean baseline allowance plus the published trial margin. Custom apps, Node.js apps, WordPress.com export-only moves, WAF-restricted hosts, large databases, large file sets, tenant migrations, and assisted relay routes may require more credits.
Credit packs, coupon credits, and promotional credits are digital service credits. Stripe or another payment processor may handle payment details. Duplicate, mistaken, or failed purchases can be reviewed by support.
Compliance responsibilities
You are responsible for having a lawful basis, notices, contracts, backups, change windows, and administrator authority for the data being migrated. Migration Monkey acts on documented instructions for migration metadata processing and is designed to avoid payload custody whenever possible.
Third-party names
Third-party names, trademarks, service marks, logos, and trade names, including WordPress, WooCommerce, Magento, Microsoft 365, Gmail, Google Workspace, Zoho, Yahoo, cPanel, Installatron, Node.js, Laravel, Drupal, Joomla, PrestaShop, Cloudflare, Sucuri, and other product or company names, are the property of their respective owners. Migration Monkey uses these names only to identify supported migration sources and destinations and is not endorsed by or affiliated with those owners.
Contact
Questions about these terms can be sent to support@migrationmonkey.com.