Environment Production

New migration

Create an account, confirm data ownership, connect both endpoints, and run a no-custody migration.

  1. 1Account
  2. 2App profile
  3. 3Source
  4. 4Destination
  5. 5Review and migrate

App profile

Choose the stack you are moving.

Waiting for install folder scan.

Source endpoint

Where the current site lives.

Folder ready for scan

Destination endpoint

Where the app will be migrated.

All checks passed

Direct server-to-server

We only orchestrate. Your servers talk directly.

Source server 203.0.113.25
Source to destination tunnel TLS 1.3 + signed job token
Destination server 198.51.100.42
No custody Control plane never touches payloads.
1 Source capture plugin

Captures files and database chunks locally, signs a manifest, and opens an outbound encrypted stream to the destination.

2 Destination restore agent

Creates or validates the fresh install, receives chunks directly from source, restores paths, imports DB, and rewrites config.

3 Audit-only control plane

Stores progress, consent, hashes, and error telemetry. No archives, dumps, uploads, or customer payloads land here.

Recent migrations

ID Application Source Destination Status Progress Credits Action
MIG-98214 W WordPress 6.5 203.0.113.25
/var/www/nyc_wp		 198.51.100.42
/var/www/staging_wp		 Ready to migrate 240
MIG-98213 M Magento 2.4.6 192.0.2.44
/home/magento_live		 198.51.100.42
/var/www/magento_stg		 Completed 382
MIG-98212 D Drupal 10.2 203.0.113.88
/var/www/drupal_prod		 192.0.2.77
/var/www/drupal_stage		 In progress 316
MIG-98211 JS Node.js custom 18.x 198.51.100.11
/opt/apps/api		 203.0.113.25
/opt/apps/api_stg		 Queued 210

Migration troubleshooting

Common blockers get actionable fix popups so operators can recover without guessing.

Gate Ownership/TOS not accepted

Start is blocked until the account owner confirms authorization to move the data.

WordPress wp-admin plugin install failed

Filesystem permissions, disabled plugin editor, or ModSecurity can block the helper plugin.

SFTP Permission denied on web root

Wrong owner/group or jailed path prevents the destination agent from writing restored files.

Database Import times out

Large dumps need chunked import, extended packet size, or a direct database socket path.

Runtime PHP or Node version mismatch

The destination runtime does not match the detected app requirements.

WAF Proxy blocks the agent handshake

Strict WAF rules can challenge the signed endpoint handshake or callback telemetry.

Migration Monkey terms

Data ownership and authority

You confirm that you own the website, application files, databases, media, customer records, logs, and configuration data being migrated, or that the owner/controller has authorized you in writing to perform this migration.

No payload custody

Migration Monkey coordinates a direct server-to-server transfer. The source endpoint sends files and database chunks directly to the destination endpoint. Migration Monkey does not receive, store, proxy, or back up customer payloads.

Metadata we keep

We keep account identity, consent acceptance, job status, endpoint fingerprints, transfer hashes, billing records, troubleshooting events, and audit logs so the migration can be supported, reconciled, and evidenced.

GDPR and regulated data

You are responsible for having a lawful basis and appropriate notices for the migration. Migration Monkey acts on documented instructions for metadata processing and avoids payload custody by design.

Endpoint scripts

You authorize temporary source and destination scripts, plugins, or agents to inspect application versions, package chunks locally, restore to the destination, and report progress/errors back to the control plane.

Server-to-server script

Migration fix

    Buy credits