Treat server migration as a sequence, not an event
Most migrations to Nubis Compute go more smoothly when they are broken into discovery, landing-zone design, test migration, validation, and cutover.Server migration workflow
Inventory the source servers
Capture CPU, memory, disk layout, OS version, open ports, scheduled jobs, attached services, and dependency relationships.
Map the target design
Decide on the Nubis project, instance sizing, disks, VPC placement, security rules, and public access model.
Prepare a pilot server
Move one representative workload first so your team can validate tooling, cloud-init, backup, and support processes.
Sync data and configuration
Reproduce application config, secrets, SSH access, and any attached data paths before traffic moves.
What to validate before cutover
- The instance boots with the expected image and bootstrap logic
- Attached disks are mounted and application paths are correct
- Private and public traffic rules match the intended design
- Monitoring and backup coverage are active
- Billing ownership is correct for the project and organization