Automate the migration
of your virtual machines

Discover the most open and reliable way to modernize your cloud infrastructure with full control, operational efficiency, and no vendor lock-in.

What is Chrysara?

Chrysara is Whitestack’s advanced solution designed to automate the migration of workloads from legacy environments to next-generation hypervisors.

Built with a standalone approach, it eliminates third-party dependencies, giving organizations complete control over their migration processes. It features an intuitive interface, support for YAML templates, and reusable configuration catalogs, streamlining every stage of the transition.

Problem

Virtual machine migration, while not inherently complex, becomes laborious and costly when performed manually. It typically requires multiple iterations to validate functional aspects before transferring the workload, slowing down projects and driving up costs.

Solution

Chrysara streamlines this process by reducing it to an error-free dry run and final deployment. This enables task parallelization and large-scale migrations, making the process faster, more efficient, and reliable for enterprise environments.

Chrysara is the solution that allows you to migrate from your current provider to a new one seamlessly

Automated and reliable validation

With Chrysara, migration does not depend on manual reviews. Its ability to run verification scripts when starting the VM in the new environment ensures an immediate decision: proceed or rollback. This means lower risk and higher confidence at every step.

Total storage flexibility

Unlike other solutions, Chrysara allows migrating both local disks (ephemeral or hyperconverged) and volumes on traditional storage. This versatility avoids limitations and adapts to the reality of any enterprise infrastructure.

Massive and parallel migrations

While other vendors force long, sequential processes, Chrysara accelerates iterations to just a dry run and a final deployment. This enables parallel migrations, significantly reducing time and costs.

Technological independence

Chrysara frees organizations from vendor lock-in and manufacturer dependencies. Its open approach allows migrating virtual machines without proprietary lock-ins, ensuring freedom, control, and the ability to modernize infrastructure on their own terms.

Key Features

Disk conversion

Transforms virtual machine disks into the format supported by the target hypervisor.

Resource generation on target hypervisor

Chrysara detects VM metadata at the source and automatically generates the necessary resources on the target platform, including YAML manifests for KubeVirt.

Full rehosting

Combines disk conversion and template generation to deploy VMs directly to the target environment.

Advanced settings

Offers additional configurations such as VirtIO drivers, network mapping, volumes, security groups, and health probes.

Post-migration validation

Executes external "black box" testing to ensure that each migrated VM is fully operational.

Migration templates

Executes external "black box" testing to ensure that each migrated VM is fully operational.

Migration parallelism

Enables simultaneous execution of multiple migration processes, optimizing time and resources.

Comprehensive reports

Generates detailed statistics, automatically identifies failed VMs, and enables new tasks exclusively for those that require them.

Recovery from checkpoints

In the event of failures, migrations can be resumed from a safe checkpoint, avoiding the repetition of already completed processes.

How does it work?

Chrysara is designed to evolve and adapt to the needs of every organization. It allows easy integration of new source or target hypervisors, as well as seamless addition of input sources and extra custom configurations.

Migration certification

Level	Objective	Environment	Tests
Level 0	Booting	Isolated	Software recognizes HW specs (CPU, RAM, Disk, Network) Disks and Partitions correctly mounted Network interfaces correctly initialized (IP and MAC address)
Level 1	Functional	Connected	The VM has connectivity to relevant endpoints Key components start correctly The VM responds to a functional test (API)