What to plan for.
BEFORE MOVING
Note the database version at both ends Note the character set and collation Export with the command line for anything large Verify the dump is complete before relying on it
WHAT CHANGES
Database and user names carry the new account's prefix The password will be new The host remains localhost
The application configuration must be updated for all three.
WHAT DOES NOT CHANGE
The table prefix, which travels in the dump.
COMMON FAILURES
The configuration not updated, producing a connection error immediately A truncated dump, producing missing tables Character set mismatch, producing mangled text A version difference rejecting old date values
TESTING BEFORE SWITCHING
Import into the new server, point a hosts file entry at it, and test the site fully before changing DNS.
That is how a migration is verified.
KEEPING THE OLD ONE
Do not cancel the source hosting until the new one is proven and DNS has propagated. A week at minimum.
AFTERWARDS
Run the same content audit on both. The numbers should match.
