Move the service—not just the files.

Choose a measured workload, data location and named operator before provisioning.

Record the services that make the site work, including those not stored with WordPress.

One dashboard login does not prove ownership of the whole website stack.

Treat file deployment and database replacement as separate decisions.

Change only the records needed for the website and preserve the mail configuration.

A successful certificate step is not proof that every public hostname works.

A working contact form includes receipt in the intended inbox, not only a success message.

Define how new writes are handled before replacing a database or changing traffic.

An older database can remove newer records even when the application files are correct.

Name what can be reversed, what must be reconciled and who can authorize each step.

A server transfer can affect other applications; isolate the exact unit of ownership first.

Hand over a usable operating record and verify the client can reach the controls they own.

Portability needs source, data, service records and a receiving workflow—not just a backup button.

Accept the launch only when the real reader and business paths work together.