Migrate

Move a site from one saved profile to another — staging to production, or to a new server — with URLs rewritten and the target's database credentials kept.

How

Migrate in the rail (or a site's Migrate tab, which pre-fills the source). Four steps:

1. Source and target — two saved sites.
2. Scope — Content + DB (recommended: wp-content and the database, without replacing the target's WordPress core and root files) or Full site (the whole public root and database, while the target's database credentials stay active).
3. URLs — the source and target addresses. Both are read from the sites automatically; override them if the target should answer on a different address.
4. Review — one sentence in plain words saying exactly what will happen, then the word MIGRATE to confirm.

What happens

1. A fresh backup of the source is made, in the chosen scope. It stays in your backup folder afterwards.
2. It is restored onto the target. The target's wp-config.php database credentials are preserved; if the table prefixes differ, the target's is applied.
3. If the scope includes the database, every occurrence of the source URL is replaced with the target URL — across all tables, inside serialised data — and home and siteurl are set.

Before you migrate

• Both sites need SSH access and WP-CLI (for the URL replace).
• The target must already have WordPress installed with working database credentials; that is what is preserved.
• Make a backup of the target first if it holds anything you would miss. The migration overwrites it.

Reversing

A migration cannot be undone by the app, but nothing is lost: the source's backup is in your folder, and if you backed the target up first, restoring that backup to the target puts it back.