Skip to main content
Solved

IFS Cloud 24R2 Onprem Migration to Azure

  • June 22, 2026
  • 2 replies
  • 68 views

Forum|alt.badge.img

Hi Team

We are currently planning the migration of our IFS Cloud 24R2 environment from on-premises VMware infrastructure to Azure Virtual Machines, and we would like to seek your guidance on the appropriate migration approach.

We are evaluating the following two options:

  1. Lift-and-Shift (Rehost):
    Migrating the existing VMware-based environment directly to Azure VMs with minimal changes.

  2. Redeployment (Rebuild):
    Rebuilding the IFS Cloud environment natively in Azure following recommended architecture and deployment practices.

Our key questions are:

  • Does IFS recommend Lift-and-Shift for IFS Cloud 24R2 environments, or is a Redeployment approach generally preferred?
  • From your experience, what are the advantages and risks associated with each approach in the context of IFS Cloud?

Additionally, since the IFS Cloud ERP application stack involves Kubernetes-based components, we would like to understand:

  • If we proceed with Lift-and-Shift, could this introduce any potential issues with Kubernetes clusters, such as:
    • Networking complexities
    • Performance overhead
    • Compatibility or configuration challenges in Azure
  • Would a Redeployment approach (e.g., setting up Kubernetes properly in Azure VMs or optimized configurations) be a more stable and future-proof strategy?

Our priority is to ensure:

  • Long-term stability and supportability
  • Alignment with IFS best practices
  • Optimal performance in Azure

We would appreciate your recommendations on the most suitable approach, along with any known limitations, risks, or prerequisites we should consider.

Thank you in advance for your support.

 

Best answer by SamiL

Correct, the Remote Deployment is packaged to VMs to make it standard across hosting environments.

There is no support for the several native Kubernetes platforms, even if it would be technically possible to run on them (with development and testing efforts for each platform) without VMs.

So your two options are really:
 - Lift-and-Shift as VMs are supported regardless of where they run
 - move to IFS hosted managed Cloud where services run on a cluster as a special case

The Remote Deployment runs fine on Azure-based VMs. When moving you do need to double check that the IP spaces any of the networks used (including the internal Kubernetes network in microK8s ie. the pod network) are not conflicting.

2 replies

Forum|alt.badge.img+7
  • Sidekick (Customer)
  • June 23, 2026

Hi Team

We are currently planning the migration of our IFS Cloud 24R2 environment from on-premises VMware infrastructure to Azure Virtual Machines, and we would like to seek your guidance on the appropriate migration approach.

We are evaluating the following two options:

  1. Lift-and-Shift (Rehost):
    Migrating the existing VMware-based environment directly to Azure VMs with minimal changes.

  2. Redeployment (Rebuild):
    Rebuilding the IFS Cloud environment natively in Azure following recommended architecture and deployment practices.

Our key questions are:

  • Does IFS recommend Lift-and-Shift for IFS Cloud 24R2 environments, or is a Redeployment approach generally preferred?
  • From your experience, what are the advantages and risks associated with each approach in the context of IFS Cloud?

Additionally, since the IFS Cloud ERP application stack involves Kubernetes-based components, we would like to understand:

  • If we proceed with Lift-and-Shift, could this introduce any potential issues with Kubernetes clusters, such as:
    • Networking complexities
    • Performance overhead
    • Compatibility or configuration challenges in Azure
  • Would a Redeployment approach (e.g., setting up Kubernetes properly in Azure VMs or optimized configurations) be a more stable and future-proof strategy?

Our priority is to ensure:

  • Long-term stability and supportability
  • Alignment with IFS best practices
  • Optimal performance in Azure

We would appreciate your recommendations on the most suitable approach, along with any known limitations, risks, or prerequisites we should consider.

Thank you in advance for your support.

 

Hello,

This year we migrated for IFSv8 to IFS Cloud 24R1 on premise in Cloud Remote. We use Amazon EC2 environnement.

What we learned :

  • IFS DOES NOT WANT to support Managed KUBERNETES
  • IFS DOES NOT WANT to support Managaed DATABASE Oracle
     

Maybe IFS is more “kind” for the Azure Plateform, but I’m not very shure because their business model is Cloud managed by IFS.

 


Forum|alt.badge.img+11
  • Hero (Employee)
  • Answer
  • June 23, 2026

Correct, the Remote Deployment is packaged to VMs to make it standard across hosting environments.

There is no support for the several native Kubernetes platforms, even if it would be technically possible to run on them (with development and testing efforts for each platform) without VMs.

So your two options are really:
 - Lift-and-Shift as VMs are supported regardless of where they run
 - move to IFS hosted managed Cloud where services run on a cluster as a special case

The Remote Deployment runs fine on Azure-based VMs. When moving you do need to double check that the IP spaces any of the networks used (including the internal Kubernetes network in microK8s ie. the pod network) are not conflicting.