Loading...
Uptime during migration
Data loss
Migration completed

Cleq has been a consistent presence since day one, always quick to respond and resolve issues. We're convinced they'll keep delivering that same quality going forward

Owner • SerenIT
SerenIT moved to a better hosting environment in one week, with no downtime, no data loss, and no disruption to their clients or candidates. Cleq has managed their infrastructure ever since.
We plan before we touch anything, and we do not cut over until we are certain nothing will break. Let us take a look at your setup.
The platform stayed live for clients and candidates at every stage of the migration. Not one hour of unplanned downtime.
Every record, every user, every job listing migrated without a single item lost or corrupted.
From kickoff to full cutover in seven days. SerenIT expected it to take longer. It did not have to.
SerenIT has had no provider-related incidents since the migration. Cleq manages their infrastructure on an ongoing basis.
SerenIT's previous hosting provider was not delivering the reliability their platform needed. Support was slow, stability was inconsistent, and the team had lost confidence that the infrastructure could hold up as the business grew. They wanted out, but migrating a live recruitment platform is not straightforward. Candidates were actively using the system. Clients were posting roles. Any mistake during the migration would have been immediately visible and costly. They needed someone who could move fast, plan properly, and not break anything in the process.


Cleq identified several challenges that were limiting scalability and increasing operational complexity:
These challenges created friction between engineering, IT, and compliance teams, slowing decision-making and increasing operational risk.
We mapped every component, every dependency, and every risk before a single change was made. The new environment was built and validated in parallel so the cutover was a controlled switch, not a leap of faith.
🔍 Full migration plan before touching production
We mapped every component, every dependency, and every risk before a single change was made. The new environment was built and validated in parallel so the cutover was a controlled switch, not a leap of faith.
🏢 Database migration with integrity validation
The full database was migrated and checked record by record before any traffic moved to the new environment. Nothing moved until we were certain nothing was missing.
🔐 Staged DNS cutover with zero interruption
DNS changes were staged and monitored carefully to avoid propagation issues. The cutover was executed during a low-traffic window and completed without a single report of downtime from SerenIT's users.
🛡️ Ongoing infrastructure management
Cleq has continued to manage SerenIT's infrastructure after the migration, handling monitoring, updates, and any issues that arise before they become problems.
The first thing we did was map everything. Before touching a single setting in production, we documented the full architecture, identified every dependency, and built the new hosting environment in parallel. Once the new environment was running and validated, we moved the database. We checked it thoroughly before anything else happened. Only when we were confident that every record was intact and every service was functioning correctly did we stage the DNS cutover. We executed it during a low-traffic window, monitored propagation in real time, and had rollback ready at every stage. The whole migration was complete in one week.