Pay less for infrastructure. Hand over the operations.
TechOneOps moves your applications from an expensive cloud or hosting provider to Hetzner, or takes over the servers you already run, wherever they are. Every move is planned, tested and reversible, and from the first week of live operations your environment is monitored around the clock.
From handover to live operations of an existing environment
Migration phases, from assessment to regular operations
Lock-in: documentation, configuration, scripts and access stay yours
Many companies pay cloud prices for workloads that do not need them.
Large cloud platforms are built for scale most small and mid-sized companies never reach. You pay for managed extras, data transfer and reserved capacity, and the monthly bill keeps growing faster than your business.
Hetzner offers powerful dedicated and cloud servers in European data centres at a fraction of what comparable resources cost with the large providers. For most web applications, databases, internal systems and Kubernetes clusters, the infrastructure is more than enough.
What is usually missing is the team to run it. That is the part we take on. You get lower infrastructure costs and an operations team in one step, with infrastructure and our service shown separately in the proposal, so you can compare the total cost with what you pay today.
- Infrastructure sized to what your applications actually use, not to a price list of managed extras
- Servers in EU data centres: your data stays under the GDPR, and we sign a data processing agreement (DPA) with you
- Monitoring, backups, updates and incident response included in managed operations
- A clear cost comparison before you commit to anything
How a migration works
A migration is a project with a plan, not a weekend of improvisation. Every phase has a clear result, and you decide when to move on to the next one.
Assessment and target design
We map your applications, data, dependencies and traffic, then design the target environment and size it to real usage.
Environment built as code
The new environment is built with infrastructure as code, for example Terraform, Ansible or Helm, so it is documented, repeatable and versioned.
Parallel run and tests
The old and new environments run side by side. We synchronise data and test functionality, performance, backups and restores before anything is switched.
Cutover in an agreed window
Traffic is moved in a window agreed with you, usually outside your business hours, following a written cutover plan with a way back.
Hypercare after cutover
In the first days after the move we watch the environment with heightened attention and respond to anything unusual straight away.
Regular operations
The environment moves into managed operations: 24/7 monitoring, monthly preventive checks and support under the agreed service level.
The cutover is written down before it happens.
Before the switch, you receive a cutover plan with every step, the person responsible and the point at which we would roll back. Nothing depends on someone remembering what to do at night.
Cutover night at a glance
| Step | What happens | Check before continuing |
|---|---|---|
| 1 | Lower DNS TTL in advance and announce the maintenance window | Announcement sent, TTL active |
| 2 | Pause writes and run the final data synchronisation | Record counts match on both sides |
| 3 | Switch DNS and load balancer to the new environment | Health checks green, TLS certificates valid |
| 4 | Smoke tests with your team on key user journeys | Sign-off from your contact person |
| 5 | Keep the old environment available for an agreed period | Rollback remains possible until sign-off |
The example is illustrative. Your plan reflects your applications and your agreed window.
Servers already in place? Live operations in three weeks.
If your servers already run where they should, on Hetzner, with another cloud provider or on your own hardware, there is nothing to migrate. We take over the existing environment in three weeks and run it from then on.
| When | What happens | Result |
|---|---|---|
| Week 1 | Access, information and knowledge handover from your team or previous provider | We know what runs, where, and who decides |
| Week 2 | Entry audit, monitoring and alerting set up | A documented baseline and alerts that reach us |
| From week 3 | Live operations under the agreed support plan | Business hours or 24/7 support, monthly checks and reports |
The entry audit becomes the baseline for every following monthly check. An availability (uptime) commitment is agreed once the audit and takeover are complete, because only then is the state of the environment known.
What we need from you
A smooth handover depends on a few things only you can provide. We agree the details in the first conversation and keep the effort on your side small.
- Access to servers, provider consoles, repositories and other agreed systems
- Knowledge transfer: a few sessions with the people who know the environment today
- A list of authorised people who may report incidents and approve changes
- A description of the system, as far as it exists. Gaps are fine, we fill them during the handover
No lock-in. Your environment stays yours.
Everything we build or change is documented and versioned, and it belongs to you. You keep control of your servers and your data at all times.
If you ever decide to end the cooperation, we hand over everything your own team or another provider needs to continue:
- Documentation of the environment and operating procedures
- Configurations and infrastructure code
- Scripts, automation and deployment pipelines
- All access credentials, transferred in an orderly way
Questions about migration and onboarding.
Will there be downtime during the migration?
We plan the migration to keep downtime as short as possible. Thanks to the parallel run, the cutover itself usually takes a short, announced window outside your business hours. The exact window depends on your applications and data and is agreed in advance.
How much can we save by moving to Hetzner?
That depends on what you run today and how it is billed. In the assessment we compare your current costs with the target environment plus our service, so you see the full picture before you decide.
How is a migration priced?
A migration is a one-off project outside the monthly managed operations fee. We quote it after the assessment, and work starts only once you have approved the quote.
Which providers can you migrate from?
From the large cloud platforms such as AWS, Azure or Google Cloud, from traditional hosting providers and from your own servers. If a move does not make sense for part of your setup, we tell you.
What if our current provider or team is not cooperative?
We work with what is available. Missing documentation is common, and the entry audit is designed to fill the gaps. What we do need is legitimate access to your systems and data.
Find out what your move would look like.
Tell us what you run today and where. We reply within one business day and propose the next step in writing, from a first assessment to a full migration plan. No commitment.