Migration
A migration is the process of moving data, software, or an entire system from one environment to another.
In website and infrastructure work, migration often means moving a site between hosts, domains, servers, or environments while preserving functionality and data.
What it does
Migration changes where a system lives or how it is deployed.
It is commonly used to:
- Move a site to a new host
- Change domains or environments
- Clone a site between development, staging, and production
- Consolidate infrastructure
- Rebuild or modernize an existing system
Core concepts
Source and destination
Every migration has a source environment and a destination environment.
The work usually involves moving files, the database, configuration, and environment-specific settings.
Data integrity
A successful migration preserves content, structure, behavior, and important system relationships.
Risk and rollback
Migrations carry risk, so they are usually paired with a backup and some rollback plan.
Common use cases
- Host changes
- Domain changes
- Environment cloning
- Production cutovers
- Platform or infrastructure updates
Practical notes
- Migration is broader than copy-and-paste. URLs, configs, credentials, file paths, and caches often need attention too.
- For WordPress, migration commonly involves both files and the database.
- Tools such as AIOWPM and WP-CLI are often used to support migration workflows.
- A safe migration usually starts with a backup and often uses staging for testing before production cutover.
Frequently Asked Questions
Is migration the same as backup?
No. A backup is a recovery copy. A migration is a move or transfer process.
Does migration always mean moving to a new host?
No. It can also mean moving between domains, environments, servers, or deployment setups.
Why use staging during migration?
Because staging lets changes be tested before the production environment is affected.