Skip to content

Engines2Cloud Migration

This is your guide for a smooth transition from SWITCHengines to Switch Cloud.

This documentation supports your migration from the legacy SWITCHengines service to the Compute and service in Switch Cloud. It provides all relevant checklists, technical documentation, decision tools, and scripts — structured into four clear phases.

Migration Timeline:

  • Start: Autumn 2025
  • SWITCHengines End-of-Life: December 2026

Technical Scope

In this migration guide we exclusively provide guidance and support for SWITCHengines (OpenStack) projects.

If you have questions regarding a SWITCHkaas to Switch Cloud Kubernetes Migration, please contact the appropriate support channels listed below.

1. SWITCHengines OpenStack to Switch Cloud Compute Migration (Engines2Cloud)

  • In Scope: Migration of OpenStack projects from SWITCHengines to Switch Cloud Compute.
  • Migration Options: "Rebuild" and "Auto-Migration".
  • Full guidelines, documentation & support can be found on the current and linked pages.
  • Support Contact: cloud-support@switch.ch
    • Please use subject header: "Engines2Cloud Migration"

2. SWITCHkaas to Switch Cloud Kubernetes Migration

  • In Scope: Migration of Kubermatic projects from SWITCHkaas to Switch Cloud Kubernetes.
  • The SWITCHkaas End-of-Life is September 2026.
  • Migration Option: "Rebuild" only". No "Auto-Migration" available.
  • A migration FAQ can be found in the SWITCHkaas user documentation: https://kaas.pages.switch.ch/docs/migration/
  • Support Contact: cloud-support@switch.ch
    • Please use subject header: "SWITCHkaas to Switch Cloud Kubernetes Migration"

3. SWITCHengines Object Storage to Switch Cloud S3 Migration

  • In Scope: Migration of Object Storage from SWITCHengines to Switch Cloud S3.
  • The SWITCHengines Object Storage End-of-Life is December 2026.
  • Migration Option: Self-Service Transfer
  • Support Contact: cloud-support@switch.ch
    • Please use subject header: "SWITCHengines Object Storage to Switch Cloud S3 Migration"

SWITCHengines OpenStack to Switch Cloud Compute Migration "Engines2Cloud" Migration

Our Recommendation:

We strongly recommend choosing a Rebuild whenever possible. A Rebuild provides a clean, future-proof setup and avoids carrying over legacy issues. However, we acknowledge that in special cases an Auto-Migration may be required. For these scenarios, we provide an Auto-Migration script as a helper tool. This script is only meant to complement the official documentation of the recommended open-source migration tool, which is developed by an external provider.

Disclaimer:

The responsibility for the migration outcome – both Rebuild and Auto-Migration – lies fully with the project owners. Switch provides the guidance and tools listed on this page, but execution and validation remain in the project owners responsibility.

The following guidelines are solely dedicated to the OpenStack Engines2Cloud Migration. The present guide is designed to support you throughout the process. We look forward to welcoming you on Switch Cloud.

PHASE 1 – Orientation & Preparation

Objective:

Understand your current setup and prepare to choose between Rebuild or Auto-Migration: Build a clear picture of your current SWITCHengines environment. This preparation is essential to decide whether a Rebuild or an Auto-Migration is the better path for you. A structured self-assessment avoids surprises later and gives both you and the Switch Team the necessary context to support your migration.

Your Tasks (and why they matter):

  • Assign a technical SPOC (Single Point of Contact): Ensures there is one person responsible for technical questions and coordination. This avoids confusion and makes communication efficient.
  • Run a Self-Assessment.

These steps create the baseline for all your further migration decisions: - List OS in use (Linux distribution, Windows versions, etc.) → Helps determine compatibility and tooling needs. - Document all relevant VMs → Required to know what can be migrated directly and what might need a rebuild or what can be ignored. - Define data volumes → Large datasets may influence migration time, cost, and tooling choice. - Identify acceptable downtime windows → Critical for choosing the right migration path and planning cutover with minimal disruption. - Evaluate location and redundancy requirements (locations will change) → Since locations in Switch Cloud will change, you need to know your redundancy and availability needs upfront. - Optional: Prepare a simple architecture sketch (mandatory for support)→ A visual map of your current setup helps the team (and you) quickly understand dependencies and risks.

Outcome:

When Phase 1 is completed, you have:

  • A documented view of your current environment
  • Key decision factors for downtime, complexity, and redundancy
  • The clarity needed to move into Phase 2 – Decision & Planning with confidence

Once this is complete, you're ready to move to the strategic decision phase.

PHASE 2 – Strategic Decision & Planning

Objective: Decide your path forward and start planning accordingly.

Choose One Path:

  • Rebuild: Create a new setup in Switch Cloud, running in parallel to your current SWITCHengines instance. Pros & Cons Rebuild
  • Auto-Migration: Use provided tools to migrate your current setup (in a half-automatic way) Pros & Cons Auto-Migration

Your Tasks:

  • Compare pros and cons using provided guidance.
  • Decide on your preferred option.
  • In case you need support, send an E-mail to Switch. Email Template

Resources:

  • Email Template
  • Pros & Cons Overview
  • Optional: Book a 1:1 Planning Call

Outcome:

When Phase 2 is completed, you have:

  • Chosen your migration path (Rebuild, Auto-Migration, or External Partner)
  • Documented the reasoning behind your choice (pros/cons considered)
  • Prepared to move forward with a clear plan and next steps

PHASE 3 – Timeline & Alignment

Objective: Share your decision, define your timeline, and align documentation.

Your Tasks:

  • Submit your selected path (Rebuild / Auto-Migration)
  • Share your planned migration window (used for billing validation and coordination)
  • Finalize architecture and planning documentation if support is required.
  • Optional: Book an alignment session (1:1) with Switch.

Resources:

  • Email Template
  • Early Adopter Reminder: Rebuild or Auto-migrate by January 2026 to qualify for extra credits.

Outcome:

When Phase 3 is completed, you have:

  • Submitted your selected migration path to Switch
  • Defined and shared your migration/rebuild window (for billing validation and coordination)
  • Finalized your supporting documentation (as-is / to-be architecture, dependencies)

PHASE 4 – Execution & Finalization

Objective: Carry out your migration and close the loop.

Execution Options:

Mandatory Final Steps:

  • To decommission legacy resources on SWITCHengines, send a standard decommissioning email to: engines-support@switch.ch
  • Submit Final Confirmation to Switch Email including the decommission request confirmation
  • Switch will then validate and close the migration case, and terminate your contract on SWITCHengines.

Resouces:

Outcome:

When Phase 4 is completed, you have:

  • Successfully executed your migration or rebuild
  • Performed final checks, tests and validations on the new Switch Cloud
  • Submitted the final confirmation to Switch and closed your legacy SWITCHengines resources

Thank you for going through the migration steps. Our Switch Cloud Team looks forward to welcoming you on the new Switch Cloud. With this guide, we aim to make your migration as simple, transparent, and well-supported as possible.