FuelVision365 reaches milestone with Microsoft AppSource publication

This week, FuelVision365 celebrated a significant milestone: both FuelVision365 Core and FuelVision365 Trips have officially been published in the Microsoft AppSource. A key contributor behind the scenes is Business Solution Developer Jan Pieter de Boer, who played a central role in preparing the solutions for the cloud.  We asked Jan Pieter to reflect on the journey—its challenges, the lessons learned, and the value of going cloud-first. 

A Strategic Leap to the Cloud

“The shift to the cloud was more than just a technical change,” Jan Pieter explains. “It was a strategic move to future-proof our product.” The process, which involved a deep rethinking of both architecture and workflow, came with a steep learning curve. A big part of the challenge? Making key decisions early on—ones that would later be difficult or even impossible to change. “The cloud forces you to plan ahead in ways that on-premise environments don’t,” he says. “You constantly ask yourself: what must be done now? What will be hard to adjust later? Are we missing anything?”

Technical Challenges and New Rules

A big part of the challenge? Making key decisions early on—ones that would later be difficult or even impossible to change. “The cloud forces you to plan ahead in ways that on-premise environments don’t,” he says. “You constantly ask yourself: what must be done now? What will be hard to adjust later? Are we missing anything?”

Clear benefits

Despite the complexities, the benefits are clear. “Customers receive updates more quickly, which means bugs are resolved faster,” he says. “And because everyone is closer to the latest version, we no longer need to support as many old versions. One change in the code now reaches all users.”

The journey

The move toward a cloud-ready architecture began in 2019, with the modularization of FuelVision365 into extensions. In 2023, the team began phasing out incompatible code. By December 2024, the second phase focused on securing Microsoft’s approval—ensuring all extensions met the technical standards required for publication.