What we do · Data and web
Managed datacenter migrations, rehearsed
Moving a live production platform (web, database, files, search and cache) to a new datacenter, or from another provider to us, without a weekend of downtime. The old side keeps running untouched until the new side is proven, and going back costs nothing.
What it is
A migration run as an engineering project, not a ticket. We build the destination fresh, seed it with your data while you keep trading, rehearse the cutover, and then move in a window measured in minutes. Afterwards we audit the new platform against the old one before anything at the old site is switched off.
How we build it
Built new, not restored. The destination stack is built to measured specifications, with current software and our hardening baseline, rather than copied from old images.
Data seeded early, deltas moved late. Databases are seeded from a physical backup and kept current by replication or incremental re-seed. Files are pre-synchronised, so the final pass only moves what changed. Search indexes are copied with a native remote reindex instead of being re-crawled through the CMS.
The right path for each payload. Bulk data travels over a relay path built for throughput; small deltas go direct over our encrypted backbone. Where a customer needs it, we extend their networks between sites so servers keep their addresses throughout.
The window is the DNS window, and it is yours. If a change could touch your traffic, we agree the timing with you first. Nothing else is scheduled into the cutover.
Rollback by design. Old data directories are renamed, never deleted, so going back is a rename and a DNS change.
A playbook with a clock. Every cutover is written as a playbook with a time budget per step.
Audit, then decommission. After the move we compare the new platform with the old baseline: exposure from the outside, patch level, cache hit rate, response times. Only then is the old side switched off, with its data kept until you sign off.
What it protects you from
- Weekend long maintenance windows and lost trading days.
- Editorial or order data entered during the window going missing.
- A "finished" migration that still quietly depends on the old site.
- A cutover with no way back.
In practice
A national news publisher. We moved the publisher's six site news and lifestyle group from Amsterdam to our Digital Realty facility in Athens. Because the destination was pre-seeded, the final file pass over millions of files moved only the changed ones in about seventy seconds, and the closing database and uploads sync took under five minutes, so each property's visible cutover was about five minutes regardless of editorial backlog. The publisher is served from Athens, close to its readers.
A news portal rebuilt in Athens. After moving a news portal onto a new three blade platform, cached responses came back in a few milliseconds and uncached pages in under half a second.
Why EuroVPS
- The old platform stays live and untouched until the new one has earned the traffic.
- Playbooks with time budgets, rehearsed and improved with every migration.
- One team owns the network, storage, platform and application layers of the move.
- We can extend your networks between sites so nothing has to be renumbered.
- Post move audits before anything is decommissioned, and your sign-off before data is retired.
FAQ
How much downtime should we expect? For most web platforms, the cutover is the DNS propagation window plus a final sync measured in minutes. We give you a time budget per step before the day.
Can you move us from another provider? Yes. We need read access to the source to seed the data; the source does not need to change.
Do we have to change IP addresses? Not necessarily. Moving between our sites, we can extend your networks so addresses move with the servers.
What if something goes wrong on the day? The old side is intact, so rollback is a DNS change. We decide go or no go against criteria agreed in advance.
Who does the work at the destination? Our engineers, end to end: hardware, network, storage, platform and the application stack.
Planning a move? Talk to an engineer.
Your next infrastructure partner
Let’s look at
your setup.
Tell us what you run today and what needs to improve. An engineer will review your brief and help you plan the next step.
+357 222 32280
who will look after your infrastructure.
Let’s start with your setup.
A little context helps us start the right conversation.