Customer Stories
Top Human Resource Provider Migrates Infrastructure to the Cloud
Visma Raet gains transformational business benefits by migrating its workload to the cloud with no downtime

Visma Raet is a leading international provider of human resource and payroll solutions in the Netherlands, Spain, and Latin America. It was the first company to develop HR software in the cloud, offering a fully integrated range of HR software and services. With 1.7 million clients currently using its software to manage their HR affairs, the company aims to become the largest cloud-based enterprise software provider in Europe. Visma Raet won HR Professional of the Year in 2021.
Platform was outdated and no longer scaling
Why
Migrate on-premise TFS to Azure DevOps
What
Adopt robust DevOps process to add agility while ensuring safe and speedy data migration
How
Innovate or Die
Organizations are moving to the cloud in droves. Visma Raet strives for excellence, but recognized that its platform was outdated and no longer scalable. To continue innovating, maintain high productivity, and efficiently serve its clients, the company sought an HR cloud solution to give it a competitive edge. But HR is data-heavy, and Visma was concerned about successfully migrating critical data and workloads to the cloud without risking business interruption or downtime. Any interruption to its 250 developers would mean a considerable loss of money, time, and effort.
Preparation to Achieve Zero Downtime Migration
With only 13 weeks lead, Xebia helped Visma meticulously prepare, communicating regularly with its developers in the Netherlands, Belgium, Spain, and India, to ensure they could anticipate risks during the migration weekend. Xebia first migrated the on-site TFS App Tier. Next, it regularly communicated with Visma's developers about risk management, helping Visma prepare presentations and workshops to notify its teams about the planned migration weekend on a recurring basis. Everything had to be seamless. The migration to VSTS (Azure DevOps) was performed in one weekend, and on Monday, everything worked perfectly—no glitches. The timing couldn't have been more perfect, as the old TFS server went down six weeks later, which would have cost an enormous amount of time and effort to replace.
Contact