How do I migrate an account to another server?

Before you start

Read Migration overview. You need a completed backup of the account on the source, BackupWall on both servers, and the target's port 8087 reachable from the source.

1. Link the servers

Pairing is one way: the token is made on the target.

1. On the target: open Settings → Peering, card "Receive migrations on this server". Enter a label and choose Mint peer token. Copy the token; it is shown once. The page also shows this server's TLS fingerprint.
2. On the source: open Settings → Peering, card "Send migrations to a remote server". Enter a label, the remote URL (https://<target>:8087) and the peer token, then choose Register peer. BackupWall checks the connection and pins the target's certificate.
3. If the fingerprint is not what you expect, stop.

Links made before TLS existed show as "Insecure" until you pin them again. A rebuilt server gets a new certificate and a new fingerprint, so linked servers must pin the new one.

2. Migrate

1. On the source, open Migration and choose New migration. The wizard has four steps:
   • Target server.
   • Account: one account, or a reseller with all its accounts.
   • Settings: target username, primary domain, package, DNS/SSL/FTP/cron switches, the cutover plan, and Transfer (Direct push or Seed from backup destination).
   • Confirm.
2. The account is created on the target.
3. Choose Start migration and watch the progress bar. The run ends COMPLETED, partial or failed.
4. Read the Report for each run.

3. Re-sync and finalize

• When the run shows COMPLETED, choose Re-sync to pull changes made since, as often as you like. A re-sync takes a fresh backup of the account first, which re-reads every file; the migration waits for it as long as it keeps making progress.
• When you are ready to switch over, choose Finalize…, then Run final sync. See Cutover and DNS.
• A failed migration cannot be re-synced or finalized. A partial one can.

After the migration

• FTP passwords need a reset after a migration unless the report says they were carried. Read each run's Report.
• BackupWall never deletes an account it created, so a failed run leaves the new account on the target for you to clean up.
• Accounts land on the target's shared IP.

Recurring clones

On a completed push, the migration page has a Recurring clone control to set a frequency, pause or delete. Each run is a re-sync. Clone links pause when the licence is unlicensed with enforcement on.