CID ERP Cloud Migration to Hidora: A Case Study

CID ERP is a Swiss ERP publisher and integrator based in western Switzerland. For over twenty years, the company has helped SMEs and public organizations manage their core business processes (accounting, human resources, commercial management, invoicing). Their ERP solution is used daily by hundreds of users who depend on its availability to work effectively.

When Alexandre Jungo, Co-director of CID ERP, started looking for an alternative to their traditional hosting setup, he knew exactly what he wanted: a performant, secure, sovereign platform managed by people who understand the technical challenges of a software publisher.

The challenge: hosting that couldn't keep up

For years, CID ERP relied on conventional hosting from a local provider. The infrastructure worked, but it was showing its limits as CID ERP's business grew.

The issues were numerous. First, performance had become insufficient: ERP response times degraded during peak hours when dozens of users accessed the same modules simultaneously. CID ERP's teams regularly received complaints from clients frustrated by system slowness.

Second, scalability was virtually non-existent. Every capacity increase required manual intervention, a support ticket, sometimes several days of waiting. For a software publisher that needs to onboard new clients quickly, this was a commercial bottleneck.

Finally, data sovereignty was becoming increasingly important. Several CID ERP clients, particularly Swiss public entities, required guarantees about where their data was stored and processed. The former hosting provider couldn't offer clear certifications on this front.

Beyond these primary issues, the lack of environment isolation was creating operational risk. Development, testing and production workloads shared the same infrastructure without clear separation. A database query gone wrong during testing could impact production performance. CID ERP's developers were forced to schedule their testing windows carefully to avoid disrupting end users, which slowed their release cycle considerably.

Searching for a cloud partner

Alexandre Jungo and his team evaluated several options. Hyperscalers (AWS, Azure, Google Cloud) offered technical power but raised sovereignty and complexity concerns. Managing infrastructure at the scale of AWS required DevOps expertise that CID ERP didn't want to build internally. Their business is ERP, not infrastructure.

They also considered traditional Swiss hosting providers, but many still offered rigid models with dedicated servers and little flexibility.

The cost model was another concern. CID ERP needed predictable billing aligned with actual usage. Hyperscalers are notorious for complex pricing structures where costs spiral with data transfer fees, API calls and hidden surcharges. For a mid-sized Swiss publisher, a surprise bill of several thousand francs at month-end is not acceptable. CID ERP wanted a transparent, usage-based model where costs correlate directly with the resources consumed.

It was through conversations with other software publishers in the region that Hidora's name kept coming up. The approach was compelling: a managed cloud platform based in Switzerland, with an accessible and responsive engineering team.

The Hidora solution

The migration to Hidora Cloud was carried out in three distinct phases over six weeks.

Phase 1 : Audit and architecture. Hidora's team began with a thorough audit of CID ERP's existing infrastructure. This included analyzing databases, application flows, storage volumes and load patterns. A detailed migration plan was produced with clear milestones and validation criteria at each stage.

Phase 2 : Migration and testing. The production environment was replicated on Hidora Cloud. Databases were migrated using synchronization procedures that guaranteed zero data loss. Load tests were performed to validate that performance met CID ERP's requirements. The Hidora team worked alongside CID ERP's developers to fine-tune application configurations.

Phase 3 : Switchover and stabilization. The production switchover was completed on a Sunday evening with less than 30 minutes of downtime. Hidora's team remained on standby for the first two weeks to monitor performance and intervene immediately if needed.

Concrete results

The effects of the migration were felt from day one.

3x performance improvement. Average ERP response times were reduced by a factor of three. End users noticed the difference immediately, with modules loading in under one second where they previously had to wait five to ten seconds.

Automatic scalability. The infrastructure now adapts automatically to demand. When CID ERP onboards a new client with 50 users, there's no longer any need to plan a manual capacity increase. Hidora's platform allocates the necessary resources transparently.

Guaranteed sovereignty. Data is hosted exclusively in Swiss data centers. Hidora is ISO 27001 certified, allowing CID ERP to confidently meet the requirements of its public sector clients.

Responsive support. Hidora's engineering team responds within an hour during incidents. Alexandre Jungo emphasizes that this is a radical change from the previous provider, where support tickets could go unanswered for 24 hours.

