Skip to content

Knowledgebase

Planning a migration to a VPS or dedicated server

servers

A move to a server is a migration project, even when the website address stays the same. The operating system, panel, PHP or .NET version, database engine and management responsibilities can all change. Build a plan around the application and its data rather than copying files first.

01 Inventory the running service

List websites, databases, mail, DNS zones, cron jobs, certificates, licenses, API callbacks and firewall allowlists. Record software versions and required extensions. Identify who can pause writes, approve DNS changes and restore the previous service. Confirm which migration tasks are included in your Nabtech order.

  1. Agree the target configuration and management scope. Confirm the OS, supported control panel, resource allocation, backup destination and access method before provisioning.
  2. Create the destination accounts and security rules. Use a separate administrative identity where supported, strong authentication and restricted management access. Keep database services private unless remote access is required and controlled.
  3. Copy files and a database backup. Update paths, credentials and service addresses. Recreate schedules and integrations, leaving duplicate transactional jobs disabled until cutover.
  4. Test using a preview method that reaches the new server without sending ordinary customers there. Check application functions and external integrations, not only a static home page.
  5. Choose a cutover window. For a store or portal, pause writes or use a documented replication method for the final data synchronisation. Record exactly which copy becomes authoritative.
  6. Update DNS and required third-party allowlists. Verify TLS, email delivery, callbacks and background processing. Watch both servers for unexpected writes or requests during DNS cache expiry.

What must a server-migration rollback account for?

Keep the old environment and a restorable backup until acceptance checks pass. A rollback must account for new orders or updates received on the destination. Pointing DNS back without reconciling those writes can lose data. Document who makes the rollback decision and which symptoms trigger it.

02 Close the migration properly

Confirm that backups complete on the new server and that monitoring reaches it. Revoke temporary transfer credentials, remove public backup archives and update internal access records. Cancel the former hosting service only after the team has verified the website, mail and retention requirements. A control-panel license or existing IP address does not automatically move with a server order.

Was this answer helpful?

Need a little more help?

Our support team can help you find the next step.

Contact support