System migrations
Moving services from end-of-life systems, recreating their configuration on a supported platform and switching traffic in a controlled way.
SYSTEMS / PRODUCTION OPERATIONS
Infrastructure you can maintain after deployment.
I bring Linux environments into order, migrate services from older systems, containerise applications and build a safe path from configuration to monitoring, backups and rollback.
- Platforms
- Debian, Ubuntu, RHEL
- Layers
- System, network, containers
- Priority
- Continuity and recoverability
APPROACH
Production needs more than a running process.
A server is part of a wider system: DNS, certificates, a firewall, storage, dependent services, monitoring, backups and operational procedures. Changing one element can affect the whole chain.
Before a migration, I inventory services, ports, data, dependencies and startup methods. The new environment is built in parallel, tested and only then takes over traffic.
A deployment is complete only when health checks, logs, backups, a recovery plan and clear instructions for subsequent updates are in place.
AREAS OF EXPERTISE
Areas I combine in one project.
The scope follows your goal and the current state of the environment. We can start with a single issue or a complete project.
Containerisation
Docker Compose, process isolation, read-only filesystems, health checks, restricted privileges and predictable releases.
Reverse proxies and TLS
Nginx, Let's Encrypt certificates, security headers, caching, request limits and support for multiple domains.
Operations and recovery
Monitoring, logrotate, backups, retention, smoke tests, rollback and documentation for everyday maintenance.
WHAT YOU RECEIVE
What you receive beyond the configuration.
A deployment should be verifiable, maintainable and safe to develop further.
- 01
An inventory of services, ports, processes, data and dependencies.
- 02
The target architecture for the host, containers, network and reverse proxy.
- 03
Scripts for deployment, updates, backups, smoke tests and rollback.
- 04
Configuration of TLS, logging, log rotation and basic hardening.
- 05
A production runbook and checklists for cutover and recovery.
HOW I WORK
From context to controlled deployment.
- 01
Inventory
I review services, data, dependencies, resource usage and the limitations of the old host.
- 02
Parallel build
I prepare the target system without interfering with the running production environment.
- 03
Validation
I test the application, network, certificates, backups and behaviour behind the reverse proxy.
- 04
Cutover
I switch traffic, watch the metrics and keep a ready rollback plan.
WHEN IT HELPS
This service makes sense when…
You do not need a finished specification. A specific problem, risk or desired outcome is enough.
- The operating system has reached end of life and further updates are becoming risky.
- The application is started manually, without a repeatable deployment process.
- Multiple undocumented services share resources on a single server.
- You need to safely add another domain or a backend on a different port.
- Health checks, backups, log rotation or a tested rollback are missing.
Debian
Ubuntu
RHEL
Docker
Docker Compose
Nginx
systemd
Let’s Encrypt
Bash
PostgreSQL
RELATED WORK
See how these skills come together in a working project.
MONITORING / OBSERVABILITY
UPnator
A monitoring and reliability platform for websites, APIs, servers, databases and telephony, with alerts, status pages, incident history and SLO reports.
Read the case study →
CYBERSECURITY / AI / EVIDENCE
AISeeRisk
A security audit platform combining an authorised scope, reliable evidence, risk prioritisation and controlled remediation with subsequent verification.
Read the case study →
AI / VOIP / COMMUNICATION PLATFORM
Callchestra
A business communication orchestration platform combining AI agents, PBX, routing, workflows, call analytics and integrations in one controlled environment.
Read the case study →
EVENTS / ORGANIZER PLATFORM
Eventnado
A two-sided event platform combining a catalogue and search for attendees with planning, administrative requirements, registration and event operations for organisers.
Read the case study →
HEALTHCARE / BOOKING
Psycholog Spektrum
A psychology practice website combining a calm presentation of its services, appointment booking, contact forms and tools for everyday administration.
Read the case study →
E-COMMERCE / HANDMADE
Sodashi Arts
An online shop for handmade crafts, scrapbooking and mixed media, designed around detailed product presentation, straightforward purchasing and everyday catalogue management.
Read the case study →
VOIP / COMMUNICATION PLATFORM
RelayPBX
A platform for building and operating business telephony, combining visual configuration, routing, tenants, SIP diagnostics and different deployment models.
Read the case study →FAQ
Common questions before we start.
Does a migration require shutting down the old server?
Usually not during preparation. The target environment is built in parallel, and downtime is limited to the final synchronisation and traffic cutover.
Is Docker always the right choice?
No. Containers are used where they simplify releases and isolation. System services or specialised components can remain managed by systemd.
Do you configure Nginx and certificates?
Yes. The scope can include reverse proxies, redirects, upload limits, caching, security headers, Let's Encrypt and a certificate renewal test.
What happens if a new release fails its health check?
The deployment process should stop the release and restore the previous image or configuration. Rollback is designed before the cutover, not after a failure.
NEXT STEP
Planning a server migration or bringing production into order?
We will start with an inventory and risk assessment, then prepare the target environment, tests, cutover and rollback scenario.