It will only take a few steps to migrate virtual machines or bare metal servers from your existing OSCA, Scaleup or Oracle Global Startup Ecosystem subscription to the new subscription using the OCI console, CLI (recommended) or REST API.
Step 1: Export/Import Image
You will need to export your images to object storage in the existing subscription, import them in the new subscription, and then use them when creating new instances, as described in the OCI documentation.
Currently OCI doesn’t support exporting Windows images.
QUICK TIP: You may want to take this opportunity to configure boot volume backup (minimum recommended policy: Silver).
Step 2 (Optional): Migrate Block Volumes
If you have any block volumes, you will have to use OS utilities or third-party software to migrate them to the new subscription.
QUICK TIP: It is a best practice to have all your application data in block volumes instead of boot volumes.
Also, you may want to take this opportunity to configure block volume backup (minimum recommended policy: Silver).
Don’t forget that in OCI block volumes are encrypted by default using AES-256 or your own keys (recommended).
Step 3 (Optional): Update Load Balancing and DNS
Whether you are using OCI’s load balancing or DNS service or a third-party’s, you will need to update these services with the new instance IPs after you migrate to the new subscription.
Step 4: Migrate Other Resources
All other resources (e.g.: VCNs, subnets, route tables, internet gateways, security lists, DHCP options, NAT gateways) will need to be re-created manually using the OCI console or existing automation (Terraform, Chef).
QUICK TIP: Your security lists will need to be updated at least for the new instance IPs, but you may also want to take this opportunity to remove any outdated or unused rules.
Like with OCI Compute, it will also only take a few steps to migrate buckets and objects to the new subscription.
If you only have a few buckets and objects, it may just be easier to download your objects from the existing subscription, re-create buckets and upload objects to the new subscription manually using the OCI console.
QUICK TIP: You may want to take this opportunity to move any objects that you seldom or rarely access to archive storage.
Otherwise, you may want to create a “staging” server in OCI Compute with enough storage capacity for your objects, and use the CLI (recommended) or REST API to re-create buckets and download/upload objects following the instructions in the OCI documentation.
Don’t forget that in OCI objects are also encrypted by default using AES-256 or your own keys (recommended).