Pre-Migration Checklist

This checklist helps ensure your CloudRaya account, resources, and operational processes are ready before starting the migration from CloudRaya old panel to CloudRaya New Panel. Completing these steps will reduce downtime, prevent data gaps, and ensure a smooth transition for both technical and non-technical stakeholders.

Purpose of This Checklist

Migration to CloudRaya New Panel is an automated platform upgrade that preserves core infrastructure and account data while introducing a new operational model built around Projects, improved security, and clearer billing and auditability.

This checklist helps you:

Protect historical data and configurations that will not be migrated
Validate readiness for the new Projects and Teams model
Prepare users who rely on API, billing, and operational reports
Minimize disruption during the migration window

1. Account & Access Readiness

Confirm Account Email Access

After migration completes, you will receive an email to reset your password for CloudRaya New Panel.

Ensure that:

The registered email address is active and accessible
Your email system does not block automated system emails
You can receive messages from @wowrack.com and CloudRaya domains

If you do not receive the reset email, contact CloudRaya Support before retrying login.

2. Review Resource Inventory

Core resources will remain active and available after migration. Before proceeding, document your current environment for validation later.

Record the following:

Virtual Machines (names, IPs, status)
VPCs and subnets
Load Balancers
VPN connections
Kubernetes clusters
Storage services
Managed Services
Marketplace subscriptions

This reference helps confirm that all resources appear correctly in CloudRaya New Panel.

3. Export Billing & Financial Records

Some historical financial and usage data is not migrated to CloudRaya New Panel.

Before migration, export or record:

Credit history
Monthly billing reports
Invoices
Top-up history
Usage summaries

Recommended Format

Use PDF exports from the Control Panel where available
Store records in a secure internal system for finance, audit, or compliance purposes

4. Configuration & Automation (Not Migrated)

Some configuration-level and automation data is not carried over and must be recreated manually in CloudRaya New Panel.

Before migrating, document the following:

VM Schedules: automated start/stop and scheduling rules

Recommendation

Document VM scheduling rules, timing, and affected instances
Recreate these configurations in CloudRaya New Panel after migration

5. Project & Resource Organization Planning

CloudRaya New Panel introduces Projects as a first-class organizational and access control model.

Important Change

In old panel, resources were grouped using Project Tags (primarily for billing and labeling).

In New panel:

Projects become logical containers for resources
Projects support multi-user access through Project Teams
Billing, access, and visibility are scoped at the Project level

What Happens During Migration

Resources previously assigned to Project Tags are placed into a Default Project
Resources in the Default Project cannot be moved into newly created Projects

Recommendation

If you want a clean structure, consider creating new VMs and resources in new Projects after migration.

Plan your target Project structure in advance:

Examples:

By environment: Development, Staging, Production
By application: Web App, Internal Tools, Customer Portal
By department or client

6. API & Automation Users

If you actively use CloudRaya APIs:

CloudRaya New Panel uses a new API model with different endpoints, authentication flows, and response formats
Automation, scripts, and third-party integrations built for old panel may not be compatible with new panel without updates

Recommended Action

If your environment heavily relies on API automation, consider postponing migration until CloudRaya New Panel API documentation is available
Pause automation and scheduled jobs during the migration window
Monitor CloudRaya platform updates for the release of new panel API documentation
Validate all scripts and integrations in a controlled environment before re-enabling production workflows

7. Object Storage Users

If you use Object Storage through the portal UI:

The built-in File Explorer is discontinued in new panel

Prepare Tools

Ensure you have access to:

S3-compatible CLI tools
Desktop clients
API-based object management tools

These will be required to browse and manage objects going forward.

8. Multi-User Access Planning

CloudRaya New Panel introduces Project Teams for secure collaboration.

Before migrating:

Identify who needs access to each project
Prepare individual email accounts for each team member
Invited users will become project members and can create and manage your resources

This improves security, auditability, and compliance compared to shared credentials.