Reduced operational costs. Hidora's usage-based billing model allowed CID ERP to reduce hosting costs by 30% compared to the previous model, while benefiting from significantly better infrastructure.

Proper environment separation. CID ERP now operates distinct development, staging and production environments. Developers can run intensive database migrations and load tests on staging without any risk to production users. This isolation accelerated their release cadence from monthly to bi-weekly deployments, directly improving their ability to deliver features and fixes to clients.

Alexandre Jungo's testimonial

"The migration to Hidora was a turning point for CID ERP. We finally have infrastructure that matches our software solution. Our clients notice the performance difference, and we can guarantee their data sovereignty without compromise. The Hidora team understands our challenges as a publisher: they don't just host our servers, they invest in our success."

— Alexandre Jungo, Co-director, CID ERP

Lessons learned from this migration

This migration validated several principles that apply to any Swiss company considering a hosting change.

The audit phase is non-negotiable. Without a precise map of the existing setup, surprises during migration are inevitable. The initial 2-week audit identified undocumented application dependencies and unexpected data flows between modules. These discoveries could have caused service interruptions if they had been found mid-migration.

Progressive migration reduces risk. Rather than a total switchover, the phased approach allowed each component to be validated individually. If an issue had been detected on a specific module, the rollback would have affected only that module, not the entire platform.

Post-migration support makes the difference. The two weeks of on-call support after the switchover allowed three database configuration adjustments to be fixed quickly that would not have been caught during load testing. This type of hands-on support is the difference between a successful migration and a chaotic one.

The commercial impact is real. Beyond the technical gains, CID ERP now uses the quality of its hosting as a selling point with prospects. ISO 27001 certification and Swiss hosting have become selection criteria for public sector tenders.

Invest in monitoring before the switchover, not after. One lesson CID ERP's team would emphasize in hindsight is the importance of having full observability configured on the new environment before production traffic arrives. During the first week after switchover, two slow database queries surfaced that had not appeared during load testing because the test data set did not fully replicate production query patterns. Because the Hidora team had deployed application performance monitoring and real-time log aggregation from day one, these queries were identified and optimized within hours rather than days. Teams that defer monitoring setup until after migration risk flying blind during the most critical window.

Migration checklist for Swiss software publishers

CID ERP's experience highlights a repeatable process that other Swiss software publishers can follow when evaluating a cloud migration.

Before you start:

• Document all application dependencies, including undocumented integrations between modules. Most ERP systems have data flows that are not reflected in architecture diagrams.
• Measure current performance baselines (response times, throughput, error rates) so you have objective benchmarks to compare against after migration.
• Inventory your clients' compliance requirements. Public sector clients may require specific certifications or data residency guarantees that constrain your choice of provider.
• Identify your peak usage periods. ERP systems often experience predictable load spikes around month-end closings, payroll processing and fiscal year transitions.

During migration:

• Run parallel environments for at least one week before cutover. This allows your team to validate real-world performance with actual client data patterns.
• Involve your client-facing team in testing. They know the workflows end users rely on and can spot regressions that automated tests might miss.
• Plan the cutover for a low-activity window, ideally a weekend, and communicate the timeline to affected clients well in advance.

After migration:

• Monitor aggressively for the first 30 days. Some performance issues only surface under specific load patterns that may not occur during testing.
• Collect feedback from end users. Perceived performance improvements are as important as measured ones for client retention and satisfaction.
• Update your commercial materials. If you now offer Swiss-hosted, ISO 27001-certified infrastructure, make sure your sales team knows how to articulate this advantage in proposals and tenders.

What this migration illustrates

CID ERP's case is representative of a broader trend in the Swiss software ecosystem. Business application publishers are realizing that their hosting infrastructure is a differentiating factor for their own clients. A performant application on slow infrastructure is a slow application.

By choosing a managed, sovereign cloud partner, CID ERP not only solved its technical problems but also strengthened its commercial value proposition. Being able to tell a prospect "your data is in Switzerland, on ISO 27001 certified infrastructure, managed by engineers based in Geneva", that's a concrete selling point in a market where trust is essential.

For Swiss companies considering a similar migration, the message is clear: you don't have to choose between performance and sovereignty. With the right partner, you can have both.