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
1
Inventory the source servers
Capture CPU, memory, disk layout, OS version, open ports, scheduled jobs, attached services, and dependency relationships.
2
Map the target design
Decide on the Nubis project, instance sizing, disks, VPC placement, security rules, and public access model.
3
Prepare a pilot server
Move one representative workload first so your team can validate tooling, cloud-init, backup, and support processes.
4
Sync data and configuration
Reproduce application config, secrets, SSH access, and any attached data paths before traffic moves.
5
Cut over with rollback in mind
Keep DNS, load-balancer, and rollback steps documented before the final switch.
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