The database cut, as part of moving the VPS.
Sites are already synced. The last step is a short write freeze, a final dump or sync, then the application points at the new host. This is not a standalone database project.
Files first. Database last. DNS after a write test.
A full dump onto the new server while the old one still takes writes. Slow. It does not have to be the downtime.
Maintenance on the app, final dump, restore, one row written and read. Mail and DNS wait until that row exists on the new side.
The old server is not destroyed in the window. If the new grant fails, DNS stays where it was. We do not drop the source to prove the move.
That job lives on the other page
A version upgrade or a split onto a second machine, with the web server staying put, is a database migration. This page is the database step inside a server move.
Included in the server-move quote when we already have the inventory
It is not a second project with a second minimum. If the database turns out larger than the inventory, the quote changes before the window, not after.
Server move, and the database is the part you are unsure about?
Tell us the engine, the size, and whether the sites move too. No password in the first message.